It has been since segwit, but the process of retrieving data and viewing it from segwit is much more complicated.

Retrieving from op_return is easy, so easy that a court will likely deem that the node runner is storing illegal content, because their computer will almost certainly contain the tools that can be used to view the content.

Reply to this note

Please Login to reply.

Discussion

Any content on any hard disk or storage media can be classified as illegal by authorities, depending on their definition of illegal.

Run a node always minimum under TOR. I'm more concerned about largely organized Spam attacks. The argument that fees have to be played for these Spam attacks is a joke if government can easily pay for this.

Weak. You can say the same about surfing the internet on a pc

In July 2019, an anonymous BSV transaction embedded CSAM images in a ~100KB OP_RETURN output (pre-Genesis, when BSV allowed ~100KB, similar to BTC v30 now). The block was mined, making the content immutable and queryable via explorers (e.g., Blockchair). Exact txid wasn’t widely publicized for ethical reasons, but CoinGeek and BSV Wiki confirmed it.

Interpol and EU Authorities issued a notice in late 2019 urging BSV node operators to filter or prune the content.

BSV has an unlimited OP_RETURN field.

Governments that want to prosecute someone for something will find a way.

True but china has us by the balls. Bitcoin is the only hard money that can out compete china’s gold stack. Only Bitcoin can save their sorry asses

Retrieving content from segwit vs op_return is literally the same complex bash one liner. No practical difference (definitely not from court perspective)

I defer to Nick Szabo on that one. A computer scientist with a law degreee.

Hello Mr Judge, which one of these two is highly illegal and which one is cool?

Getting image data from op_return:

bitcoin-cli getrawtransaction 4719e7252f4bdefd9f7bdf5058f17af28729b79c303b067eb01c107e57235754 1 | jq -r '.vout[0].scriptPubKey.asm | sub("^OP_RETURN "; "")' | xxd -p -r | tail -c +25 | base64 -d >image.jpg

Getting image data from witness:

bitcoin-cli getrawtransaction 584b6d204fcf6e2a3dd82a9adc55890447a09b534ab7d725a7353aecf547bcbf 1 | jq '.vin[0].txinwitness[1][122:40430] | gsub("4d0802";"")' | xxd -r -p > image.webp