MIME-Version: 1.0
From: adiabat <rx@awsomnet.org>
Date: Wed, 21 Sep 2016 18:45:55 -0400
Message-ID: <CAKEeUhjisp8qdXDNz3C+pB1MUTfvmHZPmsE-f0DVTxnph6NmMQ@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a11402ef2e6a9ad053d0c4e44
Subject: [bitcoin-dev]  Requesting BIP assignment; Flexible Transactions.
Precedence: list

--001a11402ef2e6a9ad053d0c4e44
Content-Type: text/plain; charset=UTF-8

Hi-

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.

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!

-Tadge

--001a11402ef2e6a9ad053d0c4e44
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi-<br><br>One concern is that this doesn&#39;t seem compa=
tible with=20
Lightning as currently written.=C2=A0 Most relevant is that non-cooperative=
=20
channel close transactions in Lightning use OP_CHECKSEQUENCEVERIFY,=20
which references the sequence field of the txin; if the txin doesn&#39;t=20
have a sequence number, OP_CHECKSEQUENCEVERIFY can&#39;t work.=C2=A0 <br><b=
r>LockByBlock
 and LockByTime aren&#39;t described and there doesn&#39;t seem to be code =
for=20
them in the PR (186).=C2=A0 If there&#39;s a way to make OP_CLTV and OP_CSV=
 work=20
with this new format, please let us know, thanks!<br><br>-Tadge</div>

--001a11402ef2e6a9ad053d0c4e44--