"CSAM on the blockchain is not a problem cuz it looks random!!!!"

😠😡😠😡

Reply to this note

Please Login to reply.

Discussion

nostr:nprofile1qqs0erxlk3srn6pwa5mfn4t0pvfg2l3cyjhztpmjucms24mmnjk03rgpp4mhxue69uhkummn9ekx7mqpzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmc3tyyv9 It is already there and it indeed is less of an issue because it requires jumping through hoops to display the data that was scrambled and hacked onto my node. Whether it truly "doesn't matter" to the law is a legal question that hasn't been tested in court, but it certainly helps that the software was not intended for this use and does nothing to facilitate it... Until v30.

My concern is that there will be fewer hoops to jump through, and that core is making it easier to store arbitrary contiguous data for no monetary reason.

nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpzdmhxw309aex2mrp0yhx5c34x5hxxmmdqyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnvv9hxgpywa92 I may be wrong, but I thought the Bitcoin core desktop software will display op return, without xor. I may be wrong. I don't have time to check right now. But either way, I think the distinction between different "one liners" is very important and should not be flippantly ignored.

bitcoin-qt does not display them

the only way to display them is to call `bitcoin-cli getrawtransaction` which:

- decodes scrambed xor data from disk

- parses the block

- returns the data in a human-readable form.

- human readable in the case of OP_RETURN is a hex string

so in the very least you need bitcoin-cli to call an RPC on your node to parse the data and return json

then you need to run jq to extract the opcode and xxd -r -p to turn the hex into raw bytes.

then you need some way to interpret these bytes, if its just an image you could just redirect the bytes to a png/jpg file and open it. you might need the `file` command to detect the filetype.

if it is coded slightly different like my byte shift example, then you would need to add an extra command to the pipeline (via perl which is available on most linux machines)

so yes you would most definitely need the command line in the very least to transform the data to read it. but there is no guarantee its in an encoding you could interpret.

its not like a folder where people can just drop files into. you must run commands to extract the data. it doesn't really matter if the data is contiguous or not, because it needs to be transformed regardless.

"It doesn't really matter if the data is contiguous or not, because it needs to be transformed regardless."

I disagree. Ease of transformation matters. Being contiguous seems like a HUGE difference. From a programmer's perspective I can see why one would think it doesn't matter, but from a lawyer's perspective, I think it would matter a lot. Obviously I'm just offering a fuzzy conjecture and I'm not a lawyer, but I do not consider this question to be settled AT ALL and I don't think you should either.

I should also acknowledge that I'm probably wrong about being able to transform the data without CLI. I'm not trying to weasel out of that. Score 1 for nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpzdmhxw309aex2mrp0yhx5c34x5hxxmmdqyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnvv9hxgpywa92 on that point.