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)
Subject: Re: [bitcoin-dev] Making OP_TRUE standard?
Precedence: list


--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--