We can already just run knots and prune Op_return data over a certain size.

I think the point here is to store in fast memory only transferable utxos for waxwings project which is join markets.

Also, I do agree with you that not storing such data on one's nodd is appropriate and undermining the garantee that JPEGs will be findeable would froce them to run full nodes.

Reply to this note

Please Login to reply.

Discussion

Core prunes op_return since 0.10 something

It's not about pruning data. It's about UTXOs that have to be held in memory and increasing the resources needed to run a node. Or maybe i missed the point too.

https://studio.glassnode.com/dashboards/btc-utxo-set

What I meant is that core will not store those in the utxo set at all

Indeed, important to mention OP_RETURN, but iirc Stamps followed the example of Counterparty and did not use it, specifically to avoid being pruned (though the history of this is complex and controversial).

Yes, they do use bare p2ms, which is not pruned. But the last time I've checked, the ordinals was the actual problem, because people crate a ton of small amount (10k sats) UTXOS to "hold" inscriptions.

If you roll the numbers, small size p2tr dominates this recent surge in UTXOs

Right, i see. I guess what I'm saying in the OP applies mostly to them.