4/ A “claim” is proof of past participation in a previous mining round. Concretely, it’s a block whose hash might or might NOT meet the difficulty target of a particular height, but is valid otherwise. Very similar to how miners claim their shares from Stratum pools today.
-
-
15/ Miner who mines block T+100 has a lot of power in terms of choosing what claims to honor. He can’t include a bogus claim, but he can choose which claims in the mempool to include / overlook. Not clear if this is solvable.
Show this thread -
16/ What if someone retroactively goes back and mines block T. He won’t be able to rewrite the block, but he could send a claim for block T even though he did not originally work on block T. Effectively “stealing the pot”.
Show this thread -
17/ One possible way to alleviate (not eliminate) this problem is to limit the amount of reward that could be re-distributed beyond the initial miner. Say, initial miner is guaranteed at least 50% of the pot.
Show this thread -
18/ Biggest problem: Complexity. Already you can see how much complexity is added to the protocol to accommodate sharing behavior. There are potentially many unknown gaming behaviors that can arise due to the added rules. Complexity is the enemy of security. Exhibit A: Ethereum.
Show this thread -
19/ Conclusion: IMO, if sharing reward is desirable, it's much better to add that functionality via a higher layer protocol, such as BetterHash, without compromising the underlying protocol. Unix philosophy has served us extremely well.https://twitter.com/hugohanoi/status/1004455570953330689 …
Show this thread
End of conversation
New conversation -
-
-
This is why to use a braid (DAG), because it eliminates the orphan problem and lets you get the block time down around one second. So you can sample the hashrate ~600 times faster or mine profitably with 1/600 the hashrate. p2pool has a ~30% orphan rate - heavily punishes latency
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.

