Ok. And you said the miner made the commitment *before he started hashing that block*? So does the commitment have any weight before the block has been mined? I'm trying to understand how you prevent the miner from dropping / censoring shares in the payout.
-
-
Accumulated work is easy to measure: just add it all regardless of DAG structure. If you need double spend protection I have another algorithm...In the simplest case of a diamond sub-graph -- just order first the side with the smaller hash, for instance. But this generalizes.
-
Anywhere I can read up more on this DAG-based consensus? And just to be clear, the reason you're opting for a DAG is to reduce the orphan rates. So it's an optimization. Is this an accurate assessment? Would share-chain consensus work with just a simple linked-list, like BTC?
-
Yes, it's called p2pool, and it's all but dead for a host of reasons. A DAG isn't really an optimization since a blockchain fails to reach consensus for fast block times, due to orphans. If you want fast blocks, a DAG is required.
-
What do you think are the *main* reasons? that p2pool is dead
-
besides the high orphan rates
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
