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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jtimon@jtimon.cc>) id 1Yxenk-0004a9-Cc
for bitcoin-development@lists.sourceforge.net;
Wed, 27 May 2015 17:07:32 +0000
Received: from mail-wg0-f48.google.com ([74.125.82.48])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Yxenj-0004Fj-0E
for bitcoin-development@lists.sourceforge.net;
Wed, 27 May 2015 17:07:32 +0000
Received: by wgme6 with SMTP id e6so15330052wgm.2
for <bitcoin-development@lists.sourceforge.net>;
Wed, 27 May 2015 10:07:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=qWCD7XijP82iYvrsULh0BLgBM9fXm2QoUABoNERn7Gw=;
b=Qf/HYhMDVWXjkJS3ALZrZQrrCq4INemYmD8A15TNnFfG3OcXGaF67hzSNg+55Y339N
ae70BhQSWxgZxb4hF1T29banl2/kidwhUmfhoDgY3LOxuuM0VyNTWKDbpZET/ptXDKBs
+KJKriCpWzmBPakfcQ+lVxtEdee7WpDfkIvyZsDgpk18l2zgkKiVj45n4BNMEME2egUh
zP0HyZHk9GievC48oQHMDTMfcZ6fwokbiq+PJoo319LLh+JmKzetDF2OYEQnIz8KU7rS
Qqwqpxk2Ni5c6HJEZ/fW6HUoBtYBQ1iy+8GuTCvgFBX7+EBDhIlcSyvhTYvFYvh1V3AT
Zesg==
X-Gm-Message-State: ALoCoQm77VsTGtXYl0RkYD4GEQwDyanjCLFKh0DOMf2bJrR+B0IYxuG9/8ruMtrJHm+IJQxilNfJ
MIME-Version: 1.0
X-Received: by 10.194.60.164 with SMTP id i4mr61377695wjr.133.1432746444628;
Wed, 27 May 2015 10:07:24 -0700 (PDT)
Received: by 10.194.127.97 with HTTP; Wed, 27 May 2015 10:07:24 -0700 (PDT)
Received: by 10.194.127.97 with HTTP; Wed, 27 May 2015 10:07:24 -0700 (PDT)
In-Reply-To: <20150527105805.GC25814@savin.petertodd.org>
References: <CAOG=w-sfiUQQGUh=RR55NU-TkAi1+2g3_Z+YP3dGDjp8zXYBGQ@mail.gmail.com>
<20150527074713.GB22286@savin.petertodd.org>
<CAAS2fgSjT-dtS8cNoRjvEhtBeG9SUi4OsKAAGkAf_WkxEyg=9g@mail.gmail.com>
<20150527105805.GC25814@savin.petertodd.org>
Date: Wed, 27 May 2015 19:07:24 +0200
Message-ID: <CABm2gDoOyjWex=j+yro2xspEH-zsdy3iu6Dyx81ziJ8ZvvVj2w@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=047d7ba97f1ae2bae905171346da
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1Yxenj-0004Fj-0E
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Consensus-enforced transaction
replacement via sequence numbers
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, 27 May 2015 17:07:32 -0000
--047d7ba97f1ae2bae905171346da
Content-Type: text/plain; charset=UTF-8
On May 27, 2015 12:58 PM, "Peter Todd" <pete@petertodd.org> wrote:
> What I'm not seeing is how the relative nLockTime that nSequence
> provides fundamentally changes any of this.
This allows the implementation of a rcltv that doesn't make script depend
on the current height, in a similar way that cltv uses the nLockTime (which
has been compared with the current height already when checking the script).
In fact, the implementation could be simpler if the goal of maintaining the
original nSequence semantics was ignored ( although not that simpler, but
you wouldn't need to use ~ (bitwise not).
I'm still not sure whether there should be 2 BIPs for this or just one.
> --
> 'peter'[:-1]@petertodd.org
> 000000000000000001643f7706f3dcbc3a386e4c1bfba852ff628d8024f875b6
>
>
------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7ba97f1ae2bae905171346da
Content-Type: text/html; charset=UTF-8
<p dir="ltr"><br>
On May 27, 2015 12:58 PM, "Peter Todd" <<a href="mailto:pete@petertodd.org">pete@petertodd.org</a>> wrote:</p>
<p dir="ltr">> What I'm not seeing is how the relative nLockTime that nSequence<br>
> provides fundamentally changes any of this.</p>
<p dir="ltr">This allows the implementation of a rcltv that doesn't make script depend on the current height, in a similar way that cltv uses the nLockTime (which has been compared with the current height already when checking the script).<br>
In fact, the implementation could be simpler if the goal of maintaining the original nSequence semantics was ignored ( although not that simpler, but you wouldn't need to use ~ (bitwise not).<br>
I'm still not sure whether there should be 2 BIPs for this or just one.</p>
<p dir="ltr">> --<br>
> 'peter'[:-1]@<a href="http://petertodd.org">petertodd.org</a><br>
> 000000000000000001643f7706f3dcbc3a386e4c1bfba852ff628d8024f875b6<br>
><br>
> ------------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
> <a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
><br>
</p>
--047d7ba97f1ae2bae905171346da--
|
