summaryrefslogtreecommitdiff
path: root/6c/16b6519b026f45949b65709f8babd3479e50f3
blob: 88a4fb74ec0346d89f94af52a7e18e7a7bf768de (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
Return-Path: <eric@voskuil.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 6D326279
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 14 Nov 2016 18:47:38 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pg0-f50.google.com (mail-pg0-f50.google.com [74.125.83.50])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6A20FA1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 14 Nov 2016 18:47:37 +0000 (UTC)
Received: by mail-pg0-f50.google.com with SMTP id f188so56760091pgc.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 14 Nov 2016 10:47:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=voskuil-org.20150623.gappssmtp.com; s=20150623;
	h=from:content-transfer-encoding:mime-version:date:subject:message-id
	:references:in-reply-to:to;
	bh=x1AVxfShLqv/PD76TIP+gcQAM6Go844wmfz1pDZW0ps=;
	b=i7FhpR/IBN8VYaq7D/C7p21NRM+PqDkeyEpiBCa/v1zpTzMhIwHhLm54yWBsQqpqMd
	Wsj2FLze5Vo8JhXOz78FPvkq13O9AhuEB9Yj+urGAVutgw8x+TEgfUeXIxH01COB+DKn
	LA80i8Pz4yoHJTpMmBAo4r/q0T+zwruuMY86ewGOK7fKmblbEo8R7nRJzeAqze1niAMp
	1Nb/BH679YVN/WNfp5xXqeoLXxUi/f78PCutndJfZFjaYj5bjA3/9ew04hiji6tuUAUP
	WZXDeYcjo9EGcprsRVlFYbYD2YRrr1S7YWh2peBIHgh2Z7hzrv4SkLu/sd5jVylyHpiT
	d5/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:from:content-transfer-encoding:mime-version:date
	:subject:message-id:references:in-reply-to:to;
	bh=x1AVxfShLqv/PD76TIP+gcQAM6Go844wmfz1pDZW0ps=;
	b=B0sLYVlkzcZv0bwuu5kQn0v5dPJzcX/IsDsisrl2EysuXm4g2GW+wDLE8drBOVNX5+
	nd1n1FHOjCtLkMGtFr2Hp75smYZr9Z83H2t5q97NE70a2EMjKQ5Yysq/tfSI2mzDWVi8
	vc9it8H+hskQzu0NoBkv+3kYsTfhASynMpfcOQGiNFr3RujFBVWsIM/6ghmEvQgKBH78
	U3OoKljdXJsMx03bjNPl6MqYJxp7O/v4LKJsaaXYpIu7LKChnsJHogo1lR8Ays/jV/ia
	mAipqHXMkpQ+WzQ69v+zDE0FHJjnrnjDhPS8E6c0pA2b2GhQHCaA8x+14qDf5T1PKmgh
	J6ug==
X-Gm-Message-State: ABUngvd1G/Qxtqmpe3FaSCguemJrSLet0BSHADpcGNSIWFnaCAS1i3FHZzWi/lsa5SvS/g==
X-Received: by 10.98.15.5 with SMTP id x5mr38414850pfi.140.1479149257061;
	Mon, 14 Nov 2016 10:47:37 -0800 (PST)
Received: from [10.116.39.181] (mobile-166-176-185-48.mycingular.net.
	[166.176.185.48]) by smtp.gmail.com with ESMTPSA id
	d1sm36916975pfb.76.2016.11.14.10.47.36
	(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Mon, 14 Nov 2016 10:47:36 -0800 (PST)
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>
X-Mailer: iPhone Mail (14B100)
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,HTML_MESSAGE,MIME_QP_LONG_LINE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Mon, 14 Nov 2016 18:49:09 +0000
Subject: Re: [bitcoin-dev] [BIP Proposal] Buried Deployments
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2016 18:47:38 -0000


--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--