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
|
Return-Path: <elombrozo@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 8D47C15C5
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Sep 2015 12:44:47 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com
[209.85.220.43])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C963D1CA
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Sep 2015 12:44:46 +0000 (UTC)
Received: by pablk4 with SMTP id lk4so77135895pab.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 28 Sep 2015 05:44:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=user-agent:in-reply-to:references:mime-version:content-type
:content-transfer-encoding:subject:from:date:to:cc:message-id;
bh=WkkJdikRlCCwdolzXzy/ity4h6MZn8yll5eRqt6og/w=;
b=vAKJHULee7JtEkwncQmn7g4LExjDy5cf5XQjSN5fh5/dBbor0VXZEA5YaaPD5JEq9Y
hLYyQsX9++aSkKgUXobJ2xLit+F+b25yoBjPu3QG4YZD1SG2CtriZEVJuiR7b71aq2z3
mD5E4y3jbggGyt4OR1FoWQKznigZsxFH+0nhkWAY7wdBci48iQPqeLaxo6MEq4rguh/8
6apJi5xZimCoxVqGne+E+pX0GdK4QUhlhFUjcDjdjrN3csGIeJlbs+F8geFV43sf3Upf
hRXsAVug6kXz0anV1MM/LmbrbhJiQvnNptRximTmJ3qlFgEE1V8en2LLHAC5hE0VQmFG
yM/Q==
X-Received: by 10.66.237.6 with SMTP id uy6mr26128764pac.129.1443444286517;
Mon, 28 Sep 2015 05:44:46 -0700 (PDT)
Received: from [192.168.1.100] (cpe-76-167-237-202.san.res.rr.com.
[76.167.237.202])
by smtp.gmail.com with ESMTPSA id oq9sm5177057pbb.0.2015.09.28.05.44.45
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 28 Sep 2015 05:44:45 -0700 (PDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <CA+w+GKSm2Np92+NA77nNMB5LqSyO0=W8dziiMtGO=Jf+7KidHQ@mail.gmail.com>
References: <20150927185031.GA20599@savin.petertodd.org>
<CA+w+GKRCVr-9TVk66utp7xLRgTxNpxYoj3XQE-6y_N8JS6eO6Q@mail.gmail.com>
<CALqxMTFEme9gYHTAVVLtFc4JCK4hoBLXEhMCRdEXK9cWso_pUA@mail.gmail.com>
<CA+w+GKQ8xos6S_BBMqZy6wieFCG=eNxahKXrx3mVKuZcxzjruw@mail.gmail.com>
<4965E9A0-0FF1-4A3F-9165-A21AF976E229@gmail.com>
<CA+w+GKSm2Np92+NA77nNMB5LqSyO0=W8dziiMtGO=Jf+7KidHQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----E0ORFEWPSMSAL1KIO9B2BPQDDZUGB1"
Content-Transfer-Encoding: 8bit
From: Eric Lombrozo <elombrozo@gmail.com>
Date: Mon, 28 Sep 2015 05:44:52 -0700
To: Mike Hearn <hearn@vinumeris.com>
Message-ID: <C0E61EA6-76BE-45E0-8983-A3BC26CC64CF@gmail.com>
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,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
Cc: Mike Hearn via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.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 12:44:47 -0000
------E0ORFEWPSMSAL1KIO9B2BPQDDZUGB1
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
charset=UTF-8
SPV wallets in their current form are inherently insecure. Moreover, while we at least have a soft fork mechanism that is not trivially exploitable (yes, it's got issues...but unlike SPV wallets, it isn't so easily exploitable), we have NO hard fork mechanism in place that isn't highly prone to systemic consensus failure.
But I think pretty much anyone who hasn't been in a coma for the last several years knows this...and I'll stop repeating the obvious.
On September 28, 2015 5:26:17 AM PDT, Mike Hearn <hearn@vinumeris.com> wrote:
>>
>> Go ahead and object to soft forks...but at least try not to make
>arguments
>> based on changing the definitions of terms we all generally agree
>upon.
>>
>
>I don't intend to do that, and I don't think I am - I know what the
>difference between a soft and hard fork is and am not trying to confuse
>or
>blur the two.
>
>To reiterate: this current BIP implements a soft fork. I am not
>debating
>that. I am saying it should use a hard fork instead. This will ensure
>no
>repeat of the P2SH case where invalid blocks were being found for weeks
>(or
>was it months?) after the new rules kicked in, thus exposing SPV
>wallets
>and old nodes to unnecessary risk for no benefit.
>
>Additionally, I am making it clear that there's no consensus for
>rolling
>out the new opcode in this way. As you say, the mechanism has issues.
>If
>you read the comments when I wrote my article, you can see that others
>share the same concerns:
>
>https://www.reddit.com/r/Bitcoin/comments/3griiv/on_consensus_and_forks_by_mike_hearn
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
------E0ORFEWPSMSAL1KIO9B2BPQDDZUGB1
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: 8bit
<html><head></head><body>SPV wallets in their current form are inherently insecure. Moreover, while we at least have a soft fork mechanism that is not trivially exploitable (yes, it's got issues...but unlike SPV wallets, it isn't so easily exploitable), we have NO hard fork mechanism in place that isn't highly prone to systemic consensus failure.<br>
<br>
But I think pretty much anyone who hasn't been in a coma for the last several years knows this...and I'll stop repeating the obvious.<br><br><div class="gmail_quote">On September 28, 2015 5:26:17 AM PDT, Mike Hearn <hearn@vinumeris.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>Go ahead and object to soft forks...but at least try not to make arguments based on changing the definitions of terms we all generally agree upon.</div></blockquote><div><br /></div><div>I don't intend to do that, and I don't think I am - I know what the difference between a soft and hard fork is and am not trying to confuse or blur the two.</div><div><br /></div><div>To reiterate: this current BIP implements a soft fork. I am not debating that. I am saying it should use a hard fork instead. This will ensure no repeat of the P2SH case where invalid blocks were being found for weeks (or was it months?) after the new rules kicked in, thus exposing SPV wallets and old nodes to unnecessary risk for no benefit.</div><div><br /></div><div>Additi
onally,
I am making it clear that there's no consensus for rolling out the new opcode in this way. As you say, the mechanism has issues. If you read the comments when I wrote my article, you can see that others share the same concerns:</div><div><br /></div><div><a href="https://www.reddit.com/r/Bitcoin/comments/3griiv/on_consensus_and_forks_by_mike_hearn">https://www.reddit.com/r/Bitcoin/comments/3griiv/on_consensus_and_forks_by_mike_hearn</a><br /></div><div><br /></div><div><br /></div></div></div></div>
</blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>
------E0ORFEWPSMSAL1KIO9B2BPQDDZUGB1--
|
