[Proposal to Curb Bitcoin Spam via Temporary Soft Fork Sparks Debate Among Developers] According to The Block, debates among Bitcoin developers regarding blockchain data capacity have given rise to the controversial proposal BIP-444. The proposal was introduced after the Bitcoin Core v30 update removed the data size limit for OP_RETURN. Currently, only about 6.3% of nodes have adopted the new version. BIP-444 advocates limiting OP_RETURN outputs to 83 bytes, while most other scriptPubKeys would be restricted to 34 bytes or less, effectively blocking outputs containing large scripts or data blocks. The proposal also seeks to limit the size of individual data pushes, invalidate currently unused or undefined script versions to prevent circumvention of restrictions, restrict the size of embedded Merkle trees in Taproot outputs, and prohibit OP_IF in Tapscripts, effectively abolishing the ordinal inscription method. These changes would be implemented through a temporary soft fork, expected to last for one year, allowing developers time to explore alternative data storage solutions. Critics argue that this move violates Bitcoin's permissionless principle and constitutes censorship. Jameson Lopp from Casa pointed out that the proposal fails to clearly define the problem and raises unresolved legal liability issues for node operators. The proposal has not yet been submitted to the Bitcoin developer mailing list for feedback but has already sparked heated discussions on social media.