#runningknots 
Discussion
OP_RETURNs are easier on your mempool.
OP_RETURNs are the worst way to store images and whatever else you have in mind (expensive).
OP_RETURNs are immediately prunable from the UTXO database since they can never be spent
OP_RETURNs are more honest than fake addresses or other data-embedding tricks that pollute the UTXO set
OP_RETURNs are easier to filter and identify compared to data hidden in other transaction components
OP_RETURNs don't require address validation, simplifying transaction construction for data-only purposes
OP_RETURNs are transparent about their purpose as they clearly signal "this is data, not a payment"
Exactly. Bitcoin is money network, not data. Run Knots.
bitcoin is bitcoin, not a storage protocol.
100%. I Will never run Core v30.
And your knots code will still let through any non monetary transactions ^^
No shit sherlock. Yes you are right.
The point is that if you want to store data you were always able to. You can create a merkle tree with a spending condition that's actually an image and do that. It's cheaper than OP_RETURN, and impossible to block.
E.g.: https://github.com/stutxo/labitbu
Run core.
Damn, you educated me man 🏳️🌈. Any other gems of wisdom?
I actually hate ordinals and all the other shit that treats individual UTXOs (or worse, individual sats) as anything other than what they are... But I also acknowledge the reality of the situation
🧡