Why any proposed mechanism for miners to stop "illegal content" in OP_RETURNs just won't work. Here's my bitcoin stackexchange answer:
Discussion
Join Fintech Catalysts for crypto mentorship on Telegram
and get real-time trade signals, expert analysis, and mirror trading strategies
How about we license every miner. Every miner has to forward every single transaction to a truth ministry. It will then only allow legal bytes into any transaction.
heads-up: we looked for a lightning address on your profile but could not find one... u can get a free one at https://rizful.com ... and then reply back to this comment so we can zap you.
knots supporters mouths are watering at the idea
and cores supporters mouths are coated with the lizard semen of special interests - and having been already precluded from healthy adversarial thinking while a bloated ego was cultivated, due to being born after 1990 and being raised on decadent lies and "im ok yer ok" feminine antichrist faggotry, they are for all intents and purposes, USELESS GRIFTERS.
Core is increasing the attack surface of Bitcoin. Knots is pointing out the problem. We are trying to prevent regulation, not embrace it. 🤡
Sounds like a job for nostr:npub1taawqsgm9n2rvtj2pcwgqd4mrea4uqpt4hze7t6fxd72rjqng4rsh74pm5
Need some regularity clarity
Who a breaking the law:
the entity who out the data in,
the entity who displays/decode it
The entity who stores/ protocol it.
In case of btc it’s both a protocol and storage mechanism…
It goes back to freedom of speech case, should Facebook, X and tv channel sensor the speech or let them speak and justice department can come after the people who broke the law. In case of the internet not sure how you go after the protocol itself except for internet providers…
Filters don't work 100%. We al know that, but that doesn't mean to get rid of them. First of all they work for most cases and second of all they give you plausible deniability if illegal spam gets through. Doing nothing is saying your CSAM is welcome on the blockchain uncoded.
they don't work for most cases
What about the fact that an op return can display non-encoded data directly in the Bitcoin core software? This makes it appear that the INTENT of Bitcoin is to distribute arbitrary information, rather having that information "hacked" onto my node against my will. This seems to be an important legal distinction.
i don't see the difference. in both cases they require a one-liner to extract the data. the entire blockchain is already xor'd on disk
"a one-liner"
Not all one-liners are created equal. I think one could pull an image out of op return on a desktop without using the command line or any custom software at all.
We are all throwing around our opinions about this, but lawyers need to be consulted. This is a legal question.
> I think one could pull an image out of op return on a desktop without using the command line or any custom software at all.
how would you do that, the data is xor'd on disk (it looks completely random). you need to call rpcs to get the data to decode it at the very least.
"CSAM on the blockchain is not a problem cuz it looks random!!!!"
😠😡😠😡
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.