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.
Login to reply
Replies (3)
This is fine art.
nostr:nevent1qqsfpwdekvqdp5p0gnz30kg9970g63rglqgyf4feamfa2sjxqzvyl3gpzpmhxue69uhkummnw3ezumt0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0dldjxr
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
So hypothetically if literally everybody starts pruning their nodes, does that make it impossible for anyone to spin up a new node? nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpz3mhxw309aex2mrp0yhx5c34x5hxxmmd9uqsuamnwvaz7tmwdaejumr0dshszythwden5te0dehhxarj9ekxzmny9u0ljp2l nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4spz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqsuamnwvaz7tmwdaejumr0dshsu0ur8h