Topic: Bitcoin open source wallets that support replace-by-fee (RBF) (Read 1558 times)

You are right. I have been testing the wallet since I saw your post about it few months ago and I noticed it is a good wallet which is open source. I just decided not to add USDt to my review because this thread is completely about bitcoin. Same as when I added wallets like Unstoppable. Blockstream Green is also supporting few altcoins. I thought if people use it, they will find out about those altcoins by themselves.

And you can easily swap L-BTC to main chain Bitcoin directly in the wallet, or to L-USDT if you want to have stablecoins for some reason.
I wouldn't suggest holding a lot of coins in this hot wallet, but it works good for accepting payments in Liquid and Lightning and than moving then on-chain.

I am adding another bitcoin wallet.

Aqua wallet. You can read about its opt-in RBF support on the release note of the updated version (version 0.2.0) on GitHub: https://github.com/AquaWallet/aqua-wallet/releases

The wallet is supporting bitcoin onchain transactions, lightning network and liquid network.

It is worth knowing that L-BTC which is the liquid network is not actually BTC but not also an altcoin because it is more of layer 2.

Sending the full amount works, or combining multiple payments, or sending the change to an exchange (so it's someone else's problem). Sometimes I send it to an online account where I can use the balance later.
Obviously this doesn't always work, and for small payments I avoid using Bitcoin if possible. I don't like it, but I like Bitcoin too much to waste it on high fees

This looks more like a issue with Bitcoin Core wallet than with RBF itself.
I guess you could freeze all other addresses in your wallet to make sure they won't be sent without warning.[/quote]
Yep, it's a Bitcoin Core thing. I now know, so I won't let it happen again.

How are you avoiding change?
Only way I know is by sending full amounts, but in situations like that I wish bitcoin was more like monero.

This looks more like a issue with Bitcoin Core wallet than with RBF itself.
I guess you could freeze all other addresses in your wallet to make sure they won't be sent without warning.

On Electrum, I can select 'decrease payment' for both bump fee and cancel transaction if I want the additional fee to be deducted from the coins in the transaction (which would be replace by another transaction).

RBF has it's downsides for privacy: I always use coin control, and I try to avoid change. So when I used RBF in Bitcoin Core, it took another input, and added it to my transaction. I didn't expect that, and didn't get a warning about it. It's bad for privacy, and lead to a much larger transaction: 2 inputs and 2 outputs instead of 1 input and 1 output.

Ever since the release of Bitcoin Core 0.14.0 that the RPC command bumpfee can be used - if one uses bitcoin-cli - in order to increase the fee that was used in a specific transaction (as long as it had Replace by fee enabled). In order to increase the fee by using CLI, per bumpfee documentation[2], you have to respect the following command:
Usually people have trouble with the (options] argument because it is classified as a JSON object ant when constructed incorrectly can output errors such as "Error parsing JSON". An example of a command to bump the fee of an unconfirmed transaction in 40 sat/vB would be:
If you're using the GUI version of Bitcoin Core, things are more user friendly - Ever since Bitcoin Core 0.15.0[3] there is a graphical option for a user to replace the fee of an unconfirmed transaction (assuming it has RBF enabled) by just going into the menu Transactions -> Right-Click on the unconfirmed transaction -> Choose Increase Transaction Fee and then choose the desired sat/vB rate.

---

[1]https://bitcoincore.org/en/releases/0.14.0/
[2]https://bitcoincore.org/en/doc/0.21.0/rpc/wallet/bumpfee/
[3]https://bitcoincore.org/en/2017/09/01/release-0.15.0/

Unstoppable wallet has added replace-by-fee and also cancel transaction.

You can use cancel transaction on some wallets like Electrum but it means that you will double spend the unconfirmed transaction with higher fee in a way that the coin will be sent back to an address on your wallet.

I am sorry for this late reply. I am not a Bitcoin Core user. But if you can can provide a guide for it, I can add it somewhere in the OP.

Maybe  someone can provide a link to the detailed  guide for RBF or CPFP in bitcoin core wallet?

Bump

It happened in the past, but there is probability that it may not happen in the future, yes. But the probability that it will happen in the future is far higher than the probability that it will happen in the past. In 5 : 95, 5 is still a probability.

Ordinals spam like Ordi with a marketcap of over $400 million. Also are others but with lower marketcap. What if the bull run starts and these Ordinals and Inscriptions started to increase in price with increase in daily transaction, and which is most likely what will happen. The probability that the mempool will be more congested during the next significant bull run is far higher than it will not be congested. Even without Ordinals and Inscriptions, it was congested in the past.

I think you are talking about the period after every halving, i get your point, but what i am saying is, just because it happened in the past, doesn't mean that it would definitely happen in the same way in the future. So many things can and will prolly happen before we get to that time, the Ordinals spam may/may not survive until then and the activity that is expected in the Bitcoin network at that time may not also happen, this is the reason why it is somewhat impossible to accurately predict the state of the network at a future time.

Because the mempool was congested during those periods in the past, but after weeks or months it will become less congested. But there were no Ordinals and Inscriptions like BRC20 tokens at the time. Yet, congested. With them this time, it is not going to be easy at all.

Yes you can do this, but another thing is, why would you even want to keep on using the seed phrase of a wallet which doesn't support RBF. There are basic features that a wallet should have, and if they lack it; then you should choose alternatives that are better, create a new wallet in them and send your funds into the new wallet.
Why do you think so? What makes you think that the network would be clogged at these times you just said above, i am not saying it cannot happen, but what i know is that you cannot predict what the state of the network/mempool would be like at a future time.

@hosseinimr93 has answered you already.

But it is worth knowing that people that are using close source wallets (like Trustwallet) should better create a new seed phrase, keys and addresses on an open source wallet. This is because you do not know how your keys are generated. The public do know  how it is generated, maybe it it is generated by the wallet developers or not, or not secure enough like what happened to bx.

If you import a seed phrase from a wallet that does not support replace-by-fee to a wallet that supports it, and you make transaction after you import it, you have have nothing to be worried about as all transactions you will be making on the new wallet will support RBF, unless you disable it from the setting or preference. But I will just advise you to send your coins to an address or addresses generated by the seed phrase of an open source wallet that support RBF if the old wallet is close source or not trustworthy.

Yes. You can import your private key/seed phrase in a wallet that supports RBF, so that any transaction you make is flagged as RBF.
Just take note that if you have already made a transaction using a wallet that doesn't support RBF, your transaction will be still RBF-disabled, even if you import your private key/seed phrase in a wallet that supports RBF.

The real congestion have not even started yet, wait till end of 2024 and into 2025, we will see things that will bing new discussions to the forum for months to come, thanks for sharing wallets that supported RBF and it doesn't even take too long that I knew this myself.

I am used to mempool dot space for checking the min and max transaction fee for Bitcoin, since I don't want my transaction to wait around unconfirmed I always go with the mid to max, and I haven't had any problem, the thing is it will be hard for people who are used to a wallet with no RBF to move over.

My question now is can someone import their private key or recovery seed of a Bitcoin wallet that has no RBF function into a Bitcoin wallet that supports RBF? Will the function be available coming from another wallet with no issue? I will like to know.

---

By the way, this is a nice write up OP...

Wasabi wallet added.




https://docs.wasabiwallet.io/using-wasabi/Send.html#speed-up-or-cancel-transaction

Essentially yes. The wallet is generated based on two human created and memorized strings - an email address and a password.

Some will use cryptographic PRNGs of varying security, but if the wallet can still be accessed using a username/email and a password via a website then it remains highly insecure.

I have removed coinb.in.

What can this type of web wallet be called? Is it not HD brain wallet? Or is this how other web wallets are generating their seed phrase as I can see them all requiring username and password?

Although web wallets are the most vulnerable means to generate bitcoin wallets and they are the most vulnerable wallets.

I would concur with hosseinimr93. coinb.in should be viewed as a tool for advanced users to construct transactions or addresses with particular unlocking scripts, and to broadcast transactions if necessary. It can also be used by advanced users on an airgapped device as a tool for signing transactions. It should never be used as a wallet because web wallets are not secure, even if they generate entropy properly and not via an email and password which is a terrible idea.

I wouldn't put coinb.in on any list of recommended wallets, especially not one targeted at beginners.

In the case you are referring to the wallet tab in coinb.in, note that your address is generated from the combination of your email address and the chosen password and due to obvious reasons, it's not a good method for generating a wallet. As you surely know, you should generate your wallet from a completely random entropy.


Coinb.in is a great tool for building the raw transaction and it allows you to flag your transaction as RBF, but I would never recommend anyone to use it for generating a wallet.


That's not possible, if you have signed your transaction before and you want to use coinb.in only for broadcasting the transaction.
Take note that with any change in transaction data, the signature becomes invalid and there in no way coinb.in can flag your transaction as RBF, if the transaction you have signed isn't RBF-enabled.

If you have a signed transaction which hasn't been flagged as RBF and you want to broadcast a RBF-enabled transaction using coinb.in, you should build a new tranaction, flag it as RBF and sign it again.

I added https://coinb.in

I have not used this JavaScript wallet before, but if you click on advanced option while using it to generate a wallet, the RBF is checked and you will be able to use it to make transactions that support RBF.

It supports multisig. You can use it to create, verify, sign and broadcast custom raw transactions online. It has fee calculator. You can also use it offline.

If there is any reason not to add it, please let me know.

I do not know yet if the RBF is applied only when you use the JavaScript to generate wallet, or it also applicable when you used the site to broadcast a signed transaction. I hope someone will make this clear, or I will test it before this week is over.

I used https://mempool.space for it and I saw 151 sat/vbyte when I posted it.

When you posted this just not quite long, the fee rate was at 40 sat/vbyte on https://mempool.space.

https://jochen-hoenicke.de/queue/#BTC%20(default%20mempool),24h,weight is for advanced users and I will recommend newbies to still use https://mempool.space until they understand how to use the former.

This thread is about RBF. I still do not see what you are trying to prove over what is unnecessary. I will try all the best to make this readable for newbies.

Mempool now at 26 sat/vbyte and still getting lower. Newbies can easily use https://mempool.space to check the fee rate.

I wanted to inform you that you gave not clear information.
When you mentioned mempool is at 151 sat/vbyte, what is mempool at that fee rate? You did not mention about it, with 151 sat/vbyte, it is 1 vMB from tip of mempool or 50 vMB from tip of mempool. The second part is important because it will help us to know what is an affordable fee rate to use at that time.

No offense but I hope you understand my contribution. Your information is not enough and not enough can be considered as not accurate.

Like now, I can write mempool is at 200 sat/vbyte but it is 0.121 vMB from tip of mempool and I can use a lower fee rate like 50+ sat/vbyte (0.823 vMB from tip of mempool) to get a confirmation within next 1 or 2 blocks.

You later saw what happened. But that is not the main discussion. This is about the importance of RBF. I was only explaining how RBF can be helpful to increase transaction fee so that stuck transaction or transactions that are not likely to be confirmed early can be replaced by high fee one so that such transaction will not be stuck and remain unconfirmed for longer period of time.

Maybe you have forgotten that I included that in the OP: https://ninjastic.space/topic/5422456.0

151 sat/vbyte is at very tip of the mempool but it is not a highest fee rate used in waiting transactions in mempool currently or last 24 hours. The highest values are somewhere from 250 to 300 sat/vbyte (last 24 hours).

By mentioning 151 sat/vbyte, you are making newbies panic. They actually can get a confirmation in a next one to two blocks with 70+ or 80+ (80+ is better choice) sat/vbyte.

• https://jochen-hoenicke.de/queue/#BTC%20(default%20mempool),24h,weight
• https://mempool.space/graphs/mempool#24h

First they should not use wallets in online accounts that are custodial wallets usually. With such wallets, they don't have Coin control feature so sure not have choice to control fee rate too.

• Reminder: do not keep your money in online accounts

RBF makes bitcoin transaction to be easy, you do not need to have frustration of stuck transaction after you have used low fee. If the fee used is low when the mempool is congested, you can pump the fee.

The mempool is at 151 sat/vbyte now. Because of RBF, I can use a fee rate of 20 to 30 sat/vbyte or lower fee rate and still be able to pump the fee if no confirmation within the time I am expecting.

People should not be using wallets that do not support RBF.

Transactions of 1 sat/vbyte are getting confirmed today, but there is nothing bad to still use a wallet that support opt-in RBF so that you will be able to pump the fee in times of mempool congestion. The mempool can get congested at anytime, RBF is very useful.


Instead of unwanted stuck transaction, you will be able to pump the fee if using any of these wallets.

Do not mind me that I was using Electrum seed phrase to test it, actually I can use opt-in RBF on Electrum directly, which means importing it on Bluewallet is not necessary. But I was still surprised that there is such limit.

I used the seed phrase that was generated from Electrum directly it shows this:





But while I used a BIP39 seed phrase, it shows this:





Another disadvantage is when your incoming transaction is still not confirmed, if you use BIP 39 seed phrase, you will see pump fee, but which is the use of CPFP.

     



Nothing like that if you import Electrum seed phrase. But also not necessary because that can be done directly on Electrum:




Also that CPFP can be done on all wallet that supports spending of unconfirmed transaction.

Personally, I did not have any problems in the past, but I know many cases in which fraudulent operations took place, the basis of which was that a buyer was ignorant of the basics of the protocol and did not bother to seek the help of an experimenter. Perhaps it is fortunate for those who use the wallets of the trading platforms because the transaction does not appear on their applications until after at least two network confirmations, but this remains impractical in the case of urgency since the transaction cannot be accelerated using the wallet of the platform. This may be one of the reasons for the rise in the use of altcoins (USDT in particular).

I don't understand why would they want to limit the user this way but you're probably right. I just tried to send some funds from my Bluewallet, and both (bump and cancel) buttons are showing.

This is what I did. I import Electrum seed phrase on Bluewallet, I made the transaction on Electrum for testing. I saw the transaction on Bluewallet and I click on the transaction for me to be able to pump the fee, I did not see pump fee and cancel transaction. This is what I saw:



I checked the settings to know if RBF is by default or not but I did not see anything. This makes me think that it is by default. But I was unable to pump the fee.

Or maybe it is because I did not broadcast the transaction on Bluewallet. I do not know yet. I will make transaction on Bluewallet directly to know if it is because of it or not.

---

Edit:

To be able to pump the fee, the image supposed to be like this as I saw it from the Twitter video that Lucius posted as it includes 'pump fee' below which can be clicked on the pump the fee

In fact, it is "Bump fee" if we are to be precise, and that is what it says on the sample screen you posted

---

The matter should have been quite simple if you want to bump the fee of your transaction, the RBF option is enabled and you have enough funds to increase the fee. I've never had that wallet, but here's their little tutorial -> BlueWallet RBF

Before, if I receive bitcoin even from a stranger, provided if the transaction does not support RBF and the person uses high fee for it in a way the transaction can be included in the next block most probably, I can accept 0 confirmation. But after I have been reading about full RBF on this forum, I have changed my decision about that. At least, I prefer 1 confirmation now.

If the transaction supports RBF, I too accept 1 confirmation. If the amount sent is very high, I will wait until 6 confirmations too just like you.

Exactly. Thanks for providing that. @dansus021, if you follow Leo's comment, this image will appear:



Click on 'Options'.



Click on 'Pump fee'.

---

I was thinking I will be able to pump the fee on mobile Bluewallet, but unfortunately I was not able to. Or is there anything I am getting wrong?

I would just like to add that the procedure does not end with choosing a new fee and signing the transaction, but the final step is to send the transaction by clicking on the "broadcast" button. I know it seems simple and logical, but some users simply overlook the final step and wonder why that option doesn't work for them.

You can use RBF on Electrum for Android.

When making a transaction, make sure the checkbox for "Final" is left blank (this is its default setting). This will enable RBF. Then, if you need to bump your fee, on the "History" tab you simply tap on your unconfirmed transaction, tab "Options" at the bottom left, and then select "Bump fee" and choose your new fee.

Whenever I receive bitcoin from a stranger (which would be someone that either I do not trust or that I don't know their name or their address), so far I have always waited for at least one confirmation prior to giving over anything of value, such as cash.. so it is up to them if they pay a higher fee in order that they do not have to wait for the one confirmation.

Of course, if the transaction was for something that I considered to be great value, then I might wait anywhere between 3 and 6 confirmations... but most of the time, I have been o.k. with waiting for 1 confirmation, and I always disclose that before accepting payment in bitcoin.. and surely if the person was  friend or a family member, then I would not need to worry about getting at least one confirmation before transferring the item of value (or money).

Maybe none of us are experts, so sometimes issues can end up coming up, and I have had some issues in the past when dealing with strangers in which mistakes had been made, and surely some people are more honest than other people in terms of correcting the mistake.. to the extent that the mistake had not either been intentional or that once the mistake had been discovered, then sometimes people might NOT end up doing "the right thing" in terms of rectifying the situation.

It also curious me is there an android wallet that support this method Im fine if the wallet is closed source because I'm gonna using it for Hot wallet not hold a long period of time.

I know the method only Child-Pays-For-Parent (CPFP) but I just know RBF on mempool space, by using Native segwit transaction is cheaper but still sometimes there is a spike 

Assuming if the mempool is congested, the person can just click on the transaction to accelerate it like on Electrum, it is very simple. Even if the person do not know how to accelerate it, he can come to this forum and ask. Like on Electrum, the transaction support RBF by default and we can instruct the person to just pump the fee easily.

There is nothing expensive about using RBF, just check the mempool to know the best fee rate that you can use. If not in a hurry, you can wait for the mempool to become decongested and the transaction would later be included in a block.

Recently, 1 sat/vbyte transactions are not getting confirmed since many days ago, but 4 to 5 sat/vbyte are getting confirmed. If the person needs the money urgently today, he can just set the fee to 4 sat/vbyte, which is not expensive at all.

Just one example, you can enable it on Electrum if you wanted to have this capability in your open source wallet.


Yeah, basically that's it, so there's a lot of benefits to enable this features on a wallet. And I guess it should be the norm for every bitcoin user. Because just like in recent months, the fees has been tremendously high, it used to be a minimum 1 sat/vByte, but due to ordinals in which the mempool has been clogged those normal fees that we are used to are stuck and many are complaining how to accelerate or bump the fee.

If they only knew this features on most of the open source wallet, then they won't have any headaches. The cons is that you will have to used more than usual fees. And looking at the mempool now, 1 sat/vByte is no longer viable for a quick confirmation.

I don't know if the wallet you are using supports this feature or not, but it is really useful when transaction fees fluctuate fast. In many cases, RBF can save confirmation time, it also helps you when you expect a fast transaction. But somehow you may have ignored it.

But to minimize the possibility of getting stuck on your transaction, then try to get recommended fees on several sites, it can be on mempool.space or also on blockchair.

If you always do peer-to-peer transactions, I advise you to get used to using the feature. An example is that you buy bitcoin from someone you do not know and send you the transaction with a small fee after you pay it. Through the CPFP feature, you can resend the amount in a new transaction to another address of yours. This will cost more fees, but a more secure transaction because as long as the transaction is not confirmed by the network, the sender can recover the bitcoins through the double-spend feature.
The Bitcoin protocol provides useful features. All it takes is your seed words. Unfortunately, most users are not aware of this because closed source wallets and trading platforms do not provide these features on the wallets that they offer. I think they should not be called wallets at all.

Yeah, but just remember that it might be expensive on your end to do RBF, reason being, based on my experienced,

(1) somehow you have been waiting long enough (in my case 5 days), so I have to do that with a higher fee because I wanted to get it confirmed right away as I can't no longer way, hence I have to increased it more than the initial fee

(2) if you are not in a hurry, don't used it, just saying.

(3) check mempool first so that you will know how much fee you need to pay in order for your transaction not to be stuck

I have not done this Replace by fee (RBF) but a friend of mine did it and told me that it was good and it made the transaction very fast. Really not everyone knows how to accelerate their transactions. In my own understand of the whole stuff is when the person uses low transaction fee with many blocks to verify the process, then the delay of unconfirmed occurred. But if the person set high transaction fee rate, then the transaction would be faster. When the transaction is slow as it is said, the person can check the mempool to track the movement of the coins.
Op thanks you for the information.

Pumping the fee would have been a better solution for this: Someone can help me accelerate stuck transaction

Learn how to unstuck your bitcoin transaction by using the right wallet, not the wallets that do not support opt-in RBF. Check the OP to know the wallets that support opt-in RBF.

Some nodes are already starting to run it, but even if the majority don't, I suspect at some point in the future (perhaps even by v25.0, which is scheduled for May 2023) it will get switched to default true rather than default false, at which point it will rapidly spread throughout the network. Then it won't be a case of your wallet requiring to opt in to RBF - every transaction will be automatically opted in. The only stumbling block to using RBF at that point will be whether or not your wallet is good enough to support making such a transaction, but if it isn't you can always import your seed phrase in to a better wallet and do it from there, even if you had never even heard of RBF when you made the original transaction.

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


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.

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.

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.

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.

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


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

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?

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.

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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

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.


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/

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.

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.

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.

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

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
Bluewallet
Trezor Suite
Blockstream Green
Samourai
Sparrow wallet
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


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