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)
Subject: Re: [bitcoin-dev] Requesting BIP assignment; Flexible Transactions.
Precedence: list


--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--