From: "Matthew Husák" <matejocraftak@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] BIP Idea: incrementalrelayfee in feefilter?
Date: Tue, 6 Jan 2026 17:36:52 -0800 (PST) [thread overview]
Message-ID: <d3ddaf1c-44c9-4ebd-98fe-88e03a84891en@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1451 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 1958 bytes --]
next reply other threads:[~2026-01-07 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 1:36 Matthew Husák [this message]
2026-01-07 18:50 ` Murch
2026-01-08 18:13 ` Matthew Husák
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d3ddaf1c-44c9-4ebd-98fe-88e03a84891en@googlegroups.com \
--to=matejocraftak@gmail.com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox