pull down to refresh
Yes, but this is a separate issue. The UTXO set is a way of presenting current state of the Bitcoin network with the minimal necessary data.
libbitcoin simply chooses to store more data than that, whereas utreexo introduces a framework where other nodes can prove that some UTXO exists and is spendable. Everyone still needs to agree that these UTXOs exist and are spendable.This proposal seems to delegate the authority to declare some UTXOs unspendable to some underdefined process/council. Basically, it proposes a framework to regularly softfork out some UTXOs at the whim of whoever gets to author that blacklist.
Edit: Oh, I see. You mean that the motivation for the fork is poor. — I agree with that.
reply
Yes, what I mean is that if the utxoset size is an issue for you, then:
If you are worried about the utxoset and you're not mining,
utreexo is a better solution. If you run libbitcoin you don't care about it at all because you basically run full txindex. If you are a miner then don't mine what you don't like. And if you are worried about other miners, buy more ASICs until they are all bankrupt.reply
Making different architectural decisions is one of the things I find most interesting about alternative implementations. It seems crazy to me that people will suggest things like their reduce data soft fork and now this cat ridiculousness to "fix" implementation details. Voskuil was making this point on X yesterday.
utxo setis an implementation choice. Ask Voskuil whylibbitcoindoesn't have it, or askutreexoabout their solution.