Text messages shared with The Rage show that the Knots maintainer is considering a hardfork to implement a trusted multisig committee that can retrospectively alter the blockchain to remove illicit content.<\/h5>\n\n\n\n
There has been an ongoing dispute between supporters of the alternative node implementation Bitcoin Knots and supporters of the reference client Bitcoin Core. The dispute originally evolved out of Core\u2019s consideration to increase the OP_RETURN size in order prevent non-monetary transactions from using more harmful methods on the blockchain, such as data in unspendable outputs, while Bitcoin Knots proponents argue that non-monetary data \u2013 first described as \u201cspam\u201d \u2013 has no place in Bitcoin, and that Core developers should not optimize for it.<\/p>\n\n\n\n
To combat said \u201cspam\u201d, the Bitcoin Knots client \u2013 maintained by Bitcoin Core contributor Luke Dashjr \u2013 implements what it describes as filters, in which transactions which communicate non-monetary data are kept out of the Knots node\u2019s mempool.<\/p>\n\n\n\n
Over the past year, the discussion around Knots filters has grown increasingly out of control, as the narrative changed from protecting node operators from \u201cspam\u201d to protecting node operators from hosting Child Sexually Abusive Material (CSAM) \u2013 an argument that is technically unfeasible as long as node operators continue to run any node that follows the current consensus rules, as all nodes must host the same data once a block is approved.<\/p>\n\n\n\n
In private messages shared with The Rage, Dashjr now appears to concede that policing the mempool is insufficient to stop nodes from hosting theoretical CSAM. Instead, he proposes the implementation of a multisig quorum on Bitcoin that grants a designated group of people the ability to retroactively alter data that is hosted on the blockchain.<\/p>\n\n\n\n
By Dashjr\u2019s description, the trusted multisig committee would review transactions and replace any data it identifies as CSAM with a zero-knowledge proof. Node operators could then remove said data from their nodes \u2013 altering their version of the blockchain \u2013 while continuing to be able to prove that the transaction that contained the affected data is valid.<\/p>\n\n\n\n
\u201cRight now the only options would be Bitcoin dies or we have to trust someone,\u201d Dashjr writes. The proposed solution would require a consensus change, activating a Bitcoin hardfork.<\/strong><\/p>\n\n\n\n In follow-up messages, Dashjr reveals that public letters are being drafted by third parties to seemingly support the sanctioning of illegal content on the entire Bitcoin network. On advice of OCEAN\u2019s lawyer, the mining pool founded by Dashjr, the Knots team decided that \u201cit is better if the letter not be perceived as coming from us\u201d.<\/p>\n\n\n\n When asked for a comment by The Rage on the proposed hardfork, Dashjr asked \u201cYou\u2019re writing an article on completely unfounded lies?\u201d<\/p>\n\n\n\n Dashjr had no further comment for The Rage.<\/p>\n\n\n\n Dashjr\u2019s proposal raises immediate concerns on altering the permissionless nature of Bitcoin, effectively invalidating the blockchain\u2019s inherent censorship resistance. If the trusted committee enables node operators to remove CSAM data, it also gains the power to remove any other form of data it deems unfavorable.<\/p>\n\n\n\n In effect, Dashjr\u2019s proposal could place node operators at risk of criminal penalties for non-compliance with the committee\u2019s request for the removal of data. By setting the precedent that transactional data can be retroactively altered via a trusted committee, law enforcement may begin to demand censoring entire transactions they deem illicit, arguably opening the door for the enforcement of KYC\/AML.<\/p>\n\n\n\n
![\"\"\/](\"https:\/\/www.therage.co\/content\/images\/2025\/09\/the-rage-luke-dashjr-knots-hardfork.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/www.therage.co\/content\/images\/2025\/09\/the-rage-dashjr-bitcoin-hardfork-01.png\")
<\/figure>\n\n\n\n![\"\"\/](\"https:\/\/www.therage.co\/content\/images\/2025\/09\/dashjr-bitcoin-hardfork.png\")