📅 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 15:49:22
in reply to nevent1q…p6kd
Author Public Key
npub1lhe3qfx2q5m7mq5d39waepf9lzhsy0cdey66svn63fyk6rt6n7ps7zg7edPublished at
2023-06-07 15:49:22Event JSON
{
"id": "a10e8be2902fd72d8e64b80a6100355fbecf3ba130e18424e0ca0a6c0497604e",
"pubkey": "fdf31024ca0537ed828d895ddc8525f8af023f0dc935a8327a8a496d0d7a9f83",
"created_at": 1686152962,
"kind": 1,
"tags": [
[
"e",
"56b0adbf3d1d3d1065cfb99fb9d090666fd73ffb1d30c585af39837300065d3f",
"",
"root"
],
[
"e",
"647556135de898e5934c75943c84165802455b5d5e94a891b5eb2eaaa09ade2e",
"",
"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": "31dc51a32e39129bd5738f19a3856e31e5c35f17652743e8faaea08312c403386177533f303ea32588703e1741d29a2e9d22ebca98bd325af8814c0528646f7a"
}