Feedback-ID: i525146e8:Fastmail
Date: Thu, 2 Feb 2023 06:22:23 -0500
From: Peter Todd <pete@petertodd.org>
To: Andrew Poelstra <apoelstra@wpsoftware.net>
Message-ID: <Y9uc72RSs6LQojG4@petertodd.org>
References: <CACrqygAMsO1giYuxm=DZUqfeRjEqGM7msmEnZ-AHws3oA2=aqw@mail.gmail.com>
 <764E460B-C0C6-47B8-A97E-F7CBC81FD645@petertodd.org>
 <Y9pxAdm3kO1rr2kU@camus>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="y38CCmU2HZ6kL8N5"
Content-Disposition: inline
In-Reply-To: <Y9pxAdm3kO1rr2kU@camus>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE
 OP_IF OP_PUSH
Precedence: list


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

On Wed, Feb 01, 2023 at 02:02:41PM +0000, Andrew Poelstra wrote:
> On Tue, Jan 31, 2023 at 09:07:16PM -0500, Peter Todd via bitcoin-dev wrot=
e:
> >=20
> >=20
> > On January 31, 2023 7:46:32 PM EST, Christopher Allen via bitcoin-dev <=
bitcoin-dev@lists.linuxfoundation.org> wrote:
> > >All other things being equal, which is better if you need to place a
> > >64-bytes into the Bitcoin blockchain? A traditional OP_RETURN or a spe=
nt
> > >taproot transaction such as:
> > >
> > >OP_FALSE
> > >OP_IF
> > >OP_PUSH my64bytes
> > >OP_ENDIF
> >=20
> > What's wrong with OpPush <data> OpDrop?
> >
>=20
> This is a technical nit, but the reason is that <data> is limited to 520
> bytes (and I believe, 80 bytes by standardness in Taproot), so if you
> are pushing a ton of data and need multiple pushes, it's more efficient
> to use FALSE IF ... ENDIF since you avoid the repeated DROPs.

Yes, for more than 520 bytes you need to wrap the push in an IF/ENDIF so it=
's
not executed. But in this example we're just talking about 64 bytes, so that
limit isn't relevant and OpPush <data> OpDrop should be sufficient.

Specifically for more than 520 bytes you run into the the
MAX_SCRIPT_ELEMENT_SIZE check in script/interpreter.cpp, which applies to a=
ll
scripts regardless of standardness at script execution:

           //
           // Read instruction
           //
           if (!script.GetOp(pc, opcode, vchPushValue))
               return set_error(serror, SCRIPT_ERR_BAD_OPCODE);
           if (vchPushValue.size() > MAX_SCRIPT_ELEMENT_SIZE)
               return set_error(serror, SCRIPT_ERR_PUSH_SIZE);

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

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

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

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmPbnO0ACgkQLly11TVR
LzeTgRAAh4KEOfcl1rst/9v1R2MGReWITXP7hRzZVJwm/ZloG/cNVRxETjnXIfKK
SCbW5SDV0PMM2qSBKbOCze1FyrMfmYYeD1Nvh/ExIiBByBdGHbbvfmIuJg75xyZp
hHF1+V5g3oyvJSZyhl5nbvfwkhUxpu6WxiLNh7OeoMiWz+yvmtrzaVgCp4FGwcle
1kJnUY50LiVuKVx916vTTVN2QKkfYjz0CQQBZVuWddpt2GVmldXjNucRJk/iAiK+
xKjizjthwRYMDUhfOooFuEf6MobJP2GSMYSJFYXR+6QxxAcz1zvD4oIVF3ISyyRk
Q0Apr55sH0U4XQInAAT4LvwZD1WqoZ9v2qw196empAaFPcAK9DnxDEaa66GjXbO1
blUpZdhpcZPbXZid+/0wmpg4RN3BGnRA3SVQ+euPdgqmGZML77icLAq9MB31ftdh
0q/Lpc7JKVdG1kqGzwrioWa0/QnDtk/3OuqAzpBW9/4RSTN50OxqWsuCRtpx2YE5
NeDfrkUFPsYHkpH3D/MBoU/qI2w3kIfWeiQO+v+cjchRpM+33jFpKF7RSyJegdSm
dAn74QpqMCJfrfImEtjlTsVIkvajLg478ANbVXpiu/N4L9VkV8uB+N+dyw8jyMEp
xt/MZ/eRL3G7ruNh9UHwA0nyvFgMk6j2FyXt0ATxcsgYt1RwZpE=
=K8SR
-----END PGP SIGNATURE-----

--y38CCmU2HZ6kL8N5--