Hi all! 

Core 30.0 defaults both minrelaytxfee and incrementalrelayfee to 0.1 sat/vB 
now, but lots of nodes still run 1 sat/vB for incrementalrelayfee (or other 
settings).

*Problem 1*: You send RBF tx → your node accepts → peers reject 
replacements → dead end.
*Problem 2*: You can't see what min RBF fee peers have.

The obvious fix is to manually connect to peers with matching 
incrementalrelayfee, which is impossible because this policy isn't exposed 
over P2P. BIP133 feefilter only signals minrelaytxfee.

*Proposal*: Extend feefilter with incrementalrelayfee field (parallel to 
minrelaytxfee). Peers can then filter out un-bumpable RBF invs, reducing 
spam and improving propagation.

*Benefits*:
- spam protection: your node stops spamming peers with un-bumpable RBFs
- transparency: you can see what RBF policy other nodes use, thus you can 
find miner node which you can add as manual peer
- pure policy change, no consensus risk

*WDYT guys?*

Happy to prototype or draft a BIP if there's interest.

Cheers,
Matt.

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/d3ddaf1c-44c9-4ebd-98fe-88e03a84891en%40googlegroups.com.