📅 Original date posted:2012-03-01
📝 Original message:On Thu, Mar 1, 2012 at 8:09 AM, Ben Reeves <support at pi.uk.com> wrote:
> One more thing to add. The implementation in the reference patch fixes
> the blockchain forking issue however by still allowing spent coinbases
> to be disconnected patched clients are still vulnerable to blockchain
> corruption. While not an immediate issue it would mean
> LoadBlockIndex() would error on restart and could cause problems for
> new clients during the initial blockchain download.
I am not following you here, can you explain what you're thinking?
> Is there a reason not to disallow duplicate coinbases entirely?
Because this would make it impossible for nodes to prune the vaules.
They'd all forever have to keep a set of all the coinbase hashes in
order to perform the test. The height-in-coinbase BIP will make
duplicates effectively impossible to create, which is a much more
clean behavior.
Gregory Maxwell [ARCHIVE] /
npub1f2…crwet
2023-06-07 03:10:44
in reply to nevent1q…xnfq
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwetSeen on
wss://relay.nostr.bandPublished at
2023-06-07 03:10:44Event JSON
{
"id": "fdefd8ef8d4d2b01087710899487523212c577dc206fc9bd902e081137da8499",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686107444,
"kind": 1,
"tags": [
[
"e",
"8d0fea15cf3bf2dd4fc4c205df6cc3e36626b119cb7ed7093b876376c9879239",
"",
"root"
],
[
"e",
"0c202c1b6e011dcfe9ca8aca636f49f10b7c19cb3d432b3d67adebf273c4bc65",
"",
"reply"
],
[
"p",
"5ab461bc713c73739adbc543fe021553ac026ff18e60267a0999d45ffdc3a943"
]
],
"content": "📅 Original date posted:2012-03-01\n📝 Original message:On Thu, Mar 1, 2012 at 8:09 AM, Ben Reeves \u003csupport at pi.uk.com\u003e wrote:\n\u003e One more thing to add. The implementation in the reference patch fixes\n\u003e the blockchain forking issue however by still allowing spent coinbases\n\u003e to be disconnected patched clients are still vulnerable to blockchain\n\u003e corruption. While not an immediate issue it would mean\n\u003e LoadBlockIndex() would error on restart and could cause problems for\n\u003e new clients during the initial blockchain download.\n\nI am not following you here, can you explain what you're thinking?\n\n\u003e Is there a reason not to disallow duplicate coinbases entirely?\n\nBecause this would make it impossible for nodes to prune the vaules.\nThey'd all forever have to keep a set of all the coinbase hashes in\norder to perform the test. The height-in-coinbase BIP will make\nduplicates effectively impossible to create, which is a much more\nclean behavior.",
"sig": "18c73fce4df94fe59ef947b20fa24936b38bd1e38ab4883954749529f105602e447d74ba6c34f8eb5d87b079956a333ea7a1aefee2d367a3419cea67ebbdc7d6"
}