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
104
105
106
107
108
109
110
111
112
113
|
Return-Path: <user@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id AE905BCF
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 May 2018 19:45:11 +0000 (UTC)
X-Greylist: delayed 00:17:31 by SQLgrey-1.7.6
Received: from outmail148113.authsmtp.com (outmail148113.authsmtp.com
[62.13.148.113])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E8189682
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 May 2018 19:45:10 +0000 (UTC)
Received: from mail-c245.authsmtp.com (mail-c245.authsmtp.com [62.13.128.245])
by punt20.authsmtp.com. (8.15.2/8.15.2) with ESMTP id w49JRbvk015166;
Wed, 9 May 2018 20:27:37 +0100 (BST)
(envelope-from user@petertodd.org)
Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com
[52.5.185.120]) (authenticated bits=0)
by mail.authsmtp.com (8.15.2/8.15.2) with ESMTPSA id w49JRZoB057517
(version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
Wed, 9 May 2018 20:27:36 +0100 (BST)
(envelope-from user@petertodd.org)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by petertodd.org (Postfix) with ESMTPSA id DF0EC400BF;
Wed, 9 May 2018 19:27:34 +0000 (UTC)
Received: by localhost (Postfix, from userid 1000)
id 577062222A; Wed, 9 May 2018 15:27:33 -0400 (EDT)
Date: Wed, 9 May 2018 15:27:33 -0400
From: Peter Todd <pete@petertodd.org>
To: Johnson Lau <jl2012@xbt.hk>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20180509192733.6aif4wapolbb5z7c@petertodd.org>
References: <87po25lmzs.fsf@rustcorp.com.au>
<F8C553EE-9AF5-4348-90B7-3EC55FC46B4C@xbt.hk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="cqp4iwdhqcmyciql"
Content-Disposition: inline
In-Reply-To: <F8C553EE-9AF5-4348-90B7-3EC55FC46B4C@xbt.hk>
User-Agent: NeoMutt/20170113 (1.7.2)
X-Server-Quench: 07d073ba-53bf-11e8-a283-9cb654bb2504
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZIVwkA IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdgsUFVQNAgsB Am4bWVReUlp7WmU7 bghPaBtcak9QXgdq
T0pMXVMcUwFhe35r WWweVx53dgIIf3hx YQhiWSRbW0coJFt4
QRwCCGwHMG99OWIX U11RJFFSdQcYLB1A alQxNiYHcQ5VPz4z
GA41ejw8IwAXDS1W QwcCZXUqdnoxIxN0 XAwLGzkmB0FSLxvX
X-Authentic-SMTP: 61633532353630.1039:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 52.5.185.120/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
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 19:45:11 -0000
--cqp4iwdhqcmyciql
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, May 10, 2018 at 01:56:46AM +0800, Johnson Lau via bitcoin-dev wrote:
> 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
>=20
> 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.
>=20
> 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.
I don't think that will work, as a zero-fee tx won't get relayed even with
CPFP, due to the fact that we haven't yet implemented package-based tx
relaying.
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--cqp4iwdhqcmyciql
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEFcyURjhyM68BBPYTJIFAPaXwkfsFAlrzS6AACgkQJIFAPaXw
kfvW0wf/ULVBiKK33f221DJPW7uIpfRsxl2s7n7U9PWyAWSqdjub/EAtqFaqQNfN
7atKZ62H8sUYjtT4rW5T8kxGHj2gvbWEAHizC5aKZZLyfmpd5u9kmn6UHPnK0AnB
dX16D5D9Lch+iRSGE/m0hPEEJXvP1QrwO73JtyrI076v+G+gs8fde8l6Pw5wi94v
U88Ode5E6NUfBAZxbY0yDVE2NeW2iA2hT934cJlI6hPWmNPSfWkNxMi8eYoSBGv2
b/GCQBhaDYEcL//GRTGWRYIvOqVBSD7fvRU7PECcvlqhyT7lWq8qyhJJY473G27h
B8wmf7sEU3RvBqxjGBF8cGtXxmHFlQ==
=fAEn
-----END PGP SIGNATURE-----
--cqp4iwdhqcmyciql--
|
