* Re: [bitcoin-dev] Floating-Point Nakamoto Consensus (bitcoin ml)
[not found] <mailman.27861.1601049417.32591.bitcoin-dev@lists.linuxfoundation.org>
@ 2020-09-25 17:23 ` John Tromp
0 siblings, 0 replies; only message in thread
From: John Tromp @ 2020-09-25 17:23 UTC (permalink / raw)
To: Bitcoin Protocol Discussion
Re: Floating-Point Nakamoto Consensus (bitcoin ml)
>
> This is a pretty big departure from cumulative POW.
It's still cumulative. But instead of cumulating network difficulty,
they cumulate log_2(solution difficulty).
So if two solutions are found simultaneously, and one has a hash
that's only half of the other, then that will have twice the solution
difficulty and thus contribute 1 more the cumulate log_2(solution
difficulty).
> Could you explain to me what you see happening if a node with this patch
> and no history starts to sync, and some random node gives it a block
> with a better fitness test for say height 250,000? No other solution
> will have a better fitness test at that height, so from my understanding
> its going to stop syncing. How about even later - say this proposal is
> activated at block 750,000. At 850,000, someone decides it'd be fun to
> publish a new block 800,000 with a better fitness test. What happens the
> 50,000 blocks?
Nothing happens in these cases, as the new blocks are still far behind
the tip in cumulative score (they just have higher score at their
height).
regards,
-John
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-09-25 17:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <mailman.27861.1601049417.32591.bitcoin-dev@lists.linuxfoundation.org>
2020-09-25 17:23 ` [bitcoin-dev] Floating-Point Nakamoto Consensus (bitcoin ml) John Tromp
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox