📅 Original date posted:2017-05-25
📝 Original message:Hi, I didn't want to comment on
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-February/013643.html
because it seemed to me that thread was more broad.
I like bip8 very much as an extension to bip9, but I think it could be better.
With bip9, a bip9-ready node that sees a softfork activated that he is
not aware of will see a warning. See the implementation:
https://github.com/bitcoin/bitcoin/blob/master/src/validation.cpp#L1832
But with bip8, if a deployment is made at the end of the period
instead of through 95% signaling, nodes that implement bip8 but don't
implement a certain deployment that is activated can't receive such a
warning.
The solution that comes to mind is to reserve one of the nVersion for
the specific purpose of requiring that the bit is active for one block
when a deployment is locked in in this way (or maybe also when it's
activated with miners' signaling too, maybe that can be used to
simplify the way the current warnings are checked).
I expect the code changes to do this to be simple, and I'm happy to
help with it.
Jorge Timón [ARCHIVE] /
npub1fx…cl2d8
2023-06-07 18:01:52
in reply to nevent1q…69ht
Author Public Key
npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8Published at
2023-06-07 18:01:52Event JSON
{
"id": "9bfe13448e5adc867fa7d20e06dbc01722c755af0a714e5ae9acb32bdfbb18da",
"pubkey": "498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84",
"created_at": 1686160912,
"kind": 1,
"tags": [
[
"e",
"d5c58af68712f2eb230253b058dad80b95db4f8cd6a306c324b846ca44c9fa0c",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2017-05-25\n📝 Original message:Hi, I didn't want to comment on\nhttps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-February/013643.html\nbecause it seemed to me that thread was more broad.\n\nI like bip8 very much as an extension to bip9, but I think it could be better.\nWith bip9, a bip9-ready node that sees a softfork activated that he is\nnot aware of will see a warning. See the implementation:\n\nhttps://github.com/bitcoin/bitcoin/blob/master/src/validation.cpp#L1832\n\nBut with bip8, if a deployment is made at the end of the period\ninstead of through 95% signaling, nodes that implement bip8 but don't\nimplement a certain deployment that is activated can't receive such a\nwarning.\n\nThe solution that comes to mind is to reserve one of the nVersion for\nthe specific purpose of requiring that the bit is active for one block\nwhen a deployment is locked in in this way (or maybe also when it's\nactivated with miners' signaling too, maybe that can be used to\nsimplify the way the current warnings are checked).\n\nI expect the code changes to do this to be simple, and I'm happy to\nhelp with it.",
"sig": "0f397ec454023d0d09953612d313b47e66e2d6fdbda3c2b523c433cf3ec85a5d3654eba54f6740d1a32a60f6e5b71ff70f02a9ea185e815cf24ad0bf25175670"
}