{"type":"rich","version":"1.0","author_name":"npub17rld56k4365lfphyd8u8kwuejey5xcazdxptserx03wc4jc9g24stx9l2h","author_url":"https://nostr.ae/npub17rld56k4365lfphyd8u8kwuejey5xcazdxptserx03wc4jc9g24stx9l2h","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2021-03-06\n📝 Original message:On Fri, Mar 05, 2021 at 05:43:43PM -1000, David A. Harding via bitcoin-dev wrote:\n\u003e ## Example timeline\n\u003e - T+0: release of one or more full nodes with activation code\n\u003e - T+14: signal tracking begins\n\u003e - T+28: earliest possible lock in\n\u003e - T+104: locked in by this date or need to try a different activation process\n\u003e - T+194: activation (if lockin occurred)\n\n\u003e ### Base activation protocol\n\u003e The idea can be implemented on top of either Bitcoin Core's existing\n\u003e BIP9 code or its proposed BIP8 patchset.[6]\n\u003e     BIP9 is already part of Bitcoin Core and I think the changes being\n\u003e     proposed would be relatively small, resulting in a small patch that\n\u003e     could be easy to review.\n\nTo get to specifics, here's a PR, based on #21334, that updates bip9\nto support an extra parameter to delay the transition from LOCKED_IN\nto ACTIVE until a particular timestamp is reached, and to reduce the\nactivation threshold to 90%:\n\n  https://github.com/bitcoin/bitcoin/pull/21377\n\nWith that in mind, I think the example timeline above could translate\nto taproot parameters of:\n\n  nStartTime = 1618358400; // April 14, 2021\n  nTimeout = 1626220800; // July 14 2021\n  activation_time = 1633046400; // October 1 2021\n\nThat is, signalling begins with the first retarget period whose parent's\nmedian time is at least April 14th; and concludes with the last retarget\nperiod whose final block's median time is prior to July 14th; that's\n91 days which should be about ~6.5 retarget periods, so should cover 6\nfull retarget periods, but could only cover 5.  Activation is delayed\nuntil the first retarget period where the final block of the previous\nretarget period has a timestamp of at least October 1st.\n\nNote that the timeout there is prior to the expected timestamp of the\nstartheight block specified in the proposal for bip8 parameters:\n\n  https://en.bitcoin.it/wiki/Taproot_activation_proposal_202102\n\nand earliest activation is after the expected release of 22.0 and hence\nthe maintenance end of 0.20.\n\nNote also that the PR above specifies the delay as a deadline, not a\ndelta between lockin and activation; so earlier lockin does not produce\nan earlier activation with the code referenced above.\n\nCheers,\naj"}