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 (39)
How did you loose all those bitcoins? What was your setup?
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.
I'm really glad Luke is posting on nostr more now.
This is stupid. All digital technology is based on establishing conventions for data formats. If someone makes a new one up, it's no less real.
Try actually reading what I wrote.
Running Knot !!!
Consensus is inextricable from intention.
He did not lose them. His trust was exploited to steal them. Can't be too loose about whom you trust, and sometimes ya gotta learn the hard way. It can happen to anyone.
Respect and gratitude to Luke, anyway.
So he gave his keys to someone? Seems like a bad idea no?
Bitcoin actually does support arbitrary data greater than 80 bytes. Your node will relay it too, after a miner mines it.
I would rather put the onus on the publicly traded miner corporation with a board that accepted the transaction out of band on the hook, that any solo or pool miner being forced to include it.
But that's just me.
I would rather not establish precedent that node operators are responsible for the data on the block chain. That opens up a trivial attack vector by literally anybody. Making the argument that it’s a public space and therefore individual people aren’t responsible is much safer/robust over the long term
Data is just 0s and 1s. If you choose to interpret and decode it as a JPEG that’s your problem…
That "argument" will not hold up in any court.
But so doesn't Luke's.
Kaspa fixes this.
How is that relevant at all?
Anyway tell me, how does it feel to lose something? Would you share it publicly or just keep it to yourself?
> 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.
Seems like there's no precedent for these kind of cases.
View article →exactly what i was thinking
He was very public back then accusing everyone without ever disclosing his setup and owning up to his mistake of keeping his coins in a hot wallet. Guess you werent around back then
Beware people, the global almighty Interpreter is coming for your nodes!!
Run Knots now or run for your lives!
Yep, educate them Luke!
If someone gives me directions to the beach, and I follow those directions and I end up at the beach, then I haven't misinterpreted anything.
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.
It would be weird to then blame that person for the beach existing
Ok. Did that. I’m still not sure where you think I went off base.
Yes but you could blame them for a crowded beach existing. Which is a genuine state of existence for a beach.
Basically it's amorphous and messy, and attempts to draw clear lines are pretty ambitious.
If you dont feel it is relevant - best of luck to you trusting Luke with your node.
80 bytes seems accurate 😂😂😂
View quoted note →People realize #knots means Luke gets richer and we don’t want ONE PERSON with that much control. It goes against everything #Satoshi stood for.
Luke is a conman.
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. 🔥
Samesies. I had no idea what a jerky really was until he started posting here so give me a target and I’ll take it down. 😂😂😂
Maybe he should stick to knocking women up then. Fax 📠
So he’s a loser. And a bad one. Got it. #CryHarder
@Luke Dashjr You want a #blockchain #war and refuse to speak with others … your reckoning is coming
1. You don’t mess with *anyone* in #Bitcoin and expect to undermine them
A. Luke did.
2. Luke was given multiplicity of chances to be a man and admit he was wrong on multiple things. He declined.
3. #Satoshi stood for far more than this callous tiny acorn ever will.
We don't fax no more. We broadcast proof of work with cryptographic keys
Oh you just wait 😂😂😂
There are no illegal movie files distributed via nntp because nntp only works with text files.
