A leaked conversation has revealed that developer Luke Dashjr may be considering a hard fork that could give a trusted committee the power to censor data on the blockchain. This is an idea that strikes at the heart of Bitcoin’s promise of censorship resistance.
Here’s what you need to know!
Bitcoin censorship back in the spotlight
Dashjr, maintainer of the Bitcoin Knots client, is considering a drastic step. It involves a hard fork that would give a trusted multisig committee power to retroactively alter blockchain data. The stated aim is to remove child sexual abuse material (CSAM) and other non-monetary data such as Ordinals and Runes, content that some in the community have long labeled as “spam.”
This proposal is the latest development in the ongoing feud between Bitcoin Knots and Bitcoin Core developers. The dispute dates back to earlier debates over how to handle non-monetary transactions.
Core explored adjusting the op_return size to limit harmful data storage, while Knots took a stricter position, filtering such transactions from its mempool. Over time, the discussion escalated from concerns about blockchain “clutter” to the far more serious argument of whether nodes are at risk of hosting illegal content.
Why this could change Bitcoin forever
Dashjr’s idea reportedly involves creating a multisig quorum, essentially a trusted committee with the authority to review and remove data deemed illicit.
In practice, this would mean transactions flagged for content like CSAM could be stripped out and replaced with a zero-knowledge proof, keeping the transaction valid while altering the chain’s stored data.
Source: X
In one exchange, Dashjr argued bluntly,
“Right now the only options would be Bitcoin dies or we have to trust someone.”
Needless to say, this raises some big questions for Bitcoin’s future. Allowing any group to retroactively alter blockchain data would weaken the permissionless, censorship-resistant foundation the network was built on.
Node operators could also face legal risks if they fail to comply with takedown demands, effectively forcing them into a compliance role. It could set a dangerous precedent, making way for broader censorship of transactions under KYC/AML rules.
