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
|
Return-Path: <rx@awsomnet.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 3D221B14
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Sep 2016 22:45:57 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f181.google.com (mail-io0-f181.google.com
[209.85.223.181])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C3640157
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Sep 2016 22:45:56 +0000 (UTC)
Received: by mail-io0-f181.google.com with SMTP id m186so68211259ioa.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Sep 2016 15:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=awsomnet-org.20150623.gappssmtp.com; s=20150623;
h=mime-version:from:date:message-id:subject:to;
bh=WILIIFyR7590bUKrVNGPVqNkNjTr0Hsj0ShZVrM7GWY=;
b=BWEIDPe0QSqJfYDf9HD3opeVcTEydQJUgR5lfIgWatjtoQU2XXujnDES53NZjwYTbm
g1b4ut2xIeNNn8KSHCSi7hmWxPSfu+EA8GtMiJSmZf4mGyS8QEeyr6c/Cd+hikvM4HWK
zPrN0HiDoj69mWK2c4Q2b7bZ805/juQNjfAKdwESztx/xxg480qf5h2JBzsp6wpOSxJp
hileQmG6uyM9kdVXKhyLOQ7MAMQxxstLa3/RSF+fWrMvW5wgVWHBl6bmFpyU6K5LrXx+
heyV5TNv4AHjgJT97W9noLBjHckZUnEhliswCFxXZR9rP9QWDYkQ2WiAD7A04tZknNJh
ysBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=WILIIFyR7590bUKrVNGPVqNkNjTr0Hsj0ShZVrM7GWY=;
b=S6/VEwAOWEfUhfG5qG7x/XeuoQtSZoZQAHumgdQHMkru8isduKlVH8KG9QVnsDko/D
uWJWcfscJJor/EpN9gEcBvdh9ILwXS8eTpA9NpbdMEEW8jFDUwb/0LYHWu1juQEVxY3/
3V6p3xI16AJn6rBXMmFj2SFE74E3vV9/VR6Y/qfrAG8E59IvtokbO9pQRpw2dXQJr57N
59SvcA30KGi9xeO+e3FVlfpnbfit4bj7w+iuR/mXHNdc6ClmBbQpjvgVkelOv0UI6mNn
aN0M4rafpChGddlzqWolLlIkmVJBsHoxc112d2fWDRVXqlqs6SJBQ5ahk70kuUYCiHTv
Xehw==
X-Gm-Message-State: AE9vXwOJ9zjjP05kdXLh9+SjGBYF9x1TP5VzOLHI8A5kAQX3lC9PtXO8viuyb5CORDq9xj+vRGTuxxtF9Gsn3g==
X-Received: by 10.107.31.21 with SMTP id f21mr57970626iof.5.1474497956184;
Wed, 21 Sep 2016 15:45:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.26.202 with HTTP; Wed, 21 Sep 2016 15:45:55 -0700 (PDT)
X-Originating-IP: [100.38.11.146]
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
X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, HTML_MESSAGE, RCVD_IN_DNSWL_NONE,
RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 21 Sep 2016 23:14:04 +0000
Subject: [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: Wed, 21 Sep 2016 22:45:57 -0000
--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'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't=20
have a sequence number, OP_CHECKSEQUENCEVERIFY can't work.=C2=A0 <br><b=
r>LockByBlock
and LockByTime aren't described and there doesn't seem to be code =
for=20
them in the PR (186).=C2=A0 If there'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--
|
