I've been using the Bitcoin Core wallet for years, and this 'fee estimation is not currently possible' warning used to show up rarely. Lately, it’s becoming a regular annoyance. What’s going on?
Are you fully synced? That warning usually pops up if the client doesn’t have enough transactions in the mempool to estimate fees accurately. It might also mean some transactions haven’t been confirmed yet.
Fee estimation issues are common and they usually get fixed. But the current problems could be on your end. Don’t rely solely on the wallet's estimation, always double-check with some mempool tracking sites.
I don’t get that issue. My Bitcoin Core runs pretty much all the time, except when my laptop goes to sleep. I often set my fees manually since sites like Johoe's or mempool.space show better data than the wallet.
From my experience, a 300MB mempool shouldn’t be a big deal. If you're getting fewer TXs per second, that can slow things down a lot, especially when there's a ton of unconfirmed transactions.
It really depends on your connections and how open your peers' mempool policies are. Some platforms like Johoe and Mempool.space are super well-connected.
To address your specific issue, we’d need more details. Have you updated Bitcoin Core recently? Made any changes in your settings? How often do you usually run it?
If your node isn’t fully synced, you’ll see errors when estimating fees. If you’ve missed a day’s worth of blocks, that can definitely mess with your RPC calls.
That’s a solid suggestion. But I'd suggest using mempool.space for mempool graphs instead since it shows total size, which is more useful than just transaction counts.
That could be a better way to gauge things. But it really depends on how quickly the mempool fills up, right after a block can look very different than even 10 mins later. Core's estimates are pretty forgiving for newbies who aren’t sure what to do.