Delivery-date: Fri, 03 Oct 2025 01:57:27 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of garlonicon@gmail.com designates 2a00:1450:4864:20::62d as permitted sender) client-ip=2a00:1450:4864:20::62d;
MIME-Version: 1.0
References: <6f6b570f-7f9d-40c0-a771-378eb2c0c701n@googlegroups.com>
 <aN76f2wKPHFcj8qt@mail.wpsoftware.net> <FIpHCygrCyfUu_jNgLJumi-06nYm5P6rmUVc01R3SmhdMVbQo9-8Lyxbh5yGUPrHFQRtyYQ_RvgltQNuoulyXmdnuQSklTab_sM5X63FUs4=@protonmail.com>
In-Reply-To: <FIpHCygrCyfUu_jNgLJumi-06nYm5P6rmUVc01R3SmhdMVbQo9-8Lyxbh5yGUPrHFQRtyYQ_RvgltQNuoulyXmdnuQSklTab_sM5X63FUs4=@protonmail.com>
From: Garlo Nicon <garlonicon@gmail.com>
Date: Fri, 3 Oct 2025 09:11:30 +0200
Message-ID: <CAN7kyNj0zWY8mRtitZNGSrexpQES6U4txswcEgd6BZQUYKX_tw@mail.gmail.com>
Subject: Re: [bitcoindev] [BIP Proposal] Limit ScriptPubkey Size >= 520 Bytes Consensus.
To: moonsettler <moonsettler@protonmail.com>
Cc: Andrew Poelstra <apoelstra@wpsoftware.net>, PortlandHODL <admin@qrsnap.io>, 
	Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Content-Type: multipart/alternative; boundary="0000000000004b595206403bd0d4"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

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

> 200 should be enough.

Maybe. But "520" is a battle-tested value, when it comes to the maximum
allowed stack push. Picking "520" should be safe enough, and it has a
higher chances to be accepted as a new consensus rule. Also, if it turns
out, that a lower limit, like "200" is enough, then it can be lowered later
(but bumping it would be much harder).

> If this should apply to OP_RETURN (nulldata) or not, is something I can't
make my mind up on.

I think it should be applied everywhere. And if someone needs a larger
OP_RETURN, then that Script can be taken, wrapped into TapScript branch,
and included to any Taproot address.

pt., 3 pa=C5=BA 2025 o 00:49 'moonsettler' via Bitcoin Development Mailing =
List <
bitcoindev@googlegroups.com> napisa=C5=82(a):

> Hi All,
>
> Agreed, this is something we should consider.
>
> > I would even suggest going lower than 520 bytes.
>
> 200 should be enough.
>
> If this should apply to OP_RETURN (nulldata) or not, is something I can't
> make my mind up on.
>
> BR,
> moonsettler
>
> Sent with Proton Mail secure email.
>
> On Friday, October 3rd, 2025 at 12:31 AM, Andrew Poelstra <
> apoelstra@wpsoftware.net> wrote:
>
> > On Thu, Oct 02, 2025 at 01:42:06PM -0700, PortlandHODL wrote:
> >
> > > Proposing: Softfork to after (n) block height; the creation of
> outpoints
> > > with greater than 520 bytes in the ScriptPubkey would be consensus
> invalid.
> >
> >
> > Personally, I like this. Unlike restrictions on opcode behavior or
> > witness data, it is impossible for there to be any existing UTXOs which
> > "might turn out to need" scriptpubkeys greater than 520 bytes. In a
> > post-covenant world I suppose this could change.
> >
> > There is a risk of confiscation of coins which have pre-signed but
> > unpublished transactions spending them to new outputs with large
> > scriptPubKeys. Due to long-standing standardness rules, and the presenc=
e
> > of P2SH (and now P2WSH) for well over a decade, I'm skeptical that any
> > such transactions exist.
> >
> > In any case, if confiscation is a worry, as always we can exempt the
> > current UTXO set from the rule -- if you are only spending outputs that
> > existed prior to the new rule, your new UTXOs are allowed to be large.
> >
> >
> > I would even suggest going lower than 520 bytes.
> >
> >
> > --
> > 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
> >
> > --
> > 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 email to bitcoindev+unsubscribe@googlegroups.com.
> > To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/aN76f2wKPHFcj8qt%40mail.wpso=
ftware.net
> .
>
> --
> 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
> email to bitcoindev+unsubscribe@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/FIpHCygrCyfUu_jNgLJumi-06nYm=
5P6rmUVc01R3SmhdMVbQo9-8Lyxbh5yGUPrHFQRtyYQ_RvgltQNuoulyXmdnuQSklTab_sM5X63=
FUs4%3D%40protonmail.com
> .
>

--=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/=
CAN7kyNj0zWY8mRtitZNGSrexpQES6U4txswcEgd6BZQUYKX_tw%40mail.gmail.com.

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

<div dir=3D"ltr">&gt; 200 should be enough.<br><br>Maybe. But &quot;520&quo=
t; is a battle-tested value, when it comes to the maximum allowed stack pus=
h. Picking &quot;520&quot; should be safe enough, and it has a higher chanc=
es to be accepted as a new consensus rule. Also, if it turns out, that a lo=
wer limit, like &quot;200&quot; is enough, then it can be lowered later (bu=
t bumping it would be much harder).<br><br>&gt; If this should apply to OP_=
RETURN (nulldata) or not, is something I can&#39;t make my mind up on.<br><=
br>I think it should be applied everywhere. And if someone needs a larger O=
P_RETURN, then that Script can be taken, wrapped into TapScript branch, and=
 included to any Taproot address.</div><br><div class=3D"gmail_quote gmail_=
quote_container"><div dir=3D"ltr" class=3D"gmail_attr">pt., 3 pa=C5=BA 2025=
 o 00:49=C2=A0&#39;moonsettler&#39; via Bitcoin Development Mailing List &l=
t;<a href=3D"mailto:bitcoindev@googlegroups.com">bitcoindev@googlegroups.co=
m</a>&gt; napisa=C5=82(a):<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">Hi All,<br>
<br>
Agreed, this is something we should consider.<br>
<br>
&gt; I would even suggest going lower than 520 bytes.<br>
<br>
200 should be enough.<br>
<br>
If this should apply to OP_RETURN (nulldata) or not, is something I can&#39=
;t make my mind up on.<br>
<br>
BR,<br>
moonsettler<br>
<br>
Sent with Proton Mail secure email.<br>
<br>
On Friday, October 3rd, 2025 at 12:31 AM, Andrew Poelstra &lt;<a href=3D"ma=
ilto:apoelstra@wpsoftware.net" target=3D"_blank">apoelstra@wpsoftware.net</=
a>&gt; wrote:<br>
<br>
&gt; On Thu, Oct 02, 2025 at 01:42:06PM -0700, PortlandHODL wrote:<br>
&gt; <br>
&gt; &gt; Proposing: Softfork to after (n) block height; the creation of ou=
tpoints<br>
&gt; &gt; with greater than 520 bytes in the ScriptPubkey would be consensu=
s invalid.<br>
&gt; <br>
&gt; <br>
&gt; Personally, I like this. Unlike restrictions on opcode behavior or<br>
&gt; witness data, it is impossible for there to be any existing UTXOs whic=
h<br>
&gt; &quot;might turn out to need&quot; scriptpubkeys greater than 520 byte=
s. In a<br>
&gt; post-covenant world I suppose this could change.<br>
&gt; <br>
&gt; There is a risk of confiscation of coins which have pre-signed but<br>
&gt; unpublished transactions spending them to new outputs with large<br>
&gt; scriptPubKeys. Due to long-standing standardness rules, and the presen=
ce<br>
&gt; of P2SH (and now P2WSH) for well over a decade, I&#39;m skeptical that=
 any<br>
&gt; such transactions exist.<br>
&gt; <br>
&gt; In any case, if confiscation is a worry, as always we can exempt the<b=
r>
&gt; current UTXO set from the rule -- if you are only spending outputs tha=
t<br>
&gt; existed prior to the new rule, your new UTXOs are allowed to be large.=
<br>
&gt; <br>
&gt; <br>
&gt; I would even suggest going lower than 520 bytes.<br>
&gt; <br>
&gt; <br>
&gt; --<br>
&gt; Andrew Poelstra<br>
&gt; Director, Blockstream Research<br>
&gt; Email: apoelstra at <a href=3D"http://wpsoftware.net" rel=3D"noreferre=
r" target=3D"_blank">wpsoftware.net</a><br>
&gt; Web: <a href=3D"https://www.wpsoftware.net/andrew" rel=3D"noreferrer" =
target=3D"_blank">https://www.wpsoftware.net/andrew</a><br>
&gt; <br>
&gt; The sun is always shining in space<br>
&gt; -Justin Lewis-Webster<br>
&gt; <br>
&gt; --<br>
&gt; You received this message because you are subscribed to the Google Gro=
ups &quot;Bitcoin Development Mailing List&quot; group.<br>
&gt; To unsubscribe from this group and stop receiving emails from it, send=
 an email to <a href=3D"mailto:bitcoindev%2Bunsubscribe@googlegroups.com" t=
arget=3D"_blank">bitcoindev+unsubscribe@googlegroups.com</a>.<br>
&gt; To view this discussion visit <a href=3D"https://groups.google.com/d/m=
sgid/bitcoindev/aN76f2wKPHFcj8qt%40mail.wpsoftware.net" rel=3D"noreferrer" =
target=3D"_blank">https://groups.google.com/d/msgid/bitcoindev/aN76f2wKPHFc=
j8qt%40mail.wpsoftware.net</a>.<br>
<br>
-- <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%2Bunsubscribe@googlegroups.com" target=
=3D"_blank">bitcoindev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/FIpHCygrCyfUu_jNgLJumi-06nYm5P6rmUVc01R3SmhdMVbQo9-8Lyxbh5yGUPrH=
FQRtyYQ_RvgltQNuoulyXmdnuQSklTab_sM5X63FUs4%3D%40protonmail.com" rel=3D"nor=
eferrer" target=3D"_blank">https://groups.google.com/d/msgid/bitcoindev/FIp=
HCygrCyfUu_jNgLJumi-06nYm5P6rmUVc01R3SmhdMVbQo9-8Lyxbh5yGUPrHFQRtyYQ_RvgltQ=
NuoulyXmdnuQSklTab_sM5X63FUs4%3D%40protonmail.com</a>.<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/CAN7kyNj0zWY8mRtitZNGSrexpQES6U4txswcEgd6BZQUYKX_tw%40mail.gmail=
.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/ms=
gid/bitcoindev/CAN7kyNj0zWY8mRtitZNGSrexpQES6U4txswcEgd6BZQUYKX_tw%40mail.g=
mail.com</a>.<br />

--0000000000004b595206403bd0d4--