Hi, does Decred use the same protocol as bitcoin (https://en.bitcoin.it/wiki/Protocol_documentation) except just different signing/hashing algorithms? In Pieter Wuille's presentation about Segregated Witness [1] he mentions if they would be designing bitcoin from scratch the protocol would look very different. And in my experience bitcoin's protocol is a big mess with mixing little-big endian and stuff like VarInts make it just hard to parse without providing any real benefit. Because Decred is starting from scratch there is a big opportunity here to apply all the knowledge we learned from bitcoin development in the last 5 years. E.g. integrating SegWit and LN not just as hacks on top of an already bad protocol, instead making them core parts. [1] https://goo.gl/fL0Nvu
Great Idea!!! But it is important that we create a new way to mining and also a new basic script i think. We have to be careful to not do the same errors again like bitcoins has done, but on the other site we can take advance of all the good stuff we have learned feom btc
This is a great idea - especially the data format part. Does anyone know of any research looking at the reasoning behind the use of the various data formats and possible replacements to reduce the number of formats?
Almost everything has been adjusted in one way or another. For backwards compatibility reasons, some portions of bizarre 'endianness' have been kept. These include printing hashes backwards. On the other hand, things like getwork header int32 endianness swaps were removed. Numerous bugs were also fixed. One example is having to rehash an entire transaction N times where N is the number of inputs for SIGHASH_ALL verification.
Not forgetting that the decred its essence is a (POW / POS) hybridized consensus system proof-of-work.
Keep in mind that most of the dev work done thus far with Decred has focused on tangible features that differentiate it from Bitcoin. The Decred devs are certainly aware of these myriad quirks in the code, but removing them doesn't change the externalities of the code for the average user. That said, we are definitely open to fixing these various quirks as Decred evolves. By hybridizing PoW and PoS, Decred gains continuity across hard forks in a way that is not possible with Bitcoin, so fixing problems in consensus code is much less daunting a task.
Hello the algo blake256 14 round... for Decred are now used from Saffroncoin exatly?? now i testing my miner whit this cgminer version modded for this.. this miner version is supported and valid for mining decred? i have found this info here: AMD GPU :Cgminer 3.7.2 blake sources - https://github.com/Griffitsj/cgminer-saffron/ Cgminer 3.7.2 blake windows - https://github.com/Griffitsj/cgmine...nload/saffron-1.0/cgminer-saffron-windows.zip on this mining pool: http://www.miners-pool.eu/#!/pools
The kernel may work, but I ended up just writing my own. They don't have our block header specifications, so that miner will not work. It may give you a reasonable estimation of hash rate for the chain.
I am sure they will be as simple as possible.... And if anyone needs further assistance the community will be here.