Bitcoin open source wallets that support replace-by-fee (RBF)

[Charles-Tim]

Do not let your bitcoin transaction remian unconfirmed for hours, days or months if you do not want to, check the mempool to know the accurate fee rate (sat/vbyte) for the best priority. To check the mempool:
For newbies, https://mempool.space/
For those that are no more newbies: https://jochen-hoenicke.de/queue/#BTC,24h,weight
For advanced users: Run full node to view the mempool. Not encouraging but actually worth it if you can, for privacy.


I am still surprised that there is option many years ago for replace-by-fee (RBF) to pump bitcoin unconfirmed transaction but many wallets are not supporting it, after many of the wallets are close source, some people that do not know much about bitcoin wallets are using them. This has resulted to many people to be complaining about unconfirmed transaction that will need an option that will be more difficult to solve, instead to use RBF, but the wallet used not support RBF. Newbies need to know what RBF is because it is the easiest means to accelerate bitcoin transaction.


Disadvantages of other means of accelerating bitcoin transactions

Free and paid accelerators
There are different ways you can accelerate bitcoin transaction, example is the free accelerator provided by mining pool like ViaBTC, another are the paid accelerator also provided by some mining pools. The disadvantages is that if the mempool is very congested, making use of free accelerator like that one provided by ViaBTC becomes difficult because more people making use of the service at the time of congestion, making your transaction not to be included among the ones to be accelerated, while paid accelerator will demand for a very high fee which makes it not possible for many people to use it, mining pool can demand for $700 or more to just accelerate a bitcoin transaction of $10, $21, $1000 or more. Paid accelerator is not an advisable option to use.

Another disadvantage of accelerator is that it is offered individually by mining pool, even if the mining pool has included a transaction to be accelerated, it would only be included in the block mined by the mining pool. If the mining pool is not contributing much hashrate, the chances it is would mine a block is low, which is the block the transaction will be included. But the mining pool will actually mine a block sooner or later.

CPFP
Another means to accelerate bitcoin transaction is the use of child-pay-for-parent. One of the disadvantages is that it may not be simple for newbies to understand. Another is that it requires more transaction fee, which means you will pay more transaction fee in accordance to the present mempool fee rate priority (sat/vbyte), the transaction weight or virtual size of the old and new transaction and the fee paid for the old transaction. But this is the best option left for those that are using wallets that do not support RBF. You can read more about it through these links:

Guides for CPFP
[Guide] Use CPFP if your stucked transactions from blockchain.com wallet
How Replace-By-Fee (RBF) and Child-Pays-For-Parent (CPFP) can speed up confirmation
[TUTORIAL]getting a low-fee transaction unstuck by creating a CPFP with electrum
RBF vs CPFP

A good SPV wallet to use for CPFP is Electrum, or any other wallet that has coin control.




What is RBF and how it works

Very simple, assuming you have made a bitcoin transaction, using a low fee, or the mempool become more congested and your transaction remain unconfirmed, you can easily pump the fee if the wallet you used for the transaction supports RBF, but not all wallets that supports it, resulting to inability to pump the fee to make the transaction get confirmed as early as possible. This is the reason for this topic, to let newbies know how important RBF is and to know the wallets that supports RBF.


Open source wallets that supports RBF

Bitcoin Core
Fully Noded
Electrum
Sparrow wallet
Bluewallet
Trezor Suite
Unstoppable wallet
Blockstream Green
Samourai
Specter wallet
Nunchuk (Disadvantage: Supporting email account registration and encrypted cloud backup). Best to backup seed phrase offline.
Wasabi
Coinb.in (not recommend for beginners). Read this and this.

Note: No close source wallet mentioned, if there is any, let me know so I can edit and correct it. No custodial wallet mentioned, because of obvious reason of not your key not your coin.

If you are using one of those non-recommendable wallets before reading this topic, and the transaction fee used is or more than 10 sat/byte (not vbyte) and the transaction size not more than 500 bytes, you can use VIABTC free accelerator. But note that if ViaBTC include your transaction, it will only be confirmed after ViaBTC mined a block if it has not been confirmed naturally by mempool decongestion.

Free BTC transaction accelerator!


Lastly, have you heard about full RBF? Nothing like that has been implemented, but maybe it would be possible in the future, you can follow this thread about it:

Full RBF

It has been implement. The mempoolfullrbf option is part of Bitcoin Core v24.0, which will be released in the coming days. I don't think it will take too long before the network starts to adopt it, especially given that miners will make more profit if they do and will lose out on profits to other miners if they don't. It won't be long before opting in to RBF is a thing of the past. Every transaction will be eligible to be RBFed - the only stipulation is whether or not your wallet software will let you do it (but you can always import your seed phrase/private keys to a better piece of software if needed).

You can read more on full RBF from the release note of the latest Bitcoin Core that was released few weeeks ago: https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-24.0.md

[1714655962]

1714655962

[1714655962]

1714655962

[1714655962]

1714655962

[1714655962]

1714655962

[OmegaStarScream]

You've also got:

- Open source: Bluewallet, Trezor suite
- Closed source: Exodus (both desktop and mobile)

There are step-by-step guides[1][2][3] if you want to include them.

[1] https://bluewallet.io/high-fees-and-transactions-pending-what-to-do/
[2] https://support.exodus.com/article/1480-bitcoin-faqs-learn-more-about-btc#bitcoin-custom-fees
[3] https://trezor.io/learn/a/rbf-in-trezor-suite-app

[Charles-Tim]

You've also got:

- Open source: Bluewallet, Trezor suite
There are step-by-step guides[1][2][3] if you want to include them.

[1] https://bluewallet.io/high-fees-and-transactions-pending-what-to-do/
[2] https://support.exodus.com/article/1480-bitcoin-faqs-learn-more-about-btc#bitcoin-custom-fees
[3] https://trezor.io/learn/a/rbf-in-trezor-suite-app

Never mind me, I knew Bluewallet and Trezor supported RBF too, but kind of forgot, or thinking I had included them both. You are right, I will include both.

I will not include Exodus, it is close source.

[bitmover]

CPFP
Another means to accelerate bitcoin transaction is the use of child-pay-for-parent. One of the disadvantages is that it may not be simple for newbies to understand. Another is that it requires more transaction fee, which means you will pay more transaction fee in accordance to the present mempool fee rate priority (sat/vbyte), the transaction weight or virtual size of the old and new transaction and the fee paid for the old transaction. But this is the best option left for those that are using wallets that do not support RBF. You can read more about it through these links:

I would also add that CPFP method only work if you control the private key of at least one receiving address, usually the change.

Lets suppose that  you sent a transaction with only one output to an exchange  (sending all your balance for example) you will not be able to sue this method.

Rbf is way better and cheaper.

[Charles-Tim]

I would also add that CPFP method only work if you control the private key of at least one receiving address, usually the change.

If the transaction do not have change address UTXO, the sender will not be able to use CPFP for the transaction, and if the coin is sent to a centralized exchange or custodial wallet, the exchange or wallet would be a disadvantage for the receiver because he (the receiver) does not has the private key and not able to use CPFP. That is true.

[Lucius]

If you are using one of those non-recommendable wallets before reading this topic, and the transaction fee used is more than 10 sat/byte (not vbyte), you can notify Lucius by posting on his thread to help you use free accelerator to accelerate it, he knows more about it and have better ways to make your transaction to be included as part of the transaction ViaBTC will include for acceleration. But note that if ViaBTC include your transaction, it will only be confirmed after ViaBTC mined a block if it has not been confirmed naturally by mempool decongestion.

As far as I can see, ViaBTC has set another condition for the transaction to be successfully added to their free accelerator, they obviously want to make free use more difficult and try to sell more paid ones.

Paste or enter the TXID you want to accelerate. The volume of a single transaction must be ≤0.5 KB, and the transaction fee rate should be ≥ 0.0001 BTC/KB.

In addition, it seems that the majority have adopted good methods when it comes to the set fees, because no one needs such services anymore, which is actually a good thing. One small note for all those who have not used RBF before, considering that for some it can be a bit confusing - when you use this option and increase the fee, don't forget to confirm the last step - click broadcast button.

For more privacy mempoolspace TOR link : http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/

[dkbit98]

There are few more open source wallets that support RBF replace-by-fee:

• Sparrow wallet
• Specter wallet
• Nunchuk

I think few more open source hardware wallets with their apps also support this, but I can't confirm for all of them.
There is also a list of RBF compatibility for various services and wallets but I don't know how updated this is:
https://bitcoinops.org/en/compatibility/#replace-by-fee-rbf

[hd49728]

With Replace by Fee, you won't have to need other satoshis left in your wallet beyond a value of your previous broadcasted transaction.

I mean if you have 0.005 BTC and you broadcast it, later you can use Replace by Fee by increasing your fee rate, but the total value of that transaction would be 0.005 BTC. It is the same value is your previous broadcasted transaction but with a lower fee rate.

Maybe some newbies will misunderstand that they need to add some more satoshis to use RBF. My two cents.

[o_e_l_e_o]

Lastly, have you heard about full RBF? Nothing like that has been implemented, but maybe it would be possible in the future, you can follow this thread about it:

It has been implemented. The mempoolfullrbf option is part of Bitcoin Core v24.0, which will be released in the coming days. I don't think it will take too long before the network starts to adopt it, especially given that miners will make more profit if they do and will lose out on profits to other miners if they don't. It won't be long before opting in to RBF is a thing of the past. Every transaction will be eligible to be RBFed - the only stipulation is whether or not your wallet software will let you do it (but you can always import your seed phrase/private keys to a better piece of software if needed).

I mean if you have 0.005 BTC and you broadcast it, later you can use Replace by Fee by increasing your fee rate, but the total value of that transaction would be 0.005 BTC. It is the same value is your previous broadcasted transaction but with a lower fee rate.

Well, the additional fee has to come from somewhere. If you aren't adding more inputs, then you have to take away from the outputs, and if you don't have a change output to take away from then you will end up paying the recipient less than originally intended.

[Charles-Tim]

It won't be long before opting in to RBF is a thing of the past. Every transaction will be eligible to be RBFed - the only stipulation is whether or not your wallet software will let you do it (but you can always import your seed phrase/private keys to a better piece of software if needed).

Which means it is still possible that if all nodes treats all unconfirmed transactions to support RBF by default, some wallets may decide not to still include the feature, but if the seed phrase or the private key of such wallet is imported on wallet that support it by default, it won't be like this time when not supported, CPFP would be used but more fee, instead, the seed phrase or private would be imported on the wallet that support RBF and be used to pump the fee using RBF. That would really be helpful, because of this, more people will dump their wallet for better ones.

[hd49728]

I mean if you have 0.005 BTC and you broadcast it, later you can use Replace by Fee by increasing your fee rate, but the total value of that transaction would be 0.005 BTC. It is the same value is your previous broadcasted transaction but with a lower fee rate.

Well, the additional fee has to come from somewhere. If you aren't adding more inputs, then you have to take away from the outputs, and if you don't have a change output to take away from then you will end up paying the recipient less than originally intended.

I did not mean about payments to others (receivers). I meant about using RBF for my own transactions so a little bit reduction in transaction value after increasing fee rate by bumping fee is not a matter.

I agree with you that if it is a transaction to a receiver that is not a sender too, the sender must add a little bit satoshi from that wallet to use RBF. Receiver will not like to receive a transaction that is less than what he should get even a few hundred of satoshi.

[Little Mouse]

Though I'm not familiar with most of them as I'm only using Electrum and Bitcoin Core for now, this is a helpful one. Thanks for this.

Note: No close source wallet mentioned, if there is any, let me know so I can edit and correct it. No custodial wallet mentioned, because of obvious reason of not your key not your coin.

What did you mean? Does any custodial wallet allow you increase the fee by any form? I can't remember if I have seen any such services or not. Also, it doesn't make a lot of sense either because custodial services usually cut higher fee than average and send with a higher fee as they send in batch.

[o_e_l_e_o]

That would really be helpful, because of this, more people will dump their wallet for better ones.

Once full RBF becomes the standard and is in common usage, then every wallet should support RBF. I'm sure there will be plenty that won't, but failing to do so at that point becomes the same as failing to support segwit addresses - a complete failure on the part of that wallet or service.

Also, it doesn't make a lot of sense either because custodial services usually cut higher fee than average and send with a higher fee as they send in batch.

And by sending in a batch, they make RBF for a single user prohibitively expensive, since that individual user would be attempt to bump a batch transaction which could be several thousands of vbytes in size.

[Charles-Tim]

What did you mean? Does any custodial wallet allow you increase the fee by any form? I can't remember if I have seen any such services or not. Also, it doesn't make a lot of sense either because custodial services usually cut higher fee than average and send with a higher fee as they send in batch.

They are custodial wallet, they may pay in batches like exchanges to gain more from their customers, so likely no custodial wallet has RBF, but possible if no batch payment and if the software of the wallet is well designed, but I do not think a custodial wallet would think in that direction. If I should conclude, no custodial wallet with that RBF feature, but the purpose of this thread is not still defeated, which is to refers only to the open wallets that support RBF, while discouraging close source wallet and custodial wallet.

[DeathAngel]

I agree, it should be more readily available to amateur investors. I read a story about a guy who was very wealthy from investing in bitcoin. He was the victim of a home invasion & was tortured to send a large amount of bitcoin to the thieves. He sent x amount of bitcoin with 0 sat/byte fee, he waited for them to go & then did RBF to an address that HE controlled.

Obviously the robbers weren’t tech gifted so went he sent the bitcoin without a fee they didn’t have a clue. He then managed to divert to coins to himself to avoid losing them. I assume he moved house so they didn’t come back when they figured out what he’d done.

[Jon_Hodl]

He sent x amount of bitcoin with 0 sat/byte fee, he waited for them to go & then did RBF to an address that HE controlled.

I am a fan of RBF but never heard of this angle before. Seems like it would just confirm before the home invaders would leave.

How did he manage to broadcast a transaction less than 1 sat/vbyte? I've been trying to figure out how to do this for an experiment but am not sure if it's possible.

Are you sure that he didn't just send with 1 sat/vbyte?

[Charles-Tim]

I agree, it should be more readily available to amateur investors. I read a story about a guy who was very wealthy from investing in bitcoin. He was the victim of a home invasion & was tortured to send a large amount of bitcoin to the thieves.

It would be good if the story points to privacy, because it is possible that if privacy is taken seriously, thieves would not have invaded his home. But people just do not care about privacy these days, unlike before when bitcoin was created.

The story is also very easy to tell, but setting zero transaction fee is nearly impossible because most people are using SPV wallets which the fee will be customized to at least 1 sat/vbyte. The thieves may use a kind of wallet that would not reflect unconfirmed transaction until it is confirmed.

I am a fan of RBF but never heard of this angle before. Seems like it would just confirm before the home invaders would leave.

Presently, no miner would take 0 fee, so expect the transaction not to confirm at all unless RBF is used to include a fee.

How did he manage to broadcast a transaction less than 1 sat/vbyte? I've been trying to figure out how to do this for an experiment but am not sure if it's possible.

You can do it on full client wallet, like Bitcoin Core.

[EarnOnVictor]

I must say that this is a very good article that would guide beginners and even some experienced Bitcoin users. I affirm all these as accurate, which makes me know the extent to which they are concise and detailed for anyone to read a short article and still gain all the needed knowledge through it.

Basically, I'm used to the Electrum wallet among your listed wallets, and it's a very good option that supports the replace-by-fee (RBF) feature. While the Child-Pays-for-Parent (CPFP) is another option to accelerate BTC transactions but has not been a good option for me due to its complexity. Regardless, what has an advantage usually has a disadvantage, and thanks for elaborately sharing the hurdles anyone could face in using all these features.

Conclusively, the high fee to execute small transactions caught my attention, and it's highly insane. This makes me advise that anyone that wants to transact Bitcoin should visit mempool to adjust the fee accordingly to their preference for completion speed to avoid unnecessary delay and extra cost.

[o_e_l_e_o]

The story is also very easy to tell, but setting zero transaction fee is nearly impossible because most people are using SPV wallets which the fee will be customized to at least 1 sat/vbyte.
You can do it on full client wallet, like Bitcoin Core.

It's not even the fact that most wallets won't let you do it, but rather, most nodes won't bother to broadcast it. Yes, you can create a transaction on Bitcoin Core which pays less than 1 sat/vbyte in fees, or indeed zero fee altogether, but given that the vast majority of nodes use the default minRelayTxFee of 1 sat/vbyte, then your transaction simply won't be broadcast through the network.

[Charles-Tim]

You do not have to wait longer when the mempool is congested or when you pay low fee, use wallets that support opt-in RBF to make transactions that support RBF to pump transaction fee which is the reason for this thread, for bitcoin users not to experience the frustration of (stuck) bitcoin transactions that do support pumping fee.

You can read more on full RBF (not opt-in) from the release note of the latest Bitcoin Core that was released few weeeks ago: https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-24.0.md

This version of Bitcoin Core adds a new mempoolfullrbf configuration option which allows users to change the policy their individual node will use for relaying and mining unconfirmed transactions. The option defaults to the same policy that was used in previous releases and no changes to node policy will occur if everyone uses the default.

Some Bitcoin services today expect that the first version of an unconfirmed transaction that they see will be the version of the transaction that ultimately gets confirmed---a transaction acceptance policy sometimes called "first-seen".

The Bitcoin Protocol does not, and cannot, provide any assurance that the first version of an unconfirmed transaction seen by a particular node will be the version that gets confirmed. If there are multiple versions of the same unconfirmed transaction available, only the miner who includes one of those transactions in a block gets to decide which version of the transaction gets confirmed.

Despite this lack of assurance, multiple merchants and services today still make this assumption.

There are several benefits to users from removing this first-seen simplification. One key benefit, the ability for the sender of a transaction to replace it with an alternative version paying higher fees, was realized in Bitcoin Core 0.12.0 (February 2016) with the introduction of BIP125 opt-in Replace By Fee (RBF).

Since then, there has been discussion about completely removing the first-seen simplification and allowing users to replace any of their older unconfirmed transactions with newer transactions, a feature called full-RBF. This release includes a mempoolfullrbf configuration option that allows enabling full-RBF, although it defaults to off (allowing only opt-in RBF).

Let us see what would happen has full RBF is on the latest version of Bitcoin Core, if node runners will support it (mempoolfullrbf=1) which will later make opt-in RBF not necessary.