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
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 007B6A8C
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 22 Sep 2016 18:27:39 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail149095.authsmtp.com (outmail149095.authsmtp.com
[62.13.149.95])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 465FD17B
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 22 Sep 2016 18:27:38 +0000 (UTC)
Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232])
by punt24.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u8MIRYKc042404;
Thu, 22 Sep 2016 19:27:34 +0100 (BST)
Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com
[52.5.185.120]) (authenticated bits=0)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u8MIRTif038116
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Thu, 22 Sep 2016 19:27:30 +0100 (BST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by petertodd.org (Postfix) with ESMTPSA id 3A888400E2;
Thu, 22 Sep 2016 18:23:45 +0000 (UTC)
Received: by localhost (Postfix, from userid 1000)
id 35C3C202D6; Thu, 22 Sep 2016 14:27:29 -0400 (EDT)
Date: Thu, 22 Sep 2016 14:27:29 -0400
From: Peter Todd <pete@petertodd.org>
To: Tom <tomz@freedommail.ch>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20160922182729.GA19254@fedora-21-dvm>
References: <CAKEeUhjisp8qdXDNz3C+pB1MUTfvmHZPmsE-f0DVTxnph6NmMQ@mail.gmail.com>
<1530052.vkWv7VPOpL@garp>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu"
Content-Disposition: inline
In-Reply-To: <1530052.vkWv7VPOpL@garp>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Server-Quench: 3937f526-80f2-11e6-829e-00151795d556
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdAAUC1AEAgsB AmAbWl1eUlp7WmI7 bghPaBtcak9QXgdq
T0pMXVMcUQ0VeH5l X0geURFzdgMIcX15 bAhhV3NcCkF4c1t1
QhhWCGwHMGF9YGIW BV1YdwJRcQRDe0tA b1YxNiYHcQ5VPz4z
GA41ejw8IwAXEilM XwwWMVMUTg4hPwZ0 TgsZHDopGEADW3Z7
ARgrOl8WGEtZDl87 N0AoUk4ZNBkJTGUA
X-Authentic-SMTP: 61633532353630.1037:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 52.5.185.120/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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] Requesting BIP assignment; Flexible Transactions.
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Thu, 22 Sep 2016 18:27:39 -0000
--sdtB3X0nJg68CQEu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Sep 22, 2016 at 10:47:03AM +0200, Tom via bitcoin-dev wrote:
> On Wednesday 21 Sep 2016 18:45:55 adiabat via bitcoin-dev wrote:
> > Hi-
> >=20
> > One concern is that this doesn't seem compatible with Lightning as
> > currently written. Most relevant is that non-cooperative channel close
> > transactions in Lightning use OP_CHECKSEQUENCEVERIFY, which references =
the
> > sequence field of the txin; if the txin doesn't have a sequence number,
> > OP_CHECKSEQUENCEVERIFY can't work.
> >=20
> > LockByBlock and LockByTime aren't described and there doesn't seem to be
> > code for them in the PR (186). If there's a way to make OP_CLTV and OP=
_CSV
> > work with this new format, please let us know, thanks!
>=20
> LockByBlock and LockByTime are still TODOs because I didn't have time to =
go
> in-dept into how BIP68 does the encoding.
> The intent is that these tags, while loading, will set the sequence integ=
er in=20
> the txin as the old version does. And while saving we do the reverse.
>=20
> In other words; the lack of sequence number in the saved format doesn't a=
ffect=20
> the in-memory format of the transaction. The in-memory version is the one=
that=20
> script will operate on.
>=20
> This means that there is no change in how CSV will work before and after =
on=20
> any level other than serialisation.
CSV uses per-input sequence numbers; you only have a per-tx equivalent.
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--sdtB3X0nJg68CQEu
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJX5CKOAAoJEGOZARBE6K+yfjkH/iYgD6x+4sbFeW+AhGeotBq/
/IfNzLMfMqM9bZuqmB9xLOhYo3TVRkdNPM/BPBz+JntLqRKM8idMHS9tsthuSRDM
0n5EfFbA9SGooOKzd1+NYAWuiT5IeOM4o0cOEstFEvd2l95ImolRlnpSgutELlNC
cpgRhGVAYHVS3iXF6F0uOMqd2uQ53rzFCio8bKXKdW9Q9totFcovDPVZZYVXrA/E
F/z3wtRRIg8iotPv4nPkcHsxRvKl4gHyBYrIZBmcUM0sqps9HmkvQNwsSNUOqqk5
qH2gteriqXSbhCxCmYrv2svX4dX1M+Tqe7USmIEkk09L++bfNBcZQDXl2Basi4w=
=djps
-----END PGP SIGNATURE-----
--sdtB3X0nJg68CQEu--
|
