Replying to Avatar SPA (Super Phat Arrow)

That wouldn't need to happen if all nodes had mempool policies that didn't restrict valid transactions. Filters are pointless if they don't filter. Knots nodes have to ask for confirmed TX that they should have already known about from the first broadcast, but rejected. Bad peer! Disconnect!
Avatar
/dev/fd0 4mo ago

Some mempool policies in core will always restrict transactions for various reasons. They still exist in core.

In an ideal world all nodes will have the same mempool but it's not the case in reality.

Rejected transactions are saved but not relayed and there are options to set the size in knots: https://github.com/bitcoinknots/bitcoin/blob/v29.1.knots20250903/doc/release-notes.md#p2p-and-network-changes

Reply to this note

Please Login to reply.

Discussion

Avatar
SPA (Super Phat Arrow) 4mo ago

So there is "spam" in your knots mempool, you just don't tell others about it?

Or is it cached somewhere else?

Avatar
/dev/fd0 4mo ago

Cached in memory but it's separate from mempool.

Avatar
SPA (Super Phat Arrow) 4mo ago

I see. Thanks, I didn't know that.

I would still rather not peer with any knots nodes because they won't tell me about valid transactions that are likely to be mined.

Avatar
Super Testnet 4mo ago

Have fun staying Core

Avatar
SPA (Super Phat Arrow) 4mo ago

Thanks 🤣