Feedback-ID: i525146e8:Fastmail
Date: Fri, 3 Feb 2023 17:10:43 -0500
From: Peter Todd <pete@petertodd.org>
To: Greg Sanders <gsanders87@gmail.com>
Message-ID: <Y92GY7s1U4P9fC/f@petertodd.org>
References: <CAPfvXf+N8aF+bqjGzpfDrhCYg7ngciSDCpUnCMHD+k5F+m3oWA@mail.gmail.com>
 <CAB3F3DuDODUxB5aK4VFWa8sKFCkZfOj6Vjb+Wp39opyt8MNnEA@mail.gmail.com>
 <CAB3F3DtrSFPmperGJJAUDZj7vt9aHgvkc0b5Pts3+mq5fTuWXA@mail.gmail.com>
 <CAB3F3DvToF_fia+X5SQi-L=BDYGLpzr8nNHqjtFBUjLMbyPE9Q@mail.gmail.com>
 <Y9vOGVMJx1b9CPYq@petertodd.org>
 <CAB3F3Du2XsHCh5o5S84XKKizTkrTFJJ-j42-qunyuSRkwX7H_Q@mail.gmail.com>
 <Y9vRjQVnZzA8Bx/s@petertodd.org>
 <CAB3F3DvumE-r+LGm8ivooPD9qfzFs-NK9Ve06Ew1EMAifSx8dw@mail.gmail.com>
 <Y9wbjsmPO+nyM267@petertodd.org>
 <CAB3F3Ds7Ux8MWnY-9Agehpk0hZx_xgeFmZG7hUjMkfe48T5GPA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="GcsX8nwDEs7HD0l+"
Content-Disposition: inline
In-Reply-To: <CAB3F3Ds7Ux8MWnY-9Agehpk0hZx_xgeFmZG7hUjMkfe48T5GPA@mail.gmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Ephemeral Anchors: Fixing V3 Package RBF
 againstpackage limit pinning
Precedence: list


--GcsX8nwDEs7HD0l+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 02, 2023 at 03:47:28PM -0500, Greg Sanders wrote:
> > OP_TRUE is the obvious way to do this, and it results with a 1 on the
> stack,
> which plays better with other standardness rules.
>=20
> What other standardness rules? MINAMALIF? How does that interact with the
> proposal?

It makes sense to require scripts to leave just a single OP_TRUE on the sta=
ck
at the end of execution, as otherwise that can be a source of malleability =
in
certain circumstances where the scriptSig ends up providing the OP_TRUE. I
don't believe we actually implement this as a rule right now. But you could
easily imagine that happening in a future upgrade.

Leaving an OP_2 on the stack doesn't achieve that and would require a
special-cased workaround. Spending the time now to do the obvious thing - u=
se
OP_TRUE as the canonical anyone-can-spend output - avoids this issue.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--GcsX8nwDEs7HD0l+
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmPdhmEACgkQLly11TVR
Lzch6w/9FZ2cRXUbxra9dM7BtEjnsKhtb7tPldpWnexoanDzpxrs1aYfeQgI55PF
2UOhXfNeI8VHuM2dMEnnRturs0VfaVqtkx7CBMog3i/51JFPwH0Qpjm4yn/MBK4U
1B3Y2/pvQFC0H6iSUsyHUPltvleKzuv5ikY9RExaDSX0KEMho5zY/aWukQsr69P1
iJrnwMz96XG1akdQTVtN41G8DLXNNCX9QiuULJ7n6VQ3nykx6aag/k90QlZFXY6X
p+tyoGb40F9RmEvP3O4OZPE12bp2ubYc3+ayQEaUC3GC+4trxQ1xTZPkxNjJY6Zy
uN8t9iRG75Fn+YRrrauClzi4vjRGHOT0YOczS4SRRB0vAFnFOzP700PKmlECg7SM
qklbr2DfpXswVMEjvIqSCZPNxUqVgnnFhTlvMgBsXoLF5+akhTtW9kp63pA3kQZO
OqrNLQT8z99Zpj0vZZbqsPq1lqYGJ6yZUvJqRbUSPxanj6DSLvtfFgZHPFIacPwf
7egRN2w54rfhm7HZX0amaw9FxClfTA4idDylUM5pmlSrlf1nT3ggtIPleS6bqFTq
p/qSQnb1s4R2FnvqV4rzCvnK7P3n9M0CV6Khzmkr6V+MOMsffD0gWmdpfrrSJyQ/
lOs+dx0qgeJ8PmFllEGfRs8uDAwq6OgcOfNEuyBqlchnGi5h6zM=
=Y5S2
-----END PGP SIGNATURE-----

--GcsX8nwDEs7HD0l+--