<oembed><type>rich</type><version>1.0</version><author_name>npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd</author_name><author_url>https://nostr.ae/npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-22&#xA;📝 Original message:The BIP-100 proposal uses a window of 12000 blocks (83 days) rather than&#xA;the standard 1000.  Given that the threshold is lower than is normal for&#xA;hard-forks, noise on the measurement could cause an activation even if less&#xA;than 75% of miners agree.  It also means that the vote has to be sustained&#xA;for longer and inherently gives a longer notice period.&#xA;&#xA;Two weeks seems low for an upgrade warning.  I guess there would be an&#xA;alert on the network.&#xA;&#xA;Do old nodes detect an upgrade by version numbers?  If that was headers&#xA;only, then they could detect that large blocks have activated.&#xA;&#xA;Have you considered a &#34;fail&#34; condition?  For example, if 750 of the last&#xA;1000 blocks set bits 4 and 14, then it counts as a rejection by 75% of the&#xA;miners.  Alternatively, if the rule doesn&#39;t activate by 11th Jan 2017, then&#xA;it is disabled.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150622/c4698689/attachment.html&gt;</html></oembed>