Guys, there is a big misunderstanding. It’s already possible to embed full JPGs in a single transaction. The problem today (Core/Knots) is where the data goes: it’s written into the pubkey or witness area, which is needed to build the UTXO set. That forces every node to keep this data forever to stay consistent – even if nobody wants to store JPGs. The planned Core update changes this by enlarging the OP_RETURN field. Spammers could still add data, but OP_RETURN outputs are unspendable and never enter the UTXO set. Nodes still see them during verification, but afterwards they don’t matter anymore. Classic full nodes keep them in history, but pruned nodes can drop the data after validation and just keep the UTXO set plus the most recent blocks. So today (Core/Knots) all nodes must carry the junk permanently. With the Core update, OP_RETURN spam doesn’t burden the UTXO set, and pruned nodes automatically shed it. The chain stays complete and consistent, but spam data has no lasting effect. This is a big win for lightweight setups like mobile devices, Raspberry Pi, or other low-power systems that only need the UTXO set. Important: Core is not creating a new problem – it’s solving one. Spam like JPGs is already possible today, just currently in a way that forces every node to carry it forever. Proof: Full big JPG (size: 215kb) on a single transaction already possible : https://ordiscan.com/inscription/105662556 Related transaction: https://mempool.space/de/tx/19977355403faa1ee0a9ce7d96d4c4adbb8c2675e1a84ca999b38c06b6d4a981 Ore am i missing something here ?