UTXO bloat data embedding - Can something be done?
stacker.news·10h

Seeing a few comments asking what can be done about data embedding with unspendable UTXOs (an issue which has been around for a long time).

This is a bit long, but hopefully it will be useful as a reference to the more general question of whether you can address protocol level “problems” at the miner / policy level.

Does anyone have any suggestions or corrections?

Realistically, short of a soft fork there is very little that can be done technically, and even that would have serious limitations & fallout (that’s the whole point of this gross protocol design).

The obvious first reaction is ask miners to stop mining things like this. There are a few ways, but one would be to increase their -dustrelayfee

By default it’s 0.00003 BTC/kB (3 sat/vB) resulting in a dust output limit…

Similar Posts

Loading similar posts...