Matthew Zipkin

How did you generate the 16000 utxo? If it was all by block generation you might have this issue: https://github.com/bcoin-org/bcoin/issues/882 A useful check would be the values of the utxos....

So I tried using your wallet.zip but since the chain data is missing the wallet had issues. I recreated the conditions with [this script](https://gist.github.com/pinheadmz/832a79fcc2c50582f294f047cad958ed) which sends 32,000 1.0 HNS UTXO...

also related: https://github.com/bcoin-org/bcoin/issues/786

In an effort to keep pull requests focused on technical discussion, I invite all contributors of conceptual review to post here: https://github.com/bitcoin-core/meta/discussions/28 Please try to keep pull request comments focused...

@1440000bytes keep your comments on topic. the topic is technical. comments about people are not relevant.

Everyone needs to cool down on this pull request. 24 hour bans are next for users that mention people and not code. After that its 7 day bans.

Fee rate estimates are only available after the full node has monitored transactions entering the mempool and waiting for confirmation, over a long enough time span. I'm not sure what...

So the nodes return fee estimates as expected for some time, then just stop for some reason?

It might be helpful to have version of the affected node and debug log output. You may need to run `bitcoin-cli logging '["estimatefee"]'` to add fee estimation log output. "mempool"...

@qk-santi ok sounds like you have a clear understanding and the behavior is still unexpected. I would check two more things: - Check your bitcoin.conf for anything that might be...