From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 06 Jan 2026 17:38:07 -0800 Received: from mail-oa1-f59.google.com ([209.85.160.59]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1vdIUw-0004jQ-NX for bitcoindev@gnusha.org; Tue, 06 Jan 2026 17:38:07 -0800 Received: by mail-oa1-f59.google.com with SMTP id 586e51a60fabf-3ed1786c9dfsf2840219fac.1 for ; Tue, 06 Jan 2026 17:38:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1767749880; x=1768354680; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:sender:from:to:cc:subject:date :message-id:reply-to; bh=ixm4tm92IFwGMvNuP2o34I+eBrpLmRD85s9AN7+QsNw=; b=GbzM4XImsOcnSHUXCKZMQftHnczNxrBeUozuEcDJ+h0HhsBZenI4Cke57/P19XHX26 fxAnamhG2bfnqVt6y2jd3l49VnN/Hz6n7pzcSONprKywshnxrz2LkoXfa76xTSGP6XQd 7hRW7E9KP1YDcKovve9RbZTfUFeOiuwDb5DqD5PwYwl7lfv4Z3kA4Focz9RCDfd9YR4J am6+ok5ssXi5it1TCiLyQ59Cfia8NhwjX5PIDiLbIDyNDZUmnMmB0QkguHaKONyIN+5W s3w9dK1dS5y09uzQUhroFjqLa8aSPoVw73ms19R9ISHY3SxwgQixTPrBpLFQm6PTZuW8 kLjw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1767749880; x=1768354680; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:from:to:cc:subject:date:message-id :reply-to; bh=ixm4tm92IFwGMvNuP2o34I+eBrpLmRD85s9AN7+QsNw=; b=BpdSuVOrUDm675VJwspmRgy8CR3pXTk/UN9eX8aZQ1UJmY/lH+NfIiiA+i4w0aeebg 8y0rRsyVu0gO6GxGY2hOHxC1He0QmURAtVhSoV7HrOSpDRDEuMS2RTlMCWZu/6yWPiTa HFkc0hjG9+1HKz64yAk6fhYtEb/tSaK0RX5XeyiNlU7dtknb4hwqHxLaxrSbxEkcIPXl i2gf+pC3KwvyF2g+pf/cZxrt69nHOm64kilO2QN1yZr1FX/Lj4dO8Hi0uYi4bXcerWJ0 E7bDTnJ5Cb2vNy1NGLyLt9bNrBs7SCi2srTY7+0wxadfwmFQbQBbInzZqLIDzV6A41+F YMOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1767749880; x=1768354680; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:x-beenthere:x-gm-message-state :sender:from:to:cc:subject:date:message-id:reply-to; bh=ixm4tm92IFwGMvNuP2o34I+eBrpLmRD85s9AN7+QsNw=; b=VQdVdWLn8u+BRFuB3fgP+bbAHyKKBlWLemnn7nt8EOnEocTUfHDjGJ0J0YijrgGQvV 6lexF0Lmh8SB9Coxb/Yr66nMSjZzM6GhyDQItgqVbDn7b7Uu/BYaRE+K2egq2SU6pZcx 8C6lzp3+nFBqshX+dkwnOJkHjef2RLdPiC9sDRZ2goRZQueFWnATLuRTkyhn5FQ44oDY AhpivtMbbzfdbAjWSObxiszOV9K/CuAOd8bY7BVc/18hgUgISSM2fUkCjkLKgMIlHl8N P5ZZwC9OR1XxWzzcSle/rU+ib+LH6x6zRLAI0uR6Kxzlo7OTqNjibA0bHbVnslN9gF1X C78g== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCWd6U9SFo1jqbAbrTHCFa/bTr/mGJP/QlsS7vOnmmGO64KvVxqfqMhrp/e14TlncMveg8D/zdpaD2qD@gnusha.org X-Gm-Message-State: AOJu0YzSD8vv5tsWZfnuzy4VH3oikKAUu5FsczySD5LpSkzF1m24JIlX /7J0FsqIA65eOwCgmfXmKTymB0x5nlu/vCU7hllII1qXILCZ4kYzNq7H X-Google-Smtp-Source: AGHT+IGEsMOS+v1qQ+42KahAgB6teqtlKYVZBp3dti9lhs/DLLOuKPXF1DKRv0oPw1tVacdAriFpdw== X-Received: by 2002:a05:6870:224f:b0:3f5:d024:250a with SMTP id 586e51a60fabf-3ffc0953d4dmr504807fac.20.1767749879935; Tue, 06 Jan 2026 17:37:59 -0800 (PST) X-BeenThere: bitcoindev@googlegroups.com; h="AWVwgWaM7AzbGcdsLw4V9OoD11EgpTYBbDulKa3J2Qu8cf5Mpw==" Received: by 2002:a05:6870:730b:b0:3e8:4817:7a50 with SMTP id 586e51a60fabf-3ff9d80a090ls861048fac.0.-pod-prod-05-us; Tue, 06 Jan 2026 17:37:55 -0800 (PST) X-Received: by 2002:a05:6808:2394:b0:450:c648:4aeb with SMTP id 5614622812f47-45a6be8a379mr388237b6e.44.1767749875164; Tue, 06 Jan 2026 17:37:55 -0800 (PST) Received: by 2002:a05:690c:688c:b0:786:8d90:70d8 with SMTP id 00721157ae682-78fb3c672f8ms7b3; Tue, 6 Jan 2026 17:36:54 -0800 (PST) X-Received: by 2002:a05:690c:6e90:b0:78c:3007:dabf with SMTP id 00721157ae682-790b5772e10mr10651627b3.27.1767749813312; Tue, 06 Jan 2026 17:36:53 -0800 (PST) Date: Tue, 6 Jan 2026 17:36:52 -0800 (PST) From: =?UTF-8?Q?Matthew_Hus=C3=A1k?= To: Bitcoin Development Mailing List Message-Id: Subject: [bitcoindev] BIP Idea: incrementalrelayfee in feefilter? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_724212_1278305295.1767749812873" X-Original-Sender: matejocraftak@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_Part_724212_1278305295.1767749812873 Content-Type: multipart/alternative; boundary="----=_Part_724213_1979778812.1767749812873" ------=_Part_724213_1979778812.1767749812873 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all!=20 Core 30.0 defaults both minrelaytxfee and incrementalrelayfee to 0.1 sat/vB= =20 now, but lots of nodes still run 1 sat/vB for incrementalrelayfee (or other= =20 settings). *Problem 1*: You send RBF tx =E2=86=92 your node accepts =E2=86=92 peers re= ject=20 replacements =E2=86=92 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=20 incrementalrelayfee, which is impossible because this policy isn't exposed= =20 over P2P. BIP133 feefilter only signals minrelaytxfee. *Proposal*: Extend feefilter with incrementalrelayfee field (parallel to=20 minrelaytxfee). Peers can then filter out un-bumpable RBF invs, reducing=20 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= =20 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. --=20 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 e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= d3ddaf1c-44c9-4ebd-98fe-88e03a84891en%40googlegroups.com. ------=_Part_724213_1979778812.1767749812873 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all!=C2=A0

Core 30.0 defaults both minrelaytxfee and incr= ementalrelayfee 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 =E2=86=92 your node accepts =E2=86=92 peers reject replacements= =E2=86=92 dead end.
Problem 2: You can't see what min RBF fee = peers have.

The obvious fix is to ma= nually connect to peers with matching incrementalrelayfee, which is impossi= ble because this policy isn't exposed over P2P. BIP133 feefilter only signa= ls minrelaytxfee.

Proposal: Extend feefil= ter with incrementalrelayfee field (parallel to minrelaytxfee). Peers can t= hen filter out un-bumpable RBF invs, reducing spam and improving propagatio= n.

Benefits:
- spam prote= ction: your node stops spamming peers with un-bumpable RBFs
- tra= nsparency: you can see what RBF policy other nodes use, thus you can find m= iner node which you can add as manual peer
- pure policy change, = no consensus risk

WDYT guys?
<= div>
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 &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/d3ddaf1c-44c9-4ebd-98fe-88e03a84891en%40googlegroups.com.
------=_Part_724213_1979778812.1767749812873-- ------=_Part_724212_1278305295.1767749812873--