At height 944003 btcd has ~8K utxos less than bitcoind v31, for example, the outputs of the tx ebc9fa1196a59e192352d76c0f6e73167046b9d37b8302b6bb6968dfd279b767 are present in the utxoset of bitcoind, and not in btcd.
This difference breaks with the generation of the same utxoset hash that bitcoind generates for assumeutxo. Changing btcd to store these utxo's will fix the issue and enable us to compute the same hash.
There are 165067399 utxos stored at the height 944003, so even 10000 utxos would represent an insignificant part of the utxoset size, in other words, storage and lookup speed can not be used as a justification for this difference in the behavior, there's no significant improvements provided by avoiding invalid scriptpubkeys in the utxoset.
At height 944003 btcd has ~8K utxos less than bitcoind v31, for example, the outputs of the tx
ebc9fa1196a59e192352d76c0f6e73167046b9d37b8302b6bb6968dfd279b767are present in the utxoset of bitcoind, and not in btcd.This difference breaks with the generation of the same utxoset hash that bitcoind generates for assumeutxo. Changing btcd to store these utxo's will fix the issue and enable us to compute the same hash.
There are 165067399 utxos stored at the height 944003, so even 10000 utxos would represent an insignificant part of the utxoset size, in other words, storage and lookup speed can not be used as a justification for this difference in the behavior, there's no significant improvements provided by avoiding invalid scriptpubkeys in the utxoset.