You are viewing a single comment's thread from:
RE: Blockchain 101 - Why double producing is bad
Thank you @timcliff for such a comprehensive explanation focussed on Double Producing.
Few questions,
- How could whistleblower or some other witness take all the SP, how does that work in the backend?
- Is the problem limited to dPOS or we have such problem in POW as well, If yes how it works on it?
- Trying to learn something about blockchain.. you mentioned that the data entered before a block is produced remains static, again trying to clarify how does that work in the backend, is it Merkle Trees and Hashes?
There is a method for it in the code. It is deprecated though.
I believe PoW has the same problem, but it is less of a big deal because pretty much everyone waits for multiple confirmations with PoW tokens.
Each node just doesn’t make any changes to the data in its own database until it receives the next block.
Thank You @timcliff,
Sorry, an off the topic question,
what does it mean by single-threaded and multi-threaded in blockchain and how it affects the tps?
In simple terms - single threaded means it can only do one thing at a time. Multi threaded means it can do multiple things at once. Multi threaded obviously allows more transacting.
Thank you and please keep on writing more about blockchain, especially about graphene and DPOS .. I have set GINA to stalk you, looking forward to more info @timcliff :)
And I have gone through your blog, you seem to have very active participation in STEEM, I just wanna know if 'one account, one vote' will be a thing just for SMT or we will be seeing a fork for STEEM. Cause if it's just limited to SMT one of my posts becomes obsolete :)
Currently it is just a concept being discussed for SMTs.