pull down to refresh

I can see that @petertodd is suggesting that utxo bloat is a direct consequence of the OP_RETURN standardness limit, which appears a rational argument at first glance. How would I be able to verify this using my own node?
You can't. The UTXO set itself, what your node stores, doesn't tell you anything useful about why a transaction was created.
You have to think about this for yourself, e.g. by looking at projects using Bitcoin and understanding what they're doing and why.
reply