Yes, the question is how obfuscated? Some really complicated encoding that they had to invent to put it on chain gives legal deniability to node runners for relaying it. A jpg less so. More space makes it easier to use less convoluted encoding. Potentially illegal to run a node with a basic jpg validated on chain.
However we all know that companies like MARA have slipstream which will allow you to go right around knots filters already.
MARA says they scan slipstream submissions, likely just Cloudflare.
This is the real sticking point no one is actually talking about. No one has a way to stop this content inside Bitcoin. We can all relay anything that will validate in a block and it gets right in, or we all filter and essentially outsource prevention to miner centralization and Cloudflare.
Both paths are direct violations of the spirit and intent of Bitcoin in my opinion. Hopefully brighter minds find a third way soon, I'm smart enough to see the real problems through the yelling but I haven't figured out a solution.
Login to reply
Replies (3)
Bitcoin treasury companies are the death knell to mining centralization.
You cant put a JPEG in OP_Return now or in core 30. It still needs to be encoded/decoded.
Dude, first sentence. Literally the first sentence I wrote.
All data is encoded. Any useful information shared between humans in any way had to be encoded and then decoded.
Standard image or video formats supported by every software package on the planet are very different from a secret code you invented just for this one image that I don't reasonably know about when it comes to legal liability. Bigger sizes make standard encodings possible that aren't right now.
This kind of low effort 0 reading comprehension 0 critical thinking repetition of party line rhetoric is exactly why the only thing actually changing is how divided bitcoiners are.