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
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
|
Return-Path: <earonesty@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 8F4C440F
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 14 Jul 2017 13:50:17 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qt0-f179.google.com (mail-qt0-f179.google.com
[209.85.216.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A87903CA
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 14 Jul 2017 13:50:16 +0000 (UTC)
Received: by mail-qt0-f179.google.com with SMTP id b40so62451947qtb.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 14 Jul 2017 06:50:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:sender:in-reply-to:references:from:date:message-id
:subject:to; bh=iZUY8oHonrIPyp5pyx46/vBojkkVFSZWyvJPGAC0GHk=;
b=P6QCxGT6j5XoxDzFgpwKCRszwpH+z9QX+WhXkE7SG5pdcHDNDEZqN29N76JoSZq2ph
V07xG4hkUKu59sHiAo1OHUoyhoRjCv7zlODgJT84dQeUX4bZ5FSksXt7PrmQ1R3bvk62
a1LEg6yTOjG8sXso1OETHnOvGGkm0HuEChbCecSq8F4eUxdZypmug2S96zBPuEEl+GGK
Di/piSbtNdAeR7Rd8b8FuHtrt0fHaJmKdWGgjDZXxs3KIKq2j5EQA1889E9s03Nk1NJN
BLrHFyyeVFPWQUvbedw5W6rghzrfTOPIg0u5/evIi6ezerm6nZq12kEfRzMeZ+wbyKoe
DuVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:to;
bh=iZUY8oHonrIPyp5pyx46/vBojkkVFSZWyvJPGAC0GHk=;
b=lOdRGeh9HUz5CA8nfy09gJ+Rz9IrObehHWtO/+lD8NQATOezn8F0cJwmFeAsCwalY1
zHWgPkwfiI8Aly6v6fFPW4flY/sNSJgaGZr3Ia/DvBFImLQ6sOcNEADw0AVjg0zArOfN
u5wmdEydBEYPR9N2ah0u5gIJjetN04M1Qn6oL9vbUG8+dXInv+a5bhsap9h+HlPM4pRj
kjnO5ZSvntbs2mlLvI94C8QA1CYYYY7ifhzcHFr0G2exzqveFigp7VlBekFywRMGimnP
m/Dguh+rcUYYmdHPkLQTp/+HlQyHuHhyqwRYhW3sOzy1cB0BULSAuuIuFUwBB3MKXfwe
R7YQ==
X-Gm-Message-State: AIVw1137xt6XP6NlvzXgS4uz4js6tFFI8BTP7qh16yVJznMu3ux8NT3r
+hS4oEa95pfokOzwpGd/zPthChGdUw==
X-Received: by 10.237.38.195 with SMTP id q61mr12389515qtd.245.1500040215738;
Fri, 14 Jul 2017 06:50:15 -0700 (PDT)
MIME-Version: 1.0
Sender: earonesty@gmail.com
Received: by 10.200.61.145 with HTTP; Fri, 14 Jul 2017 06:50:14 -0700 (PDT)
In-Reply-To: <CAKzdR-p2F3HLnU7aV7U645mrCOQ5ye4CWSeyzeb0O0j815QAfA@mail.gmail.com>
References: <CAKzdR-qCmuj02yobAj9YDYq7Ed309z2VUaMtbL_i9vF3zkp5mw@mail.gmail.com>
<CAKzdR-oRdX-fXyc6womZOyYyfHUJZdgh92FUMM8pR_QDNiJfkQ@mail.gmail.com>
<CABm2gDo0wgqkEufKn=Z8uAsi=_6fgE=0TS6Bcr21mg3xAX7Kyw@mail.gmail.com>
<7869651.CRYTeDpGy9@strawberry>
<CABm2gDqgve88eE4=dDD8FqGZQNNgRtOvXAhqSTWu_wy4zG+6Eg@mail.gmail.com>
<CAKzdR-p2F3HLnU7aV7U645mrCOQ5ye4CWSeyzeb0O0j815QAfA@mail.gmail.com>
From: Erik Aronesty <erik@q32.com>
Date: Fri, 14 Jul 2017 09:50:14 -0400
X-Google-Sender-Auth: Api6pneDax2wtlRHBC1nCFwwmK4
Message-ID: <CAJowKgKQhpYNsSmdUca7Fnzk=E8op+_Fb9rTkjiM_zBHe8Wcvw@mail.gmail.com>
To: Sergio Demian Lerner <sergio.d.lerner@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="94eb2c071580353f3c0554475468"
X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_LOW,
RCVD_IN_SORBS_SPAM 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: Fri, 14 Jul 2017 13:51:02 +0000
Subject: Re: [bitcoin-dev] A Segwit2x BIP
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: Fri, 14 Jul 2017 13:50:17 -0000
--94eb2c071580353f3c0554475468
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
While BIP91 is probably not terribly harmful, because the vast majority of
nodes and users are prepared for it - the hard fork portion of this BIP is
being deployed like an emergency patch or quick bug fix to the system.
Please consider updating the BIP to include some justification for the
urgency of the consensus change, and the reasons for not delaying until a
better engineered solution (spoonet, BIP103, etc.) can be deployed.
On Thu, Jul 13, 2017 at 3:19 PM, Sergio Demian Lerner via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> The BIP has been updated.
>
> Changes:
> - The technical spec has been improved: now the block size increase is
> specified in terms of weight and not in terms of bytes.
> - The increase in the maximum block sigops after HF has been documented.
> - Comments added about the worst case block size.
>
> Happy weekend! And don't forget to start signaling something before block
> 475776 ! It's just 90 blocks away.
> Bit 1 or 4,1 or whatever you wish, but please signal something.
>
> To the moon!
>
>
> On Wed, Jul 12, 2017 at 2:38 PM, Jorge Tim=C3=B3n via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>>
>>
>> On 12 Jul 2017 2:31 pm, "Tom Zander via bitcoin-dev" <
>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>>
>> On Monday, 10 July 2017 20:38:08 CEST Jorge Tim=C3=B3n via bitcoin-dev w=
rote:
>> > I think anything less than 1 year after release of tested code by some
>> > implementation would be irresponsible for any hardfork, even a very
>> > simple one.
>>
>> Good news!
>>
>> Code to support 2x (the hard fork part of the proposal) has been out and
>> tested for much longer than that.
>>
>>
>> Not true. It's different code on top of segwit. The first attempt in btc=
1
>> (very recent) didn't even increased the size (because it changed the
>> meaningless "base size" without touching the weight limit. As for the
>> current code, I don't think it has been properly tested today, let alone
>> "for mucj longer than 1 year.
>> Anyway, I said, one year from tested release. Segwitx2 hasn't been
>> released, has it? If so, too late to discuss a bip imo, the bip may end =
up
>> being different from what has been released due to feedback (unless it i=
s
>> ignored again, of course).
>>
>>
>> --
>> Tom Zander
>> Blog: https://zander.github.io
>> Vlog: https://vimeo.com/channels/tomscryptochannel
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--94eb2c071580353f3c0554475468
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>While BIP91 is probably not terribly harmful, because=
the vast majority of nodes and users are prepared for it - the hard fork p=
ortion of this BIP is being deployed like an emergency patch or quick bug f=
ix to the system.=C2=A0 <br><br>Please consider updating the BIP to include=
some justification for the urgency of the consensus change, and the reason=
s for not delaying until a better engineered solution (spoonet, BIP103, etc=
.) can be deployed.<br><br></div><div></div></div><div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">On Thu, Jul 13, 2017 at 3:19 PM, Sergio De=
mian Lerner via bitcoin-dev <span dir=3D"ltr"><<a href=3D"mailto:bitcoin=
-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfo=
undation.org</a>></span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div d=
ir=3D"ltr">The BIP has been updated.<div><br></div><div>Changes:<br><div>- =
The technical spec has been improved: now the block size increase is specif=
ied in terms of weight and not in terms of bytes.</div><div>- The increase =
in the maximum block sigops after HF has been documented.</div><div>- Comme=
nts added about the worst case block size.</div><div><br></div><div>Happy w=
eekend! And don't forget to start signaling something before block 4757=
76 !=C2=A0 It's just 90 blocks away.</div><div>Bit 1 or 4,1 or whatever=
you wish, but please signal something.</div><div><br></div><div>To the moo=
n!</div><div><br></div></div></div><div class=3D"HOEnZb"><div class=3D"h5">=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Jul 12, 2=
017 at 2:38 PM, Jorge Tim=C3=B3n via bitcoin-dev <span dir=3D"ltr"><<a h=
ref=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitc=
oin-dev@lists.<wbr>linuxfoundation.org</a>></span> wrote:<br><blockquote=
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div dir=3D"auto"><span><div><br><div class=3D"gmail_ex=
tra"><br><div class=3D"gmail_quote">On 12 Jul 2017 2:31 pm, "Tom Zande=
r via bitcoin-dev" <<a href=3D"mailto:bitcoin-dev@lists.linuxfounda=
tion.org" target=3D"_blank">bitcoin-dev@lists.linuxfounda<wbr>tion.org</a>&=
gt; wrote:<br type=3D"attribution"><blockquote class=3D"m_21022391466156851=
30m_7641680335976316197quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div class=3D"m_2102239146615685130m_76416803359=
76316197quoted-text">On Monday, 10 July 2017 20:38:08 CEST Jorge Tim=C3=B3n=
via bitcoin-dev wrote:<br>
> I think anything less than 1 year after release of tested code by some=
<br>
> implementation would be irresponsible for any hardfork, even a very<br=
>
> simple one.<br>
<br>
</div>Good news!<br>
<br>
Code to support 2x (the hard fork part of the proposal) has been out and<br=
>
tested for much longer than that.<br></blockquote></div></div></div><div di=
r=3D"auto"><br></div></span><div dir=3D"auto">Not true. It's different =
code on top of segwit. The first attempt in btc1 (very recent) didn't e=
ven increased the size (because it changed the meaningless "base size&=
quot; without touching the weight limit. As for the current code, I don'=
;t think it has been properly tested today, let alone "for mucj longer=
than 1 year.</div><div dir=3D"auto">Anyway, I said, one year from tested r=
elease. Segwitx2 hasn't been released, has it? If so, too late to discu=
ss a bip imo, the bip may end up being different from what has been release=
d due to feedback (unless it is ignored again, of course).</div><span><div =
dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto"><div c=
lass=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"m_2102=
239146615685130m_7641680335976316197quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<font color=3D"#888888">--<br>
Tom Zander<br>
Blog: <a href=3D"https://zander.github.io" rel=3D"noreferrer" target=3D"_bl=
ank">https://zander.github.io</a><br>
Vlog: <a href=3D"https://vimeo.com/channels/tomscryptochannel" rel=3D"noref=
errer" target=3D"_blank">https://vimeo.com/channels/tom<wbr>scryptochannel<=
/a><br>
</font><div class=3D"m_2102239146615685130m_7641680335976316197elided-text"=
>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-d<wbr>ev</a><br>
</div></blockquote></div><br></div></div></span></div>
<br>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-d<wbr>ev</a><br>
<br></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
<br></blockquote></div><br></div>
--94eb2c071580353f3c0554475468--
|
