Bitcoin Core 22.0 walletrbf=1 in bitcoin.conf is ignored

[becoin]

As I understand RBF should be enabled by default but it is not. All "category": "send" transactions show "bip125-replaceable": "no". I have put walletrbf=1 in bitcoin.conf file and restarted bitcoind but no change. Are there any changes in RBF functionality from previous versions I have missed?

[1715507667]

1715507667

[1715507667]

1715507667

[1715507667]

1715507667

[1715507667]

1715507667

[1715507667]

1715507667

[1715507667]

1715507667

[achow101]

Are the transactions you are looking at unconfirmed? It is only "yes" for unconfirmed transactions as only unconfirmed transactions can be replaced.

[nc50lc]

Are you using the GUI?
Because there's an "Enable Replace-By-Fee" check-box below the 'Send 'tab that will override the default and bitcoin.conf settings if it's unchecked.

[becoin]

Are the transactions you are looking at unconfirmed? It is only "yes" for unconfirmed transactions as only unconfirmed transactions can be replaced.

Hmmm... Haven't thought about that! Transactions are confirmed. Just tested and for unconfirmed transactions it is "yes", so walletrbf works as expected. Although, it is a bit counter intuitive if "bip125-replaceable" key/value (yes/no) still exists for confirmed transactions. Maybe something like "was-yes/was-no" for confirmed transactions is better? Thanks for responding, achow101.

Are you using the GUI?

Using bitcoin-cli. Thanks for responding too!

[HCP]

Maybe something like "was-yes/was-no" for confirmed transactions is better?

It's not very useful though. A confirmed transaction is confirmed, so it makes zero difference at that point whether it was replaceable... as once it is confirmed, it can't be replaced.

I can't really think of a useful purpose for a "was-yes/was-no" indicator outside of possibly testing that the flag was being set correctly... but it should be easy enough to simply generate a transaction and not broadcast it to see if the flag is being set as intended.