{"type":"rich","version":"1.0","author_name":"npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw","author_url":"https://nostr.ae/npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-06-22\n📝 Original message:On Mon, Jun 22, 2015 at 2:33 PM, Tier Nolan \u003ctier.nolan at gmail.com\u003e wrote:\n\n\u003e The BIP-100 proposal uses a window of 12000 blocks (83 days) rather than\n\u003e the standard 1000.  Given that the threshold is lower than is normal for\n\u003e hard-forks, noise on the measurement could cause an activation even if less\n\u003e than 75% of miners agree.  It also means that the vote has to be sustained\n\u003e for longer and inherently gives a longer notice period.\n\u003e\n\n9,000 of last 12,000 blocks is OK with me (I don't think scanning through\nthe last 12,000 block headers every new block will cause performance\nproblems, but I'd want to benchmark it to be absolutely sure).\n\n\n\u003e Two weeks seems low for an upgrade warning.  I guess there would be an\n\u003e alert on the network.\n\u003e\nDo old nodes detect an upgrade by version numbers?  If that was headers\n\u003e only, then they could detect that large blocks have activated.\n\u003e\n\nBitcoin Core will alert when automatically when 51% of blocks have a\nversion it doesn't understand.\n\nIt will also alert automatically if it detects a chain with more work that\nit doesn't consider valid for some reason. And 0.11 contains code that\nalerts if you're on a chain that is being mined really slowly.\n\nHave you considered a \"fail\" condition?  For example, if 750 of the last\n\u003e 1000 blocks set bits 4 and 14, then it counts as a rejection by 75% of the\n\u003e miners.  Alternatively, if the rule doesn't activate by 11th Jan 2017, then\n\u003e it is disabled.\n\u003e\n\nI like the fail-if-not-activated-by idea. Not so crazy about the vote idea\n(what if miners set bits 3 AND 4 ?).\n\n-- \n--\nGavin Andresen\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150622/9cf73348/attachment.html\u003e"}