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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1XZLPL-0005FF-NN
for bitcoin-development@lists.sourceforge.net;
Wed, 01 Oct 2014 15:01:35 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.178 as permitted sender)
client-ip=209.85.160.178; envelope-from=gavinandresen@gmail.com;
helo=mail-yk0-f178.google.com;
Received: from mail-yk0-f178.google.com ([209.85.160.178])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XZLPJ-0002En-Rq
for bitcoin-development@lists.sourceforge.net;
Wed, 01 Oct 2014 15:01:35 +0000
Received: by mail-yk0-f178.google.com with SMTP id 9so187892ykp.9
for <bitcoin-development@lists.sourceforge.net>;
Wed, 01 Oct 2014 08:01:28 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.206.166 with SMTP id l26mr84962451yho.18.1412175688419;
Wed, 01 Oct 2014 08:01:28 -0700 (PDT)
Received: by 10.170.188.23 with HTTP; Wed, 1 Oct 2014 08:01:28 -0700 (PDT)
In-Reply-To: <20141001130826.GM28710@savin.petertodd.org>
References: <20141001130826.GM28710@savin.petertodd.org>
Date: Wed, 1 Oct 2014 11:01:28 -0400
Message-ID: <CABsx9T0M0Xc4_rXptTS7PqoQW+KhrtdF_PGEsp5Ce2VS+7J91g@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=bcaec508f27244d18e05045dc6eb
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1XZLPJ-0002En-Rq
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [BIP draft] CHECKLOCKTIMEVERIFY - Prevent
a txout from being spent until an expiration time
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 01 Oct 2014 15:01:35 -0000
--bcaec508f27244d18e05045dc6eb
Content-Type: text/plain; charset=ISO-8859-1
Very nice, semantics are clear and use cases are compelling.
Can we defer discussion of how to roll this out for a little bit, and see
if there is consensus that:
a) benefits of having this outweigh risks
b) we're all happy with exact semantics
Then we can have a knock-down drag-out argument about whether it should
roll out as a soft fork, wait for a hard fork, be combined with some other
things that it would be nice to add or change, etc.....
--
--
Gavin Andresen
--bcaec508f27244d18e05045dc6eb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra">Very nice, semantics are clear =
and use cases are compelling.</div><div class=3D"gmail_extra"><br></div><di=
v class=3D"gmail_extra">Can we defer discussion of how to roll this out for=
a little bit, and see if there is consensus that:</div><div class=3D"gmail=
_extra"><br></div><div class=3D"gmail_extra">a) benefits of having this out=
weigh risks</div><div class=3D"gmail_extra">b) we're all happy with exa=
ct semantics</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_=
extra">Then we can have a knock-down drag-out argument about whether it sho=
uld roll out as a soft fork, wait for a hard fork, be combined with some ot=
her things that it would be nice to add or change, etc.....</div><div class=
=3D"gmail_extra"><br></div><div class=3D"gmail_extra">-- <br>--<br>Gavin An=
dresen<br>
</div></div>
--bcaec508f27244d18e05045dc6eb--
|
