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
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 04C17D77
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 17 May 2018 10:29:05 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-1857040132.protonmail.ch (mail-1857040132.protonmail.ch
[185.70.40.132])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2B31C196
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 17 May 2018 10:29:03 +0000 (UTC)
Date: Thu, 17 May 2018 06:28:54 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=default; t=1526552941;
bh=b2usWU8VxDKVqqnOkTyx/onWqc9i5kzyG5ucnyr0UU8=;
h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:
Feedback-ID:From;
b=vueJenIrFTpslwGIs5p0n5X2VhP2ZKM6KQlGNRmJDUhptngVTyUvZ24qvktzteVzQ
KnuuKm5t6hRfO8y2tOxQ7QpLqxptmLfQuT4xoV5xwnx3he54I9zH9JsAAMQ3tihGMb
UZI/1vE2DpMcSQrZgggXdLoVws2RHQkRbQBXuUlg=
To: Rusty Russell <rusty@rustcorp.com.au>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <bGnScyqXi6LMbsqtc8l3DDTfibYhKd30y-Urd28iImu-gK2hBKYPLpkkbit18RkYlmakzoJAVqKyqL5bw_By_AdXJJd1r3QrLjH1W6igKPM=@protonmail.com>
In-Reply-To: <87vabnq9ui.fsf@rustcorp.com.au>
References: <87po25lmzs.fsf@rustcorp.com.au>
<201805100227.42217.luke@dashjr.org>
<87vabnq9ui.fsf@rustcorp.com.au>
Feedback-ID: el4j0RWPRERue64lIQeq9Y2FP-mdB86tFqjmrJyEPR9VAtMovPEo9tvgA0CrTsSHJeeyPXqnoAu6DN-R04uJUg==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
FROM_LOCAL_NOVOWEL autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 17 May 2018 12:07:20 +0000
Subject: Re: [bitcoin-dev] Making OP_TRUE standard?
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, 17 May 2018 10:29:05 -0000
Good morning Rusty and list,
> Your zero-val-OP_TRUE-can't-be-spent-after-same-block SF is interesting,
>=20
> but if we want a SF just give us SIGHASH_NOINPUT and we'll not need this
>=20
> at all (though others still might).
We might still want this in general in Lightning; for instance we could mak=
e every funding transaction include such an output. If it turns out, our i=
nitial feerate estimate for the funding transaction is low, we can use the =
`OP_TRUE` for fee-bumping. This is a win for Lightning since the funding t=
ransaction ID remains the same (even in Decker-Russell-Osuntokun, the trigg=
er transaction is signed with `SIGHASH_ALL`, and refers to a fixed funding =
transaction ID).
Without the `OP_TRUE`-for-fee-bump, we would have to pretend to open a new =
different channel and RBF the old funding transaction with a new higher-fee=
rate funding transaction, then keep track of which one gets confirmed deepl=
y (there is a race where a miner discovers a block using the older funding =
transaction before our broadcast of the new funding transaction reaches it)=
.
(we could also feebump using the change output of the funding transaction, =
but such a change output might not exist for all funding transactions.)
Regards,
ZmnSCPxj
|
