📅 Original date posted:2015-08-02
📝 Original message:I think your "hardfork bit" proposal is clever.
It addresses the particular valid concern of re-org facing users of a
fork that a small/near/fluctuating majority, or less, of mining power
supported.
While the "economic majority" argument may be enough on its own in
that case, it still has some aspect of being a hand wave.
This proposal adds support to those economic actors, which makes it
easier for them to switch if/when they choose. That is, it provides a
good fallback mechanism that allows them to make a decision and say,
"we're doing this".
Do you have the latest version up on github, or someplace where it
would be easier to collaborate on the specific text?
On Sat, Aug 1, 2015 at 4:23 PM, <jl2012 at xbt.hk> wrote:
> Although the chance is very slim, it is possible to have multiple hardforks
> sharing the same flag block. For example, different proposals may decide the
> flag time based on voting result and 2 proposals may have the same flag time
> just by chance. The coinbase message is to preclude any potential ambiguity.
> It also provides additional info to warning system of non-upgrading nodes.
>
> If we are pretty sure that there won't be other hardfork proposal at the
> same time, the coinbase message may not be necessary. With some prior
> collaboration, this may also be avoided (e.g. no sharing flag block allowed
> as consensus rules of the hardforks)
>
> The "version 0" idea is not compatible with the version bits voting system,
> so I have this hardfork bit BIP after thinking more carefully. Otherwise
> they are technically similar.
Michael Ruddy [ARCHIVE] /
npub18v…wndwr
2023-06-07 17:32:06
in reply to nevent1q…asxj
Author Public Key
npub18vfm5rz5aeu4aqc0jxnfka74f9wtzu77t0qvj06dm6s94llwpshs3wndwrPublished at
2023-06-07 17:32:06Event JSON
{
"id": "363fe24c08522ab3d4663115a4c8f8d787855efd7a256dbbb15b277d54370dac",
"pubkey": "3b13ba0c54ee795e830f91a69b77d5495cb173de5bc0c93f4ddea05affee0c2f",
"created_at": 1686159126,
"kind": 1,
"tags": [
[
"e",
"e273b7f72388c1d7ff9f849ef536e41c122ca02f05e9381ab36180bcb27ad161",
"",
"root"
],
[
"e",
"efaa472eb746ac2ea9fbb39ff70269dd45d1400ce1614da7bc97b5f1eba20674",
"",
"reply"
],
[
"p",
"b61e2e7ccbf4abd7f49715c62f4ac7a93cbdd5ead0316279c5f5fe9b18dd0aaa"
]
],
"content": "📅 Original date posted:2015-08-02\n📝 Original message:I think your \"hardfork bit\" proposal is clever.\nIt addresses the particular valid concern of re-org facing users of a\nfork that a small/near/fluctuating majority, or less, of mining power\nsupported.\nWhile the \"economic majority\" argument may be enough on its own in\nthat case, it still has some aspect of being a hand wave.\nThis proposal adds support to those economic actors, which makes it\neasier for them to switch if/when they choose. That is, it provides a\ngood fallback mechanism that allows them to make a decision and say,\n\"we're doing this\".\nDo you have the latest version up on github, or someplace where it\nwould be easier to collaborate on the specific text?\n\nOn Sat, Aug 1, 2015 at 4:23 PM, \u003cjl2012 at xbt.hk\u003e wrote:\n\u003e Although the chance is very slim, it is possible to have multiple hardforks\n\u003e sharing the same flag block. For example, different proposals may decide the\n\u003e flag time based on voting result and 2 proposals may have the same flag time\n\u003e just by chance. The coinbase message is to preclude any potential ambiguity.\n\u003e It also provides additional info to warning system of non-upgrading nodes.\n\u003e\n\u003e If we are pretty sure that there won't be other hardfork proposal at the\n\u003e same time, the coinbase message may not be necessary. With some prior\n\u003e collaboration, this may also be avoided (e.g. no sharing flag block allowed\n\u003e as consensus rules of the hardforks)\n\u003e\n\u003e The \"version 0\" idea is not compatible with the version bits voting system,\n\u003e so I have this hardfork bit BIP after thinking more carefully. Otherwise\n\u003e they are technically similar.",
"sig": "0b5daeab8eba90dddb41f6930ae1ca0f6b0db2f09b3dc097e0ee7c642f2227cb8072b809a75c41bd8453c03e7d409c91ac0cc9a55cca61d1ef8df91a4e61835d"
}