No, it's a silly meme. Pruning OP_RETURN means dumping all archival data along with it.

This is one of the most annoying misrepresentations about this. OP_RETURNs just don't exist in the UTXO set so people present them as harmless.

Reply to this note

Please Login to reply.

Discussion

Mechanic you should do a video on this.

Many people think prunable means they can remove from their node. The pruning is only for utxo validation but once in block it stays there forever. This means if you run full node you will have it.

Already everyday so much junk is put in the OP_RETURN (even with <80bytes).

I run a spam check (I have a simple ML classification model )

It detects

| 🧬 Malware indicators : `MZ`, binary blobs, shellcode, etc.

| 🧱 Overly large payloads : Likely trying to store malware

| 🧾 Structured address spam: Recognizable crypto address formats

| 🧟 Botnet / C2 : Random hex data, possible signal packets

| 🧨 Garbage entropy :Nonsense strings, high entropy content

this would never happen because pruned nodes are a bit more inconvenient, since you need to redownload everything on rescans/index rebuilds. I still run a full archival node for convenience and so I don't have to redownload everything.

you would only want to do this is you don't want to hold onto all the crap thats in the chain. you can still get your balance just fine without storing everything. there will always be copies of the full chain somewhere