From: Eric Voskuil <eric@voskuil.org>
Content-Type: multipart/alternative;
	boundary=Apple-Mail-A88D0DA1-A6D3-44A6-82E1-B1F1AB9ECAAF
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Mon, 14 Nov 2016 10:47:35 -0800
Message-Id: <CEDAD65E-512A-43CA-9BD6-56F7D9E6897C@voskuil.org>
References: <CAFp6fsGmynRXLCqKAA+iBXObGOZ2h3DVW8k5L9kSfbPmL1Y-QQ@mail.gmail.com>
In-Reply-To: <CAFp6fsGmynRXLCqKAA+iBXObGOZ2h3DVW8k5L9kSfbPmL1Y-QQ@mail.gmail.com>
To: Suhas Daftuar <sdaftuar@gmail.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BIP Proposal] Buried Deployments
Precedence: list


--Apple-Mail-A88D0DA1-A6D3-44A6-82E1-B1F1AB9ECAAF
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

NACK

Horrible precedent (hardcoding rule changes based on the assumption that lar=
ge forks indicate a catastrophic failure), extremely poor process (already s=
hipped, now the discussion), and not even a material performance optimizatio=
n (the checks are avoidable once activated until a sufficiently deep reorg d=
eactivates them).

e

> On Nov 14, 2016, at 10:17 AM, Suhas Daftuar via bitcoin-dev <bitcoin-dev@l=
ists.linuxfoundation.org> wrote:
>=20
> Hi,
>=20
> Recently Bitcoin Core merged a simplification to the consensus rules surro=
unding 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 do=
cumenting the rationale in a BIP for posterity.
>=20
> Here's the abstract:
>=20
> Prior soft forks (BIP 34, BIP 65, and BIP 66) were activated via miner sig=
naling 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 simplif=
ication and optimization) replace the trigger mechanism by caching the block=
 heights at which those consensus rules became enforced.
>=20
> The full draft can be found here:=20
>=20
> https://github.com/sdaftuar/bips/blob/buried-deployments/bip-buried-deploy=
ments.mediawiki
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

--Apple-Mail-A88D0DA1-A6D3-44A6-82E1-B1F1AB9ECAAF
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div></div><div>NACK</div><div><br></div><d=
iv>Horrible precedent (hardcoding rule changes based on the assumption that l=
arge forks indicate a catastrophic failure), extremely poor process (already=
 shipped, now the discussion), and not even a material performance optimizat=
ion (the checks are avoidable once activated until a sufficiently deep reorg=
 deactivates them).</div><div><br></div><div>e</div><div><br>On Nov 14, 2016=
, at 10:17 AM, Suhas Daftuar via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-d=
ev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; w=
rote:<br><br></div><blockquote type=3D"cite"><div><div dir=3D"ltr">Hi,<div><=
br></div><div>Recently Bitcoin Core merged a simplification to the consensus=
 rules surrounding deployment of BIPs 34, 66, and 65 (<a href=3D"https://git=
hub.com/bitcoin/bitcoin/pull/8391">https://github.com/bitcoin/bitcoin/pull/8=
391</a>), and though the change is a minor one, I thought it was worth docum=
enting the rationale in a BIP for posterity.</div><div><br></div><div>Here's=
 the abstract:</div><div><br></div><blockquote style=3D"margin:0px 0px 0px 4=
0px;border:none;padding:0px"><div><div>Prior soft forks (BIP 34, BIP 65, and=
 BIP 66) were activated via miner signaling in block version numbers. Now th=
at the chain has long since passed the blocks at which those consensus rules=
 have triggered, we can (as a simplification and optimization) replace the t=
rigger mechanism by caching the block heights at which those consensus rules=
 became enforced.</div></div><div><br></div></blockquote><div>The full draft=
 can be found here:&nbsp;</div><div><br></div><div><a href=3D"https://github=
.com/sdaftuar/bips/blob/buried-deployments/bip-buried-deployments.mediawiki"=
>https://github.com/sdaftuar/bips/blob/buried-deployments/bip-buried-deploym=
ents.mediawiki</a></div></div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>bitcoin-dev mailing list</span><=
br><span><a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-de=
v@lists.linuxfoundation.org</a></span><br><span><a href=3D"https://lists.lin=
uxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation=
.org/mailman/listinfo/bitcoin-dev</a></span><br></div></blockquote></body></=
html>=

--Apple-Mail-A88D0DA1-A6D3-44A6-82E1-B1F1AB9ECAAF--