Thread

🛡️
Some people seem to want to argue that there is already CSAM in Bitcoin's blockchain. This is false. Bitcoin today does not support images at all - only arbitrary data up to 80 bytes (or 95 in the coinbase). Exploits like "Inscriptions" work by _misinterpreting_ script code, and _bypassing_ existing policy rules. They are not actually storing images, but merely putting gibberish code on the chain, which they later themselves (not Bitcoin) _misinterpret_ as images. This distinction is very real and relevant. If you don't differentiate between "data that can be misinterpreted to produce CSAM" and "data that correctly interpreted displays CSAM", then literally _all data_ is CSAM, with _no exceptions at all_. This tweet would be CSAM. Google's logo would be CSAM. Your phone's operating system would be CSAM. Literally anything _can_ be misinterpreted as CSAM.

Replies (27)

This feels like a distinction without a difference. All image data is always stored using a set of formatting and storage rules. I agree that they used processes within the bitcoin script that were not intended to be used that way. But that doesn’t change the fact that images can be stored on the blockchain using that “misuse” of bitcoin script.
As if Bitcoin isn't hard enough to understand, didn't/don't we all try to explain it to others.... This goes to another layer. Understanding longterm effects of relative small changes. Legal implications over multiple jurisdictions. People running sw on their node, storing data they don't understand nor the implications it could have. Etc. etc. And we try to make progress by posting parts, opinions to people we don't know, have total different amounts and not mutual understood levels of understanding. I'm not the brightest but how is this going to lead to more understanding or a solution.. Nobody needs to tell me this post won't help anything either. Just keeping quiet is also no solution. Antonopoulos has told us core has no power in the end. But damage can be done. My 'request' to freeze the code is not realistic. Are we just going to have to look how this plays out ? Is this just a next needed 'data war' after the 'blocksize war'. Bitcoin isn't in the same position as it was in 2017.
🛡️
So here's an example for how to read image from witness inscription (I promise it's not CSAM): bitcoin-cli getrawtransaction "584b6d204fcf6e2a3dd82a9adc55890447a09b534ab7d725a7353aecf547bcbf" 1 | jq '.vin[0].txinwitness[1]' | awk -F '0063036f726401010a696d6167652f776562705202' '{gsub("4d0802", "", $2); print substr($2, 7)}' | xxd -r -p > test.webp View quoted note →
🛡️
↩ replying to npub1c80w...h5s7
Seems like there's no precedent for these kind of cases.
ManyKeys's avatar ManyKeys
OP_RETURN Data Carrier Size Removal: Technical and Legal Risks
Increasing Bitcoin's OP_RETURN data carrier size from 80 bytes up to ~4 MB per block (Bitcoin Core v30) brings new technical and legal risks—especially regarding liability for illicit data—alongside a drive toward network standardization and transparency. This analysis weighs both sides, highlighting the debate between critics warning about centralization pressures and developer advocates focused on protocol realities and censorship resistance.
Read article →
🛡️
> Bitcoin today does not support images at all Are you suggesting v30 and higher will parse the uploaded images at the client level? I thought the Bitcoin Core GUI is strictly a wallet/block explorer interface and shall never render or interpret image data contained in blockchain transactions.
Bitcoin does not intentionally support images, but intentions many times depart from reality. Unintentionally supporting arbitrary data, IS a way to support images, among other things. And yes, many arbitrary data storage solutions indirectly support images, including for sure a phone's OS, among other devices. And some images can fall into the CSAM category, thus being illegal. It seems unnecessary to force arguments to deny the obvious.
Quit exploiting everyone’s over CSAM 1. You weren’t bitching at all when everybody was putting pictures Trump on there. 2. You just don’t want the EPSTEIN FILE on #blockchain 3. You had your chance, get ready to burn. 🔥