<oembed><type>rich</type><version>1.0</version><title>Luke Dashjr wrote</title><author_name>Luke Dashjr (npub1lh…aa9nk)</author_name><author_url>https://yabu.me/npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Some people seem to want to argue that there is already CSAM in Bitcoin&#39;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).&#xA;&#xA;Exploits like &#34;Inscriptions&#34; 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.&#xA;&#xA;This distinction is very real and relevant. If you don&#39;t differentiate between &#34;data that can be misinterpreted to produce CSAM&#34; and &#34;data that correctly interpreted displays CSAM&#34;, then literally _all data_ is CSAM, with _no exceptions at all_. This tweet would be CSAM. Google&#39;s logo would be CSAM. Your phone&#39;s operating system would be CSAM. Literally anything _can_ be misinterpreted as CSAM.</html></oembed>