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
|
Return-Path: <jl2012@xbt.hk>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 20C747F6
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 May 2018 18:12:13 +0000 (UTC)
X-Greylist: delayed 00:15:11 by SQLgrey-1.7.6
Received: from sender-of-o51.zoho.com (sender-of-o51.zoho.com [135.84.80.216])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 55F9067F
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 May 2018 18:12:12 +0000 (UTC)
Received: from [10.8.0.103] (n219073055009.netvigator.com [219.73.55.9]) by
mx.zohomail.com with SMTPS id 1525888609850828.2410265889255;
Wed, 9 May 2018 10:56:49 -0700 (PDT)
From: Johnson Lau <jl2012@xbt.hk>
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 10 May 2018 01:56:46 +0800
References: <87po25lmzs.fsf@rustcorp.com.au>
To: Rusty Russell <rusty@rustcorp.com.au>,
bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <87po25lmzs.fsf@rustcorp.com.au>
Message-Id: <F8C553EE-9AF5-4348-90B7-3EC55FC46B4C@xbt.hk>
X-Mailer: Apple Mail (2.3445.5.20)
X-ZohoMailClient: External
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,MIME_QP_LONG_LINE,
RCVD_IN_DNSWL_NONE 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] 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: Wed, 09 May 2018 18:12:13 -0000
You should make a =E2=80=9C0 fee tx with exactly one OP_TRUE output=E2=80=9D=
standard, but nothing else. This makes sure CPFP will always be needed, =
so the OP_TRUE output won=E2=80=99t pollute the UTXO set
Instead, would you consider to use ANYONECANPAY to sign the tx, so it is =
possible add more inputs for fees? The total tx size is bigger than the =
OP_TRUE approach, but you don=E2=80=99t need to ask for any protocol =
change.
In long-term, I think the right way is to have a more flexible SIGHASH =
system to allow people to add more inputs and outputs easily.
> On 9 May 2018, at 7:57 AM, Rusty Russell via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>=20
> Hi all,
>=20
> The largest problem we are having today with the lightning
> protocol is trying to predict future fees. Eltoo solves this =
elegantly,
> but meanwhile we would like to include a 546 satoshi OP_TRUE output in
> commitment transactions so that we use minimal fees and then use CPFP
> (which can't be done at the moment due to CSV delays on outputs).
>=20
> Unfortunately, we'd have to P2SH it at the moment as a raw 'OP_TRUE' =
is
> non-standard. Are there any reasons not to suggest such a policy
> change?
>=20
> Thanks!
> Rusty.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
