📅 Original date posted:2020-09-25
📝 Original message: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
John Tromp [ARCHIVE] /
npub1jz…tsze5
2023-06-07 18:27:09
in reply to nevent1q…dpf0
Author Public Key
npub1jzv8hadmmqgttce5q9dn69j4msczrwdw898t3fetwyt64gess4ssttsze5Published at
2023-06-07 18:27:09Event JSON
{
"id": "d30276da3546c07166c09f66292e10f5600a8f1409ba1193ae5b51b2e2b7a300",
"pubkey": "90987bf5bbd810b5e334015b3d1655dc3021b9ae394eb8a72b7117aaa3308561",
"created_at": 1686162429,
"kind": 1,
"tags": [
[
"e",
"4f892ae6f525d2005e47946a66b3d3edbcd098246411cbb80867ee7cc334acd9",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2020-09-25\n📝 Original message:Re: Floating-Point Nakamoto Consensus (bitcoin ml)\n\u003e\n\n\u003e This is a pretty big departure from cumulative POW.\n\nIt's still cumulative. But instead of cumulating network difficulty,\nthey cumulate log_2(solution difficulty).\n\nSo if two solutions are found simultaneously, and one has a hash\nthat's only half of the other, then that will have twice the solution\ndifficulty and thus contribute 1 more the cumulate log_2(solution\ndifficulty).\n\n\u003e Could you explain to me what you see happening if a node with this patch\n\u003e and no history starts to sync, and some random node gives it a block\n\u003e with a better fitness test for say height 250,000? No other solution\n\u003e will have a better fitness test at that height, so from my understanding\n\u003e its going to stop syncing. How about even later - say this proposal is\n\u003e activated at block 750,000. At 850,000, someone decides it'd be fun to\n\u003e publish a new block 800,000 with a better fitness test. What happens the\n\u003e 50,000 blocks?\n\nNothing happens in these cases, as the new blocks are still far behind\nthe tip in cumulative score (they just have higher score at their\nheight).\n\nregards,\n-John",
"sig": "4d762c039814e0da541ec60396caf310d0983995457d1d0859ca3cad234a897ed984932be754d626db63baa77196a545ae25f087a1ed65d4dd8b718fbee2a1ad"
}