Why Slow Transaction Propagation is a Problem

Check out testnet3 and mempool.space. It's wild how it shows mempool state vs what your node sees. You'd think that once your node finishes downloading the whole blockchain, it grabs all those pending transactions. But nope, it doesn’t work like that.

Honestly, it seems like a risky overreaction to a small issue. Just let your node chill for a day or two, and it’s all good. If you're worried about brief downtimes, the mempool saves the state, so not a big deal.

Totally agree! It's crazy how different the numbers are on mempool.space versus what you see on your own node. New miners often create empty blocks, and it’s a huge oversight.

I’m with @gmaxwell here. Most of the time, Bitcoin Core is about maintaining what’s already there rather than adding new stuff. If miners face issues, it's for a couple of days max. Non-miners should probably just stick to pools.

But wait, your node might have a different mempool policy. You could miss out on profitable transactions just because of that, and it's frustrating. Without the full block info, you can’t really measure anything properly.

This isn't just about testnet3 anymore. If you’ve got more incoming transactions than confirmations, good luck catching up. It’s weird but true, and it leads to high-fee transactions getting stuck while newer, cheaper ones take over. That’s just how it is.