pull down to refresh

A British broadcaster was convicted of distributing CSAM because he replied to a message that contained CSAM, which they counted as distribution. They were motivated to catch him because they couldn't give him a jail sentence for possession due to it being a first offence.
If replying to a message in common law jurisdictions is counted as distribution, as in replying to the sender of the CSAM, then a motivated judicial system will absolutely count relaying transactions with CSAM in OP_RETURN as distribution.
They wouldn't even have to target everyone, just convict a couple of bitcoin influencers known to be running full nodes and the PR victory is sufficient to make Bitcoin not universal money in the eyes of the majority, confirmation bias that it is money for deviants and criminals, something many people already want to believe.
The equivalent before Core 30 is that someone snuck CSAM onto your machine in a format that you couldn't read without directly reproducing it from fragments, which is clearly not the same and could be the case with anyone's machine today given the prevalence of malware.
Now that bitcoin is an uncensored and unconstrained data transfer protocol it's going to be under a completely different kind of scrutiny.
reply
You're just ignoring the responses to that thread. I've heard all of the arguments that responded to that, so I know you have.
reply
I didn't ignore any responses to that thread. Quite the opposite, I actually responded to every critical or questioning reply, because the goal of the thread was to educate. If you see a reply you think I missed, please link to it and I will respond to it.
Now I have some questions for you:
Has it, or has it not, always been consensus-valid to embed up to ~1 MB of data using OP_RETURN?
Has it, or has it not, always been consensus-valid to embed up to ~4 MB of data using witness envelopes?
c52f39725a1c62b36a1a47ebdbeabf2b7ce84d381c600fab9241ca437d51fc32
reply
Policy matters
reply
Has it, or has it not, always been standard to embed up to 10,000 bytes of data using segwit witness envelopes and up to 400,000 bytes of data using taproot witness envelopes?
reply