PANews reported on October 27th that, according to The Block, a debate among Bitcoin developers over blockchain data capacity has spawned the controversial proposal BIP-444. This proposal, introduced after the Bitcoin Core v30 update removed the upper limit on the amount of data that can be added via OP_RETURN, has only been adopted by approximately 6.3% of nodes. BIP-444 proposes limiting OP_RETURN outputs to 83 bytes and most other scriptPubKeys to 34 bytes, effectively blocking outputs containing large scripts or data blocks. The proposal also limits the size of individual data pushes, invalidates currently unused or undefined script versions to prevent circumvention of the limits, limits the size of embedded Merkle trees in Taproot outputs, and prohibits OP_IF in Tapscripts, effectively eliminating the ordinal inscription method. These changes will be implemented via a temporary soft fork, expected to last a year, to allow developers to explore alternative data storage solutions. Critics argue that this violates Bitcoin's permissionless nature and constitutes censorship. Jameson Lopp of Casa noted that the proposal lacks clear definition of the issues at stake and raises questions about the legal liability of node operators. The proposal has not yet been submitted to the bitcoin development mailing list for feedback, but it has sparked heated discussion on social media.PANews reported on October 27th that, according to The Block, a debate among Bitcoin developers over blockchain data capacity has spawned the controversial proposal BIP-444. This proposal, introduced after the Bitcoin Core v30 update removed the upper limit on the amount of data that can be added via OP_RETURN, has only been adopted by approximately 6.3% of nodes. BIP-444 proposes limiting OP_RETURN outputs to 83 bytes and most other scriptPubKeys to 34 bytes, effectively blocking outputs containing large scripts or data blocks. The proposal also limits the size of individual data pushes, invalidates currently unused or undefined script versions to prevent circumvention of the limits, limits the size of embedded Merkle trees in Taproot outputs, and prohibits OP_IF in Tapscripts, effectively eliminating the ordinal inscription method. These changes will be implemented via a temporary soft fork, expected to last a year, to allow developers to explore alternative data storage solutions. Critics argue that this violates Bitcoin's permissionless nature and constitutes censorship. Jameson Lopp of Casa noted that the proposal lacks clear definition of the issues at stake and raises questions about the legal liability of node operators. The proposal has not yet been submitted to the bitcoin development mailing list for feedback, but it has sparked heated discussion on social media.

Proposal to curb Bitcoin spam with a temporary soft fork sparks debate among developers

By: PANews

2025/10/27 07:11

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.

Share Insights