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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1Yq7W1-0000De-Uv
for bitcoin-development@lists.sourceforge.net;
Wed, 06 May 2015 22:10:05 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.44 as permitted sender)
client-ip=209.85.192.44; envelope-from=tier.nolan@gmail.com;
helo=mail-qg0-f44.google.com;
Received: from mail-qg0-f44.google.com ([209.85.192.44])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Yq7W0-0001eP-SL
for bitcoin-development@lists.sourceforge.net;
Wed, 06 May 2015 22:10:05 +0000
Received: by qgeb100 with SMTP id b100so12210588qge.3
for <bitcoin-development@lists.sourceforge.net>;
Wed, 06 May 2015 15:09:59 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.55.15.15 with SMTP id z15mr2051454qkg.21.1430950199443; Wed,
06 May 2015 15:09:59 -0700 (PDT)
Received: by 10.140.85.241 with HTTP; Wed, 6 May 2015 15:09:59 -0700 (PDT)
In-Reply-To: <CABm2gDpp-tKPa4NtX29FhB5AN9sKcJJ9CboZoaczt2bU2h=5tQ@mail.gmail.com>
References: <20141001130826.GM28710@savin.petertodd.org>
<55075795.20904@bluematt.me>
<20150421075912.GA25282@savin.petertodd.org>
<5546D653.4070404@bluematt.me>
<CABm2gDqcD4ENex3LzKfeGqaotoO-XxLHhLzOEPwk92SaiD8snQ@mail.gmail.com>
<CAE-z3OVrHqK1gyxCimz3ATBV3ojuyBNO-Jj6bzmcxMgfWe9jkg@mail.gmail.com>
<CABm2gDpp-tKPa4NtX29FhB5AN9sKcJJ9CboZoaczt2bU2h=5tQ@mail.gmail.com>
Date: Wed, 6 May 2015 23:09:59 +0100
Message-ID: <CAE-z3OXrrYWGROK1=3zVQxjqzeyYBwa1SGxEMeb4b4V3_S9KfQ@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11475dda54467a0515710e1a
X-Spam-Score: 1.8 (+)
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
(tier.nolan[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
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
1.2 MALFORMED_FREEMAIL Bad headers on message from free email service
X-Headers-End: 1Yq7W0-0001eP-SL
Subject: Re: [Bitcoin-development] Relative CHECKLOCKTIMEVERIFY (was CLTV
proposal)
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, 06 May 2015 22:10:06 -0000
--001a11475dda54467a0515710e1a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Wed, May 6, 2015 at 8:37 AM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrote:
>
> This gives you less flexibility and I don't think it's necessary.
> Please let's try to avoid this if it's possible.
It is just a switch that turns on and off the new mode.
In retrospect, it would be better to just up the transaction version.
In transactions from v2 onwards, the sequence field means height. That
means legacy transactions would be spendable.
This is a pure soft-fork.
--001a11475dda54467a0515710e1a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, May 6, 2015 at 8:37 AM, Jorge Tim=C3=B3n <span dir=3D"ltr"><<a href=
=3D"mailto:jtimon@jtimon.cc" target=3D"_blank">jtimon@jtimon.cc</a>></sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
</span>This gives you less flexibility and I don't think it's neces=
sary.<br>
Please let's try to avoid this if it's possible.</blockquote><div><=
br></div><div>It is just a switch that turns on and off the new mode.<br><b=
r></div><div>In retrospect, it would be better to just up the transaction v=
ersion.=C2=A0 <br><br>In transactions from v2 onwards, the sequence field m=
eans height.=C2=A0 That means legacy transactions would be spendable.<br><b=
r></div><div>This is a pure soft-fork.<br></div></div></div></div>
--001a11475dda54467a0515710e1a--
|
