From: rkrux <rkrux.connect@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Removal of BIP 125 RBF signalling in wallet transactions
Date: Wed, 10 Jun 2026 22:43:42 -0700 (PDT) [thread overview]
Message-ID: <212d5db3-7521-4afd-a551-fda8a6ef09c9n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1498 bytes --]
Hello list,
There is an intention in the bitcoin core wallet to remove the
BIP 125 RBF signalling[0] in transactions for which a PR is raised[1].
The primary reason for its removal is because ever since fullrbf
became the default In bitcoin core nodes in v28.0 two years back,
this signalling has become redundant.
However, a point[2] was raised in the review of the above PR that
the default input sequence number should be the one that's agreed
by the wide wallet community as a best practice. It would be helpful
if other wallet developers can share if (when) they have plans to
remove this explicit BIP 125 signalling for RBF in transactions.
It's also an intention[3] to share an informational BIP later that
highlights a recommended input sequence number in transactions.
Looking forward to replies from wallet developers in the list.
[0] https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki
[1] https://github.com/bitcoin/bitcoin/pull/35405
[2] https://github.com/bitcoin/bitcoin/pull/35405#issuecomment-4634469619
[3] https://github.com/bitcoin/bitcoin/pull/35405#issuecomment-4675005759
- rkrux
--
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/212d5db3-7521-4afd-a551-fda8a6ef09c9n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1974 bytes --]
reply other threads:[~2026-06-11 9:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=212d5db3-7521-4afd-a551-fda8a6ef09c9n@googlegroups.com \
--to=rkrux.connect@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