{"type":"rich","version":"1.0","author_name":"npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3c","author_url":"https://nostr.ae/npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3c","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2016-11-15\n📝 Original message:Actually this does nothing to provide justification for this consensus rule change. It is just an attempt to deflect criticism from the fact that it is such a change.\n\ne\n\n\u003e On Nov 15, 2016, at 9:45 AM, Btc Drak \u003cbtcdrak at gmail.com\u003e wrote:\n\u003e \n\u003e I think this is already covered in the BIP text:-\n\u003e \n\u003e \"As of November 2016, the most recent of these changes (BIP 65,\n\u003e enforced since December 2015) has nearly 50,000 blocks built on top of\n\u003e it. The occurrence of such a reorg that would cause the activating\n\u003e block to be disconnected would raise fundamental concerns about the\n\u003e security assumptions of Bitcoin, a far bigger issue than any\n\u003e non-backwards compatible change.\n\u003e \n\u003e So while this proposal could theoretically result in a consensus\n\u003e split, it is extremely unlikely, and in particular any such\n\u003e circumstances would be sufficiently damaging to the Bitcoin network to\n\u003e dwarf any concerns about the effects of this proposed change.\"\n\u003e \n\u003e \n\u003e On Mon, Nov 14, 2016 at 6:47 PM, Eric Voskuil via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e NACK\n\u003e\u003e \n\u003e\u003e Horrible precedent (hardcoding rule changes based on the assumption that\n\u003e\u003e large forks indicate a catastrophic failure), extremely poor process\n\u003e\u003e (already shipped, now the discussion), and not even a material performance\n\u003e\u003e optimization (the checks are avoidable once activated until a sufficiently\n\u003e\u003e deep reorg deactivates them).\n\u003e\u003e \n\u003e\u003e e\n\u003e\u003e \n\u003e\u003e On Nov 14, 2016, at 10:17 AM, Suhas Daftuar via bitcoin-dev\n\u003e\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e \n\u003e\u003e Hi,\n\u003e\u003e \n\u003e\u003e Recently Bitcoin Core merged a simplification to the consensus rules\n\u003e\u003e surrounding deployment of BIPs 34, 66, and 65\n\u003e\u003e (https://github.com/bitcoin/bitcoin/pull/8391), and though the change is a\n\u003e\u003e minor one, I thought it was worth documenting the rationale in a BIP for\n\u003e\u003e posterity.\n\u003e\u003e \n\u003e\u003e Here's the abstract:\n\u003e\u003e \n\u003e\u003e Prior soft forks (BIP 34, BIP 65, and BIP 66) were activated via miner\n\u003e\u003e signaling in block version numbers. Now that the chain has long since passed\n\u003e\u003e the blocks at which those consensus rules have triggered, we can (as a\n\u003e\u003e simplification and optimization) replace the trigger mechanism by caching\n\u003e\u003e the block heights at which those consensus rules became enforced.\n\u003e\u003e \n\u003e\u003e The full draft can be found here:\n\u003e\u003e \n\u003e\u003e https://github.com/sdaftuar/bips/blob/buried-deployments/bip-buried-deployments.mediawiki\n\u003e\u003e \n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e"}