📅 Original date posted:2015-08-28
📝 Original message:On Fri, Aug 28, 2015 at 10:15 PM, Matt Whitlock <bip at mattwhitlock.name> wrote:
> However, this proposal currently fails to answer a very important question:
>
> • What is the mechanism for activation of the new consensus rule? It is when a certain percentage of the blocks mined in a 2016-block retargeting period contain valid block-size votes?
I chose not to address hard fork methodology at this stage because I
wanted to focus on the main algorithm. There are a number of options
open to us for deployment including a simple fixed activation (which I
think is feasible because there is a a lot of awareness and the
industry shows they are willing to rally around a single proposal). If
there are any strong preferences, I can add a deployment section
although I think it's less interesting until we forge a clear way
forward with what blocksize proposal to use.
Btc Drak [ARCHIVE] /
npub1lh…zg7ed
2023-06-07 17:37:58
in reply to nevent1q…2shm
Author Public Key
npub1lhe3qfx2q5m7mq5d39waepf9lzhsy0cdey66svn63fyk6rt6n7ps7zg7edSeen on
wss://relay.noswhere.comPublished at
2023-06-07 17:37:58Event JSON
{
"id": "0fdfd887200c959054d1c9c0c56c61fec64b4281bb1260168115d6c1b4a8d040",
"pubkey": "fdf31024ca0537ed828d895ddc8525f8af023f0dc935a8327a8a496d0d7a9f83",
"created_at": 1686159478,
"kind": 1,
"tags": [
[
"e",
"89feefa8fe3dbd95b7d3a6c8b355b09f064e01d014925a52bfb3842ed0275076",
"",
"root"
],
[
"e",
"9de13fceea8661845992de9bab7280de1aaf6002e52adf54468ee3df469bc632",
"",
"reply"
],
[
"p",
"fdf31024ca0537ed828d895ddc8525f8af023f0dc935a8327a8a496d0d7a9f83"
]
],
"content": "📅 Original date posted:2015-08-28\n📝 Original message:On Fri, Aug 28, 2015 at 10:15 PM, Matt Whitlock \u003cbip at mattwhitlock.name\u003e wrote:\n\u003e However, this proposal currently fails to answer a very important question:\n\u003e\n\u003e • What is the mechanism for activation of the new consensus rule? It is when a certain percentage of the blocks mined in a 2016-block retargeting period contain valid block-size votes?\n\nI chose not to address hard fork methodology at this stage because I\nwanted to focus on the main algorithm. There are a number of options\nopen to us for deployment including a simple fixed activation (which I\nthink is feasible because there is a a lot of awareness and the\nindustry shows they are willing to rally around a single proposal). If\nthere are any strong preferences, I can add a deployment section\nalthough I think it's less interesting until we forge a clear way\nforward with what blocksize proposal to use.",
"sig": "5c29c7326e01ea876a403cba6ffdcef72d27d216b4a7b60ed340c3c216e826f35ebe6be43986e8fb2e6586e087a6247972f9b1473d446a914f12a078d9652b41"
}