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 protected].
To view this discussion visit
https://groups.google.com/d/msgid/bitcoindev/6f6b570f-7f9d-40c0-a771-378eb2c0c701n%40googlegroups.com.
