Subject: Re: [bitcoindev] [BIP Proposal] Limit ScriptPubkey Size >= 520 Bytes Consensus.

From: Brandon Black <[email-masked]>
Date: Thu, 2 Oct 2025 15:27:49 -0700 (PDT)

Love this idea.

I think "users will just use more outputs" is the one argument against. But with witness size not limited in this way, I don't see that being a problem.

If this avoids any of the fiddliness involved in avoiding DOS with GCC, I think we should do it.

Best,

Brandon
--Brandon, sent by an Android

Oct 2, 2025 15:00:22 PortlandHODL <[email-masked]>:

> Proposing: Softfork to after (n) block height; the creation of outpoints with greater than 520 bytes in the ScriptPubkey would be consensus invalid.
> 
> This is my gathering of information per BIP 0002
> 
> After doing some research into the number of outpoints that would have violated the proposed rule there are exactly 169 outpoints. With only 8 being non OP_RETURN. I think after 15 years and not having discovered use for 'large' ScriptPubkeys; the reward for not invalidating them at the consensus level is lower than the risk of their abuse. 
> * *Reasons for
>   * *Makes DoS blocks likely impossible to create that would have any sufficient negative impact on the network.
>   * Leaves enough room for hooks long term
>   * Would substantially reduce the divergence between consensus  and relay policy
>   * Incredibly little use onchain as evidenced above.
>   * Could possibly reduce codebase complexity. Legacy Script is largely considered a mess though this isn't a complete disablement it should reduce the total surface that is problematic.
>   * Would make it harder to use the ScriptPubkey as a 'large' datacarrier.
>   * Possible UTXO set size bloat reduction.
> 
> * *Reasons Against *
>   * Bitcoin could need it in the future? Quantum?
>   * Users could just create more outpoints.
> Thoughts?
> 
> source of onchain data [https://github.com/portlandhodl/portlandhodl/blob/main/greater_520_pubkeys.csv]
> 
> PortlandHODL
> 
> 
> -- 
> 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 [email-masked].
> To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/6f6b570f-7f9d-40c0-a771-378eb2c0c701n%40googlegroups.com[https://groups.google.com/d/msgid/bitcoindev/6f6b570f-7f9d-40c0-a771-378eb2c0c701n%40googlegroups.com?utm_medium=email&utm_source=footer].

-- 
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 [email-masked].
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/2e5be000-c054-44ea-818c-653dc11f0901%40reardencode.com.