your node stores whatever ends up in a block. If you don’t want CSAM on your disk then run a pruned node or don’t run bitcoin at all.
even if its not in a flat contiguous format (op_return) you will still be able to recover images with a line of bash when it gets in your utxo set, like the bitcoin whitepaper.
This you can’t prune and can be done without op_return.
my take: you can’t stop it, adversarial actors will do it to attack bitcoin, stop giving them ideas.
good luck!
You seem to know a lot about recovering CSAM from the UTXO set. I'm not interested in doing that myself personally. I just want to know if it is technically possible to exclusively prune op_return data
I’m actually not aware of any script that does that, its not something that any sane bitcoiner would share. I only have done it with the whitepaper.
op_returns aren’t stored in the utxo set by design. So if you have a pruned node it won’t keep it around. but you might still have it in the utxoset somewhere else if there is some not stored in op_return.
an attacker likely would store them in the utxoset just to fuck with bitcoiners, not op_return
Thread collapsed
Thread collapsed
Our adversaries aren't idiots. We can either officially sanction 100KB file storage or we can legitimately present it as something we push back against.
No technical difference so devs are blind to the world of difference in that.
why would an attacker care about an unenforceable "sanction"
Thread collapsed
Thread collapsed
