MIME-Version: 1.0
From: Suhas Daftuar <sdaftuar@gmail.com>
Date: Mon, 14 Nov 2016 13:17:25 -0500
Message-ID: <CAFp6fsGmynRXLCqKAA+iBXObGOZ2h3DVW8k5L9kSfbPmL1Y-QQ@mail.gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114c819e16f260054146da99
Subject: [bitcoin-dev] [BIP Proposal] Buried Deployments
Precedence: list

--001a114c819e16f260054146da99
Content-Type: text/plain; charset=UTF-8

Hi,

Recently Bitcoin Core merged a simplification to the consensus rules
surrounding deployment of BIPs 34, 66, and 65 (
https://github.com/bitcoin/bitcoin/pull/8391), and though the change is a
minor one, I thought it was worth documenting the rationale in a BIP for
posterity.

Here's the abstract:

Prior soft forks (BIP 34, BIP 65, and BIP 66) were activated via miner
signaling in block version numbers. Now that the chain has long since
passed the blocks at which those consensus rules have triggered, we can (as
a simplification and optimization) replace the trigger mechanism by caching
the block heights at which those consensus rules became enforced.

The full draft can be found here:

https://github.com/sdaftuar/bips/blob/buried-deployments/bip-buried-deployments.mediawiki

--001a114c819e16f260054146da99
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>Recently Bitcoin Core merged a simp=
lification to the consensus rules surrounding deployment of BIPs 34, 66, an=
d 65 (<a href=3D"https://github.com/bitcoin/bitcoin/pull/8391">https://gith=
ub.com/bitcoin/bitcoin/pull/8391</a>), and though the change is a minor one=
, I thought it was worth documenting the rationale in a BIP for posterity.<=
/div><div><br></div><div>Here&#39;s the abstract:</div><div><br></div><bloc=
kquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div><div>=
Prior soft forks (BIP 34, BIP 65, and BIP 66) were activated via miner sign=
aling in block version numbers. Now that the chain has long since passed th=
e blocks at which those consensus rules have triggered, we can (as a simpli=
fication and optimization) replace the trigger mechanism by caching the blo=
ck heights at which those consensus rules became enforced.</div></div><div>=
<br></div></blockquote><div>The full draft can be found here:=C2=A0</div><d=
iv><br></div><div><a href=3D"https://github.com/sdaftuar/bips/blob/buried-d=
eployments/bip-buried-deployments.mediawiki">https://github.com/sdaftuar/bi=
ps/blob/buried-deployments/bip-buried-deployments.mediawiki</a></div></div>

--001a114c819e16f260054146da99--