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
|
Return-Path: <rusty@ozlabs.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 4A89DAF8
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 May 2018 02:13:08 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from ozlabs.org (ozlabs.org [203.11.71.1])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6E9526B1
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 May 2018 02:13:07 +0000 (UTC)
Received: by ozlabs.org (Postfix, from userid 1011)
id 40hGwJ5ZnWz9s4Z; Thu, 10 May 2018 12:13:04 +1000 (AEST)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Johnson Lau <jl2012@xbt.hk>,
bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <F8C553EE-9AF5-4348-90B7-3EC55FC46B4C@xbt.hk>
References: <87po25lmzs.fsf@rustcorp.com.au>
<F8C553EE-9AF5-4348-90B7-3EC55FC46B4C@xbt.hk>
Date: Thu, 10 May 2018 11:36:41 +0930
Message-ID: <87bmdoe026.fsf@rustcorp.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 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: Thu, 10 May 2018 02:13:08 -0000
Johnson Lau <jl2012@xbt.hk> writes:
> 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
That won't propagate :(
> 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.
No, that would change the TXID, which we rely on for HTLC transactions.
> In long-term, I think the right way is to have a more flexible SIGHASH sy=
stem to allow people to add more inputs and outputs easily.
Agreed:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-April/015862.h=
tml
But in the long term we'll have Eltoo and SIGHASH_NOINPUT which both
allow different solutions.
Cheers,
Rusty.
|
