The Bitcoin Improvement Proposal 444 (BIP-444) is causing controversy within the Bitcoin community. This proposal calls for a temporary soft fork to limit arbitrary data stored in Bitcoin transactions, following the release of Bitcoin Core version 30. Supporters argue that this is necessary to prevent illegal content, such as child abuse images, from making node operators legally liable and undermining the decentralization of the network.
Technically, BIP-444 limits OP_RETURN data to 83 bytes, disables unused scripts, restricts the Merkle tree in Taproot, and blocks the Ordinals method. However, critics argue that this is censorship and goes against the spirit of freedom of Bitcoin. The proposal has not yet been submitted to the official development mailing list for further discussion.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
The proposed soft fork BIP-444 of Bitcoin has sparked controversy over censorship and network safety.
The Bitcoin Improvement Proposal 444 (BIP-444) is causing controversy within the Bitcoin community. This proposal calls for a temporary soft fork to limit arbitrary data stored in Bitcoin transactions, following the release of Bitcoin Core version 30. Supporters argue that this is necessary to prevent illegal content, such as child abuse images, from making node operators legally liable and undermining the decentralization of the network.
Technically, BIP-444 limits OP_RETURN data to 83 bytes, disables unused scripts, restricts the Merkle tree in Taproot, and blocks the Ordinals method. However, critics argue that this is censorship and goes against the spirit of freedom of Bitcoin. The proposal has not yet been submitted to the official development mailing list for further discussion.