Delivery-date: Fri, 03 Oct 2025 08:52:35 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of alicexbtong@gmail.com designates 2001:4860:4864:20::29 as permitted sender) client-ip=2001:4860:4864:20::29;
MIME-Version: 1.0
References: <6f6b570f-7f9d-40c0-a771-378eb2c0c701n@googlegroups.com>
 <842930fb-bede-408a-8380-776d4be4e094n@googlegroups.com> <aN_Wz5YbZ9NieQu0@mail.wpsoftware.net>
In-Reply-To: <aN_Wz5YbZ9NieQu0@mail.wpsoftware.net>
From: "/dev /fd0" <alicexbtong@gmail.com>
Date: Fri, 3 Oct 2025 19:48:38 +0530
Message-ID: <CALiT-ZpJ_F2UrvUwRjgMukxQJ+s8GVzgDCHWt=zMR+HkMDDWWQ@mail.gmail.com>
Subject: Re: [bitcoindev] Re: [BIP Proposal] Limit ScriptPubkey Size >= 520
 Bytes Consensus.
To: Andrew Poelstra <apoelstra@wpsoftware.net>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Content-Type: multipart/alternative; boundary="000000000000cd706b064041c72e"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

--000000000000cd706b064041c72e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Andrew,

> Restricting it to OP_RETURN would have zero effect on people trying to
use scriptpubkeys for data storage.

1. The data shows that nobody is using scriptPubKeys for more than 520
bytes. In fact, people have found new ways to encode data in transactions.
Example: [Merkle path][0] in taproot control block

2. If this applies to all scriptPubKeys, it could negatively affect the
[UTXO set][1] size because multiple outputs is an alternative if someone
really wants to use scriptPubKey for data.

[0]:
https://mempool.space/tx/c5714af322cd2ba94adf3d74325eb17f03d029ad2bf47dc54c=
3d929833c02628
[1]: https://mainnet.observer/charts/utxoset-size/

/dev/fd0
floppy disk guy

On Fri, Oct 3, 2025 at 7:29=E2=80=AFPM Andrew Poelstra <apoelstra@wpsoftwar=
e.net>
wrote:

> On Thu, Oct 02, 2025 at 06:21:18PM -0700, /dev /fd0 wrote:
> >
> > We can't predict future usage,
>
> Aside from proof-of-publication (i.e. data storage directly in the UTXO
> set) there is no usage of script which can't be equally (or better)
> accomplished by using a Segwit v0 or Taproot script.
>
> > so it would be great if this was restricted
> > to OP_RETURN. While there is no real use for a scriptPubKey larger than
> 520
> > bytes as shown in the data you shared, it is possible that users may
> create
> > more OP_RETURN outputs after this change. It does not affect the UTXO
> set
> > but will cost more and economically discourage the use of multiple
> > OP_RETURN outputs.
> >
>
> Restricting it to OP_RETURN would have zero effect on people trying to
> use scriptpubkeys for data storage. They would switch to any of the 65
> or so other OP_RETURN equivalents, and failing that, switch to
> OP_RESERVED, then to OP_FALSE, then to `0 1 EQVERIFY`, and so on. A
> restriction that applies specifically to OP_RETURN outputs is no
> restriction at all.
>
>
> --
> Andrew Poelstra
> Director, Blockstream Research
> Email: apoelstra at wpsoftware.net
> Web:   https://www.wpsoftware.net/andrew
>
> The sun is always shining in space
>     -Justin Lewis-Webster
>
>

--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
CALiT-ZpJ_F2UrvUwRjgMukxQJ%2Bs8GVzgDCHWt%3DzMR%2BHkMDDWWQ%40mail.gmail.com.

--000000000000cd706b064041c72e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Andrew,<div><br></div><div>&gt; Restricting it to OP_RE=
TURN would have zero effect on people trying to use scriptpubkeys for data =
storage.<br><br>1. The data shows that nobody is using scriptPubKeys for mo=
re than 520 bytes. In fact, people have found new ways to encode data in tr=
ansactions. Example: [Merkle path][0] in taproot control block<br><br>2. If=
 this applies to all scriptPubKeys, it could negatively affect the [UTXO se=
t][1] size because multiple outputs is an alternative if someone really wan=
ts to use scriptPubKey for data.<br><br>[0]:=C2=A0<a href=3D"https://mempoo=
l.space/tx/c5714af322cd2ba94adf3d74325eb17f03d029ad2bf47dc54c3d929833c02628=
">https://mempool.space/tx/c5714af322cd2ba94adf3d74325eb17f03d029ad2bf47dc5=
4c3d929833c02628</a><br>[1]:=C2=A0<a href=3D"https://mainnet.observer/chart=
s/utxoset-size/">https://mainnet.observer/charts/utxoset-size/</a></div><di=
v><br></div><div>/dev/fd0<br>floppy disk guy</div></div><br><div class=3D"g=
mail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On =
Fri, Oct 3, 2025 at 7:29=E2=80=AFPM Andrew Poelstra &lt;<a href=3D"mailto:a=
poelstra@wpsoftware.net">apoelstra@wpsoftware.net</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Oct 02, 2025 at 06=
:21:18PM -0700, /dev /fd0 wrote:<br>
&gt; <br>
&gt; We can&#39;t predict future usage,<br>
<br>
Aside from proof-of-publication (i.e. data storage directly in the UTXO<br>
set) there is no usage of script which can&#39;t be equally (or better)<br>
accomplished by using a Segwit v0 or Taproot script.<br>
<br>
&gt; so it would be great if this was restricted <br>
&gt; to OP_RETURN. While there is no real use for a scriptPubKey larger tha=
n 520 <br>
&gt; bytes as shown in the data you shared, it is possible that users may c=
reate <br>
&gt; more OP_RETURN outputs after this change. It does not affect the UTXO =
set <br>
&gt; but will cost more and economically discourage the use of multiple <br=
>
&gt; OP_RETURN outputs. <br>
&gt; <br>
<br>
Restricting it to OP_RETURN would have zero effect on people trying to<br>
use scriptpubkeys for data storage. They would switch to any of the 65<br>
or so other OP_RETURN equivalents, and failing that, switch to<br>
OP_RESERVED, then to OP_FALSE, then to `0 1 EQVERIFY`, and so on. A<br>
restriction that applies specifically to OP_RETURN outputs is no<br>
restriction at all.<br>
<br>
<br>
-- <br>
Andrew Poelstra<br>
Director, Blockstream Research<br>
Email: apoelstra at <a href=3D"http://wpsoftware.net" rel=3D"noreferrer" ta=
rget=3D"_blank">wpsoftware.net</a><br>
Web:=C2=A0 =C2=A0<a href=3D"https://www.wpsoftware.net/andrew" rel=3D"noref=
errer" target=3D"_blank">https://www.wpsoftware.net/andrew</a><br>
<br>
The sun is always shining in space<br>
=C2=A0 =C2=A0 -Justin Lewis-Webster<br>
<br>
</blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/CALiT-ZpJ_F2UrvUwRjgMukxQJ%2Bs8GVzgDCHWt%3DzMR%2BHkMDDWWQ%40mail=
.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.co=
m/d/msgid/bitcoindev/CALiT-ZpJ_F2UrvUwRjgMukxQJ%2Bs8GVzgDCHWt%3DzMR%2BHkMDD=
WWQ%40mail.gmail.com</a>.<br />

--000000000000cd706b064041c72e--