Bitcoin is and has been used to pay for much CSAM and much worse CSA but we all still use it as money. Unfortunately reality, but it’s outside of my dichotomy of control.

If someone adds CSAM to an OP_RETURN that gets hashed that event is completely out of everyone’s control (minus the person who submitted the tx) and has nothing to do with bitcoin or me. CSAM can be hashed on-chain without an expanded OP_RETURN as well in many different ways and some say it has already happened, though I haven’t seen proof either way.

I will continue to run my node and use bitcoin as I see fit and remain stoic in the face of propaganda and attacks.

Reply to this note

Please Login to reply.

Discussion

What I’m looking for is if there’s any legal liability distinction between how it’s been put on chain in the past vs in opreturn.

For what it’s worth, Adam Back has said there is solid legal precedent with TOR exit nodes and file sharing services that there is an established legal basis (in the U.S.) that would protect node runners of a public system in the event of CSAM on chain.

It is quite easily provable that a transaction and any data contained therein was submitted by a single entity and that all data hashed to the Bitcoin timechain is propagated to every node in perpetuity after submission and inclusion in a block. Demonstrably how the bitcoin protocol functions and easy to prove.

Nothing you said is an argument for a totally unasked-for 12000x increase in allowable data.

That’s a different conversation.

**** This just in.. pedoland under 'pedo software' "crisis" ****

The U.S. is the only UN member state that has not yet ratified the Convention on the Rights of the Child.

As of July 2025, child marriage is legal in 34 states.