Thread

🛡️
I have serious concerns with this framing. The legal argument doesn’t hold up. Node operators aren’t liable for encrypted data they didn’t create and can’t access. ISPs, CDNs, and Tor nodes have legal precedent here. What makes Bitcoin nodes different? CSAM has likely already been encoded in the blockchain for years through various methods. If this is truly an insta kill for adoption, why hasn’t it already happened? If Bitcoin can be killed by one attacker sending one instance of illegal content, then it was never antifragile. This argument concedes Bitcoin can’t survive adversarial use, which undermines the entire value proposition. And switch pools NOW but obviously I prefer OCEAN? That undercuts this being about Bitcoin’s survival rather than pool market share. If I’m missing something in the legal or technical analysis, I genuinely want to understand it View quoted note →

Replies (29)

You are correct on every count. OP_RETURN limits also have 0% efficacy. People are being lead around by their emotions and have sadly gone full retard. Reminds me of when everyone got tricked by Covid narratives or when many “freedom” proponents on nostr went rabid-stupid for trump in 2023. The human psyche is so easy to hack and attack. Watching it happen again, pretty sad.
Yeah it seems very obvious watching it happen but there are a lot of people who are actually falling for it. They’re ripe to be the next bcashers shaken out of their stacks by emotional manipulation and having their anxious tendencies weaponized. Like you said, if ONE instance of CSAM would destroy Bitcoin then it’s been over for a long time and was always an exceptionally fragile system. Luckily that’s not the case at all. Spam on chain has zero effect on my ability to use Bitcoin however I want. It doesn’t change the supply cap, its permission-less and censorship-resistance properties. 99.99999% of user have no clue there is spam on chain, they will never have a clue, and have no idea how to access it. I have no clue how to view spam on chain and I literally don’t care that it’s there. Means nothing to me.
If Core cared about preventing more harmful ways to imbed arbitrary data, they would have fixed the inscriptions hack 2 FUCKING YEARS ago. Instead they made a stealth change to the description of the data carrier to be able to _justify not fixing it_. For the love of God stop being so naive.
You’re the one who is naive. Spam will always morph and find its way onto the chain if it’s affordable to do so. To think you can stop it with perpetual changes to the protocol is a reactive losing game and it’s the naive way of thinking. Let go. Stop being emotional and stupid. Fees will price out spam eventually. If in the interim the spammers leave a bunch of huge stupid unspendable multisig scars on the chains that’s a much worse outcome than spendable UTXOs.
Do you lock your house when you leave? I bet you do. To think you can stop a motivated burglar from entering is the naive way of thinking. Let go. Stop being emotional and stupid. Not keeping anything of value in your home will eventually discourage burglars. Why keep paying for broken locks and windows? Just leave them open and put a welcome sign outside.
I actually don’t lock my house 😂 and I’ve never had an issue. Quite telling how these conversations are devolved into poorly constructed reductive metaphors by the emotional parties. When you can’t address the subject matter explicitly anymore constructive conversation is over. But I’ve made the correct technical points and it’s obvious that my position is the one that aligns with reality. Not engaging with your slop any further, good day.
1) We're not talking about encrypted data. 2) Bitcoin does not support images at all, so it is impossible to store CSAM. Stegonography is another matter entirely (though even in that regard, there's no evidence of CSAM). 3) Spam is not usage, and Bitcoin relies on its users to protect it. WE are Bitcoin's antifragility. 4) Obviously I'm going to recommend OCEAN. Not only am I biased, but it's also better for Bitcoin. But the point is to mitigate this, I'm willing to concede even the would-be-worst pools to mine on are better than F2Pool right now.
🛡️
I appreciate the dialogue. On point 1: Fair, but the OP_RETURN expansion makes data more readily accessible in standard format, which is your concern. The legal risk difference between encrypted and accessible is what Szabo flagged. On point 2: If Bitcoin can’t store images, what are ordinals/inscriptions doing? Taproot witness data allows arbitrary data that reassembles into images and files. The technical distinction doesn’t change the practical reality. On point 3: If Bitcoin’s survival requires coordinated human filtering rather than protocol level incentives making attacks expensive, that’s a fundamentally different security model than what Bitcoin was designed for. On point 4: The disagreement is whether filtering makes Bitcoin ‘better’ or fundamentally changes what Bitcoin is. What’s the technical solution that doesn’t require ongoing human judgment about legitimate versus illegitimate data?
2) Ordinals/Inscriptions are just spam. It's basically a scamcoin using proof-of-attacking-Bitcoin as its "algorithm". Taproot witness data does not allow arbitrary data - that's just an abusive *mis*interpretation of script code that Ordinals is doing completely unrelated to Bitcoin. This _is_ a relevant distinction. 3) Satoshi introduced spam filters to deal with the spam issue. So Bitcoin literally _was_ designed to work this way. 4) Again, Bitcoin has used spam filters from the start. It is Core30 that aims to change Bitcoin by removing some.
🛡️
It bugs me that this weak argument is what is leaned on so much rather than the clear disregard for stewardship from the core team. But then as far as I'm concerned it's not Core vs Knots, it's Core vs everyone and Knots just happened to be there as the main alternative.