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
265
266
267
268
269
270
271
272
273
274
275
276
277
|
Return-Path: <dscotese@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 65B6319F6
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Sep 2015 22:16:45 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com
[209.85.212.180])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 57456FD
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Sep 2015 22:16:44 +0000 (UTC)
Received: by wiclk2 with SMTP id lk2so121145356wic.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Sep 2015 15:16:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:date:message-id:subject
:from:to:content-type;
bh=lNzqfo98ggnYaHPyp6zczEi07JRL8/PZ0DfcQlrzGFs=;
b=tBBnBsOFwJTqTjncsSYn9kHnjvNaLWB8+R0CXuLH+D120gKJPDmNoznaM5SatHtXPz
1RFkZdg7Mga2zdnv81VrvK3fq73Ar+eT6r0z6iWwIerlrdhUFRorCYeXbZA+QqfGCV9T
/QIgZMda1GHeeaWGacECdvG1kUuVceuXKgeFbXiiVp9zcp/5jbDQ0zf/WisDVMKQLsOK
ZIetlmoeD15u8dHf+KRZsaX/+t4q6XuWewXwAvcqnF3KNFWUbggt5Y86VGU6Rn2mKy+3
DkaOILhJ8lQL35Z/92OUBdVjWTb60a0JPCD170QanZj3Znn6fbUpLHbi0+TsxXJvp0Zi
cwfA==
MIME-Version: 1.0
X-Received: by 10.194.249.34 with SMTP id yr2mr24195008wjc.90.1443478602899;
Mon, 28 Sep 2015 15:16:42 -0700 (PDT)
Sender: dscotese@gmail.com
Received: by 10.27.211.132 with HTTP; Mon, 28 Sep 2015 15:16:42 -0700 (PDT)
In-Reply-To: <5609AD23.4070305@riseup.net>
References: <20150927185031.GA20599@savin.petertodd.org>
<CA+w+GKRCVr-9TVk66utp7xLRgTxNpxYoj3XQE-6y_N8JS6eO6Q@mail.gmail.com>
<CALqxMTFEme9gYHTAVVLtFc4JCK4hoBLXEhMCRdEXK9cWso_pUA@mail.gmail.com>
<5609AD23.4070305@riseup.net>
Date: Mon, 28 Sep 2015 15:16:42 -0700
X-Google-Sender-Auth: jMm6HC2fCSSf3Z3QRgNsXp2B9as
Message-ID: <CAGLBAhf+9QozWETTd9MS8jP811f9AJxJiAk10orGK8-ZihahqQ@mail.gmail.com>
From: Dave Scotese <dscotese@litmocracy.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11c1b8d25de89c0520d60de2
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Let's deploy BIP65 CHECKLOCKTIMEVERIFY!
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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, 28 Sep 2015 22:16:45 -0000
--001a11c1b8d25de89c0520d60de2
Content-Type: text/plain; charset=UTF-8
Why are they called soft forks when they are really hidden forks? Isn't
the point of a soft fork to prevent old clients from rejecting what they
don't have the code to validate? That seems dangerous.
notplato
On Mon, Sep 28, 2015 at 2:12 PM, odinn via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> And still no movement on BIP 63...
>
> https://bitcointalk.org/index.php?topic=1083961.20
>
> Apart from that,
>
> All my prior objections to XT still hold as expressed on this list.
> XT is not acceptable.
>
> On the topic of consensus:
>
> Reaching consensus, I hope, is something that developers can
> accomplish by refining and adjusting the BIPS and coming to agreement
> upon them. This should be something that can be done in a few months
> time, before the end of the year.
>
> Cheers,
>
> - - O
>
> Adam Back via bitcoin-dev:
> > I wonder what Gavin's views are, he's usually constructive, and see
> > if he'll include it in XT - I think he may have said he was
> > supportive.
> >
> > The rationale for soft vs hard-forks is well known, so I wont go
> > over them.
> >
> > Adam
> >
> >
> > On 28 September 2015 at 06:48, Mike Hearn via bitcoin-dev
> > <bitcoin-dev@lists.linuxfoundation.org> wrote:
> >> There is no consensus on using a soft fork to deploy this
> >> feature. It will result in the same problems as all the other
> >> soft forks - SPV wallets will become less reliable during the
> >> rollout period. I am against that, as it's entirely avoidable.
> >>
> >> Make it a hard fork and my objection will be dropped.
> >>
> >> Until then, as there is no consensus, you need to do one of two
> >> things:
> >>
> >> 1) Drop the "everyone must agree to make changes" idea that
> >> people here like to peddle, and do it loudly, so everyone in the
> >> community is correctly informed
> >>
> >> 2) Do nothing
> >>
> >>
> >>
> >> _______________________________________________ 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
> >
>
> - --
> http://abis.io ~
> "a protocol concept to enable decentralization
> and expansion of a giving economy, and a new social good"
> https://keybase.io/odinn
> -----BEGIN PGP SIGNATURE-----
>
> iQEcBAEBCgAGBQJWCa0jAAoJEGxwq/inSG8CuCUIALiRt6cE3b+9f+l9m6aMTjIR
> vTEIM/7B4dIZW9eatXmkxyd44uz5YoN93SlZtV62c90HCqqpFRBCfyXRyXzQ11E7
> 0i70or5LnWDOqrD1bSsCEdrQxPIpAQnv101UHe3iyn/uHAVBiz/HfqvGMruNt0r1
> 4sMecp+LedWpy6/p9c6iMHV1rhtYRfmRfJHj+9KlSn+in5PQKx2kieWqpfqjmlNs
> J/UNoLvRuF0YxDcqEdp2BAaI0s+NyXBo3YDi4R77U9YPRj/cYuWHh/yPKAvFW+2K
> 0d9NNuKSKEY/m4uW3ghPEJL7OxlGbOoNWFS3kcKYr+BanfsPTov7yHQhBuRBRPw=
> =hd0W
> -----END PGP SIGNATURE-----
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a11c1b8d25de89c0520d60de2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Why are they called soft forks when they are really h=
idden forks?<i></i>=C2=A0 Isn't the point of a soft fork to prevent old=
clients from rejecting what they don't have the code to validate?=C2=
=A0 That seems dangerous.<br></div><div><br></div>notplato<br><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Sep 28, 2015 at 2:12 P=
M, odinn via bitcoin-dev <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-de=
v@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfound=
ation.org</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEG=
IN PGP SIGNED MESSAGE-----<br>
Hash: SHA512<br>
<br>
And still no movement on BIP 63...<br>
<br>
<a href=3D"https://bitcointalk.org/index.php?topic=3D1083961.20" rel=3D"nor=
eferrer" target=3D"_blank">https://bitcointalk.org/index.php?topic=3D108396=
1.20</a><br>
<br>
Apart from that,<br>
<br>
All my prior objections to XT still hold as expressed on this list.<br>
XT is not acceptable.<br>
<br>
On the topic of consensus:<br>
<br>
Reaching consensus, I hope, is something that developers can<br>
accomplish by refining and adjusting the BIPS and coming to agreement<br>
upon them.=C2=A0 This should be something that can be done in a few months<=
br>
time, before the end of the year.<br>
<br>
Cheers,<br>
<br>
- - O<br>
<br>
Adam Back via bitcoin-dev:<br>
<div><div class=3D"h5">> I wonder what Gavin's views are, he's u=
sually constructive, and see<br>
> if he'll include it in XT - I think he may have said he was<br>
> supportive.<br>
><br>
> The rationale for soft vs hard-forks is well known, so I wont go<br>
> over them.<br>
><br>
> Adam<br>
><br>
><br>
> On 28 September 2015 at 06:48, Mike Hearn via bitcoin-dev<br>
> <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-d=
ev@lists.linuxfoundation.org</a>> wrote:<br>
>> There is no consensus on using a soft fork to deploy this<br>
>> feature. It will result in the same problems as all the other<br>
>> soft forks - SPV wallets will become less reliable during the<br>
>> rollout period. I am against that, as it's entirely avoidable.=
<br>
>><br>
>> Make it a hard fork and my objection will be dropped.<br>
>><br>
>> Until then, as there is no consensus, you need to do one of two<br=
>
>> things:<br>
>><br>
>> 1) Drop the "everyone must agree to make changes" idea t=
hat<br>
>> people here like to peddle, and do it loudly, so everyone in the<b=
r>
>> community is correctly informed<br>
>><br>
>> 2) Do nothing<br>
>><br>
>><br>
>><br>
>> _______________________________________________ bitcoin-dev<br>
>> mailing list <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.o=
rg">bitcoin-dev@lists.linuxfoundation.org</a><br>
>> <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitc=
oin-dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation=
.org/mailman/listinfo/bitcoin-dev</a><br>
>><br>
> _______________________________________________ bitcoin-dev mailing<br=
>
> list <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-=
dev@lists.linuxfoundation.org</a><br>
> <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org=
/mailman/listinfo/bitcoin-dev</a><br>
><br>
<br>
</div></div>- --<br>
<a href=3D"http://abis.io" rel=3D"noreferrer" target=3D"_blank">http://abis=
.io</a> ~<br>
"a protocol concept to enable decentralization<br>
and expansion of a giving economy, and a new social good"<br>
<a href=3D"https://keybase.io/odinn" rel=3D"noreferrer" target=3D"_blank">h=
ttps://keybase.io/odinn</a><br>
-----BEGIN PGP SIGNATURE-----<br>
<br>
iQEcBAEBCgAGBQJWCa0jAAoJEGxwq/inSG8CuCUIALiRt6cE3b+9f+l9m6aMTjIR<br>
vTEIM/7B4dIZW9eatXmkxyd44uz5YoN93SlZtV62c90HCqqpFRBCfyXRyXzQ11E7<br>
0i70or5LnWDOqrD1bSsCEdrQxPIpAQnv101UHe3iyn/uHAVBiz/HfqvGMruNt0r1<br>
4sMecp+LedWpy6/p9c6iMHV1rhtYRfmRfJHj+9KlSn+in5PQKx2kieWqpfqjmlNs<br>
J/UNoLvRuF0YxDcqEdp2BAaI0s+NyXBo3YDi4R77U9YPRj/cYuWHh/yPKAvFW+2K<br>
0d9NNuKSKEY/m4uW3ghPEJL7OxlGbOoNWFS3kcKYr+BanfsPTov7yHQhBuRBRPw=3D<br>
=3Dhd0W<br>
-----END PGP SIGNATURE-----<br>
<div class=3D"HOEnZb"><div class=3D"h5">___________________________________=
____________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br><br></div></div>
--001a11c1b8d25de89c0520d60de2--
|
