Fee bumping - Revision history

Jhfrontz: added some links to terms

2019-01-14T23:28:17Z

added some links to terms

← Older revision		Revision as of 23:28, 14 January 2019
Line 1:		Line 1:
	The fee required for a transaction to quickly confirm varies according to network conditions. Generally it floats around slowly, but sometimes it shoots up due to spam transactions or a series of randomly-slow blocks. In such cases, you may find that your incoming or outgoing transactions get stuck in ~~0-conf status~~ for a long time. Wallets ''should'' avoid this in 99% of cases by accurately predicting an appropriate fee, and they ''should'' be able to gracefully bump fees in the remaining 1% of cases, but in general, fees are handled pretty poorly by today's wallets.		The [[transaction fee \| fee]] required for a [[transaction]] to quickly [[confirmation \| confirm]] varies according to network conditions. Generally it floats around slowly, but sometimes it shoots up due to [[spam transactions]] or a series of randomly-slow blocks. In such cases, you may find that your incoming or outgoing transactions get stuck in an unconfirmed state for a long time. [[wallet \| Wallets]] ''should'' avoid this in 99% of cases by accurately predicting an appropriate fee, and they ''should'' be able to gracefully bump fees in the remaining 1% of cases, but in general, fees are handled pretty poorly by today's wallets.

	This page gives exact instructions on how to increase the fee on a transaction that is currently stuck in order to make it unstuck. This is always done by creating a new transaction that will either spend the coins sent by the stuck transaction (called [[Transaction fees#Feerates_for_dependent_transactions_.28child-pays-for-parent.29\|child-pays-for-parent]], or CPFP) or replace the stuck transaction (called [[replace by fee\|replace-by-fee]], or RBF). The instructions vary significantly depending on your wallet software. Find your wallet in the table of contents, and then go to the section labeled "I sent the stuck transaction" or "I received the stuck transaction", as appropriate.		This page gives exact instructions on how to increase the fee on a transaction that is currently stuck in order to make it unstuck. This is always done by creating a new transaction that will either spend the coins sent by the stuck transaction (called [[Transaction fees#Feerates_for_dependent_transactions_.28child-pays-for-parent.29\|child-pays-for-parent]], or CPFP) or replace the stuck transaction (called [[replace by fee\|replace-by-fee]], or RBF). The instructions vary significantly depending on your wallet software. Find your wallet in the table of contents, and then go to the section labeled "I sent the stuck transaction" or "I received the stuck transaction", as appropriate.

Sgornick: Fix link for Child-pays-for-parent.

2018-03-06T00:04:09Z

Fix link for Child-pays-for-parent.

← Older revision		Revision as of 00:04, 6 March 2018
Line 1:		Line 1:
	The fee required for a transaction to quickly confirm varies according to network conditions. Generally it floats around slowly, but sometimes it shoots up due to spam transactions or a series of randomly-slow blocks. In such cases, you may find that your incoming or outgoing transactions get stuck in 0-conf status for a long time. Wallets ''should'' avoid this in 99% of cases by accurately predicting an appropriate fee, and they ''should'' be able to gracefully bump fees in the remaining 1% of cases, but in general, fees are handled pretty poorly by today's wallets.		The fee required for a transaction to quickly confirm varies according to network conditions. Generally it floats around slowly, but sometimes it shoots up due to spam transactions or a series of randomly-slow blocks. In such cases, you may find that your incoming or outgoing transactions get stuck in 0-conf status for a long time. Wallets ''should'' avoid this in 99% of cases by accurately predicting an appropriate fee, and they ''should'' be able to gracefully bump fees in the remaining 1% of cases, but in general, fees are handled pretty poorly by today's wallets.

	This page gives exact instructions on how to increase the fee on a transaction that is currently stuck in order to make it unstuck. This is always done by creating a new transaction that will either spend the coins sent by the stuck transaction (called [[~~https://en.bitcoin.it/wiki/Transaction_fees~~#Feerates_for_dependent_transactions_.28child-pays-for-parent.29\|child-pays-for-parent]], or CPFP) or replace the stuck transaction (called [[replace by fee\|replace-by-fee]], or RBF). The instructions vary significantly depending on your wallet software. Find your wallet in the table of contents, and then go to the section labeled "I sent the stuck transaction" or "I received the stuck transaction", as appropriate.		This page gives exact instructions on how to increase the fee on a transaction that is currently stuck in order to make it unstuck. This is always done by creating a new transaction that will either spend the coins sent by the stuck transaction (called [[Transaction fees#Feerates_for_dependent_transactions_.28child-pays-for-parent.29\|child-pays-for-parent]], or CPFP) or replace the stuck transaction (called [[replace by fee\|replace-by-fee]], or RBF). The instructions vary significantly depending on your wallet software. Find your wallet in the table of contents, and then go to the section labeled "I sent the stuck transaction" or "I received the stuck transaction", as appropriate.

	In some cases, the instructions here become kludgy. Any time you're working outside of the normal wallet GUI, you're doing something that the developer didn't intend, and this could have negative consequences. Although we have tried to give good instructions, we can't guarantee that everything will work perfectly. If your wallet GUI doesn't directly support fee bumping, then the lowest-risk thing for you to do is to not bump the fee, and to just wait. This page is for those situations where you ''can't'' just wait.		In some cases, the instructions here become kludgy. Any time you're working outside of the normal wallet GUI, you're doing something that the developer didn't intend, and this could have negative consequences. Although we have tried to give good instructions, we can't guarantee that everything will work perfectly. If your wallet GUI doesn't directly support fee bumping, then the lowest-risk thing for you to do is to not bump the fee, and to just wait. This page is for those situations where you ''can't'' just wait.

Sgornick: Add link to Child-pays-for-parent subsection of Transaction fees article on first use of that term in this article.

2018-03-06T00:01:25Z

Add link to Child-pays-for-parent subsection of Transaction fees article on first use of that term in this article.

← Older revision		Revision as of 00:01, 6 March 2018
Line 1:		Line 1:
	The fee required for a transaction to quickly confirm varies according to network conditions. Generally it floats around slowly, but sometimes it shoots up due to spam transactions or a series of randomly-slow blocks. In such cases, you may find that your incoming or outgoing transactions get stuck in 0-conf status for a long time. Wallets ''should'' avoid this in 99% of cases by accurately predicting an appropriate fee, and they ''should'' be able to gracefully bump fees in the remaining 1% of cases, but in general, fees are handled pretty poorly by today's wallets.		The fee required for a transaction to quickly confirm varies according to network conditions. Generally it floats around slowly, but sometimes it shoots up due to spam transactions or a series of randomly-slow blocks. In such cases, you may find that your incoming or outgoing transactions get stuck in 0-conf status for a long time. Wallets ''should'' avoid this in 99% of cases by accurately predicting an appropriate fee, and they ''should'' be able to gracefully bump fees in the remaining 1% of cases, but in general, fees are handled pretty poorly by today's wallets.

	This page gives exact instructions on how to increase the fee on a transaction that is currently stuck in order to make it unstuck. This is always done by creating a new transaction that will either spend the coins sent by the stuck transaction (called CPFP) or replace the stuck transaction (called [[replace by fee\|replace-by-fee]] or RBF). The instructions vary significantly depending on your wallet software. Find your wallet in the table of contents, and then go to the section labeled "I sent the stuck transaction" or "I received the stuck transaction", as appropriate.		This page gives exact instructions on how to increase the fee on a transaction that is currently stuck in order to make it unstuck. This is always done by creating a new transaction that will either spend the coins sent by the stuck transaction (called [[https://en.bitcoin.it/wiki/Transaction_fees#Feerates_for_dependent_transactions_.28child-pays-for-parent.29\|child-pays-for-parent]], or CPFP) or replace the stuck transaction (called [[replace by fee\|replace-by-fee]], or RBF). The instructions vary significantly depending on your wallet software. Find your wallet in the table of contents, and then go to the section labeled "I sent the stuck transaction" or "I received the stuck transaction", as appropriate.

	In some cases, the instructions here become kludgy. Any time you're working outside of the normal wallet GUI, you're doing something that the developer didn't intend, and this could have negative consequences. Although we have tried to give good instructions, we can't guarantee that everything will work perfectly. If your wallet GUI doesn't directly support fee bumping, then the lowest-risk thing for you to do is to not bump the fee, and to just wait. This page is for those situations where you ''can't'' just wait.		In some cases, the instructions here become kludgy. Any time you're working outside of the normal wallet GUI, you're doing something that the developer didn't intend, and this could have negative consequences. Although we have tried to give good instructions, we can't guarantee that everything will work perfectly. If your wallet GUI doesn't directly support fee bumping, then the lowest-risk thing for you to do is to not bump the fee, and to just wait. This page is for those situations where you ''can't'' just wait.

Sgornick: Add link to Replace by fee article on first use of that term.

2018-03-05T23:57:28Z

Add link to Replace by fee article on first use of that term.

← Older revision		Revision as of 23:57, 5 March 2018
Line 1:		Line 1:
	The fee required for a transaction to quickly confirm varies according to network conditions. Generally it floats around slowly, but sometimes it shoots up due to spam transactions or a series of randomly-slow blocks. In such cases, you may find that your incoming or outgoing transactions get stuck in 0-conf status for a long time. Wallets ''should'' avoid this in 99% of cases by accurately predicting an appropriate fee, and they ''should'' be able to gracefully bump fees in the remaining 1% of cases, but in general, fees are handled pretty poorly by today's wallets.		The fee required for a transaction to quickly confirm varies according to network conditions. Generally it floats around slowly, but sometimes it shoots up due to spam transactions or a series of randomly-slow blocks. In such cases, you may find that your incoming or outgoing transactions get stuck in 0-conf status for a long time. Wallets ''should'' avoid this in 99% of cases by accurately predicting an appropriate fee, and they ''should'' be able to gracefully bump fees in the remaining 1% of cases, but in general, fees are handled pretty poorly by today's wallets.

	This page gives exact instructions on how to increase the fee on a transaction that is currently stuck in order to make it unstuck. This is always done by creating a new transaction that will either spend the coins sent by the stuck transaction (called CPFP) or replace the stuck transaction (called RBF). The instructions vary significantly depending on your wallet software. Find your wallet in the table of contents, and then go to the section labeled "I sent the stuck transaction" or "I received the stuck transaction", as appropriate.		This page gives exact instructions on how to increase the fee on a transaction that is currently stuck in order to make it unstuck. This is always done by creating a new transaction that will either spend the coins sent by the stuck transaction (called CPFP) or replace the stuck transaction (called [[replace by fee\|replace-by-fee]] or RBF). The instructions vary significantly depending on your wallet software. Find your wallet in the table of contents, and then go to the section labeled "I sent the stuck transaction" or "I received the stuck transaction", as appropriate.

	In some cases, the instructions here become kludgy. Any time you're working outside of the normal wallet GUI, you're doing something that the developer didn't intend, and this could have negative consequences. Although we have tried to give good instructions, we can't guarantee that everything will work perfectly. If your wallet GUI doesn't directly support fee bumping, then the lowest-risk thing for you to do is to not bump the fee, and to just wait. This page is for those situations where you ''can't'' just wait.		In some cases, the instructions here become kludgy. Any time you're working outside of the normal wallet GUI, you're doing something that the developer didn't intend, and this could have negative consequences. Although we have tried to give good instructions, we can't guarantee that everything will work perfectly. If your wallet GUI doesn't directly support fee bumping, then the lowest-risk thing for you to do is to not bump the fee, and to just wait. This page is for those situations where you ''can't'' just wait.

Belcher: /* I sent the stuck transaction */ added a step on the suggestion of the user Content from IRC

2017-12-20T22:49:16Z

I sent the stuck transaction: added a step on the suggestion of the user Content from IRC

← Older revision		Revision as of 22:49, 20 December 2017
Line 45:		Line 45:
	# You need to temporarily break connectivity. Go to Settings -> Options -> Network Tab. Enable "Connect through SOCKS5 proxy (default proxy)". Change "Proxy IP" and "port" to something that won't actually work; for example, an IP of 127.0.0.1 and a port of 10 is very unlikely to work. If you already have a proxy set up, note down your current settings so that you can restore them later.		# You need to temporarily break connectivity. Go to Settings -> Options -> Network Tab. Enable "Connect through SOCKS5 proxy (default proxy)". Change "Proxy IP" and "port" to something that won't actually work; for example, an IP of 127.0.0.1 and a port of 10 is very unlikely to work. If you already have a proxy set up, note down your current settings so that you can restore them later.
	# Shut down Bitcoin Core.		# Shut down Bitcoin Core.
			# Go to your [[Data directory]] and delete the file <tt>mempool.dat</tt>. This stops it acting as a cache and reloading your transaction.
	# Start Bitcoin Core with the command-line option <tt>-walletbroadcast=0</tt>. On Linux, you might be able to just run <tt>bitcoin-qt -walletbroadcast=0</tt>, depending on how your current startup script works. On Windows: find the shortcut for Bitcoin Core on your desktop or start menu; right click it and choose "properties"; add <tt>-walletbroadcast=0</tt> to the end of "target", so for example <tt>"C:\Program Files\Bitcoin\bitcoin-qt.exe"</tt> would become <tt>"C:\Program Files\Bitcoin\bitcoin-qt.exe" -walletbroadcast=0</tt>; click "Apply"; use that specific shortcut to start Bitcoin Core.		# Start Bitcoin Core with the command-line option <tt>-walletbroadcast=0</tt>. On Linux, you might be able to just run <tt>bitcoin-qt -walletbroadcast=0</tt>, depending on how your current startup script works. On Windows: find the shortcut for Bitcoin Core on your desktop or start menu; right click it and choose "properties"; add <tt>-walletbroadcast=0</tt> to the end of "target", so for example <tt>"C:\Program Files\Bitcoin\bitcoin-qt.exe"</tt> would become <tt>"C:\Program Files\Bitcoin\bitcoin-qt.exe" -walletbroadcast=0</tt>; click "Apply"; use that specific shortcut to start Bitcoin Core.
	# On the Transactions tab, right click the stuck transaction and choose "abandon transaction". '''Warning''': Even though the transaction is listed as abandoned, ''it can still go through''. People have in the past lost money by abandoning a transaction, resending a separate replacement transaction, and then having ''both'' transactions go through. The following steps are designed to replace the abandoned transaction in a way which will prevent this sort of double payment from happening.		# On the Transactions tab, right click the stuck transaction and choose "abandon transaction". '''Warning''': Even though the transaction is listed as abandoned, ''it can still go through''. People have in the past lost money by abandoning a transaction, resending a separate replacement transaction, and then having ''both'' transactions go through. The following steps are designed to replace the abandoned transaction in a way which will prevent this sort of double payment from happening.

Theymos: /* Choosing an appropriate new fee */

2017-06-07T17:04:41Z

Choosing an appropriate new fee

← Older revision		Revision as of 17:04, 7 June 2017
Line 17:		Line 17:
	# If any of ''those'' transactions also have red 'U's, you have to follow those as well and add their sizes and fees to the running totals. And so on. You might have to go down several layers.		# If any of ''those'' transactions also have red 'U's, you have to follow those as well and add their sizes and fees to the running totals. And so on. You might have to go down several layers.
	# Now TOTAL_SIZE is the the total size (in bytes) of all unconfirmed ancestors of your stuck transaction, and TOTAL_FEES is the total fees (in BTC) for all unconfirmed ancestors of your stuck transaction.		# Now TOTAL_SIZE is the the total size (in bytes) of all unconfirmed ancestors of your stuck transaction, and TOTAL_FEES is the total fees (in BTC) for all unconfirmed ancestors of your stuck transaction.
	# Go to https://estimatefee.com/. Around the middle-right of the page it'll say ~~something~~ "nnn satoshis/byte", where nnn is some number. Remember this number as TARGET_FEERATE.		# Go to https://estimatefee.com/. Around the middle-right of the page it'll say "nnn satoshis/byte", where nnn is some number. Remember this number as TARGET_FEERATE.
	# We need to estimate the additional size of your replacement or CPFP transaction. We'll call this value NEWTX_SIZE. If the transaction you're trying to unstick is one that you sent, estimate NEWTX_SIZE as 100. If the transaction you're trying to unstick is one that you received, estimate NEWTX_SIZE as 500. Later on this page, the section for your specific wallet might give you a different value for NEWTX_SIZE, in which case you should use that value instead.		# We need to estimate the additional size of your replacement or CPFP transaction. We'll call this value NEWTX_SIZE. If the transaction you're trying to unstick is one that you sent, estimate NEWTX_SIZE as 100. If the transaction you're trying to unstick is one that you received, estimate NEWTX_SIZE as 500. Later on this page, the section for your specific wallet might give you a different value for NEWTX_SIZE, in which case you should use that value instead.
	# Compute the following: [(TARGET_FEERATE / 100000000) * (TOTAL_SIZE + NEWTX_SIZE)] - TOTAL_FEES. The result is an estimate of the '''total''' fee that your new transaction will need to pay in BTC. For mBTC, multiply by 10<sup>-3</sup>; for bits/uBTC, 10<sup>-6</sup>; for satoshi, 10<sup>-8</sup>. This number is '''not''' per kB. If your wallet only allows you to specify fees in BTC/bits/satoshi per kB/byte, multiply the result by one of the following estimated conversion factors (we conservatively assume the worst-case 192-byte transaction for this estimation):		# Compute the following: [(TARGET_FEERATE / 100000000) * (TOTAL_SIZE + NEWTX_SIZE)] - TOTAL_FEES. The result is an estimate of the '''total''' fee that your new transaction will need to pay in BTC. For mBTC, multiply by 10<sup>-3</sup>; for bits/uBTC, 10<sup>-6</sup>; for satoshi, 10<sup>-8</sup>. This number is '''not''' per kB. If your wallet only allows you to specify fees in BTC/bits/satoshi per kB/byte, multiply the result by one of the following estimated conversion factors (we conservatively assume the worst-case 192-byte transaction for this estimation):

Theymos: replace bitcoinfees.21.co with estimatefee.com

2017-06-07T17:04:18Z

replace bitcoinfees.21.co with estimatefee.com

← Older revision		Revision as of 17:04, 7 June 2017
Line 17:		Line 17:
	# If any of ''those'' transactions also have red 'U's, you have to follow those as well and add their sizes and fees to the running totals. And so on. You might have to go down several layers.		# If any of ''those'' transactions also have red 'U's, you have to follow those as well and add their sizes and fees to the running totals. And so on. You might have to go down several layers.
	# Now TOTAL_SIZE is the the total size (in bytes) of all unconfirmed ancestors of your stuck transaction, and TOTAL_FEES is the total fees (in BTC) for all unconfirmed ancestors of your stuck transaction.		# Now TOTAL_SIZE is the the total size (in bytes) of all unconfirmed ancestors of your stuck transaction, and TOTAL_FEES is the total fees (in BTC) for all unconfirmed ancestors of your stuck transaction.
	# Go to ~~http~~://~~bitcoinfees~~.~~21.co~~/ . ~~Ensure that it says "Satoshis" in~~ the ~~upper~~-~~left dropdown under~~ "~~Fees~~"~~. In the big table with colored bars~~, ~~find the first row that~~ is ~~green. On the left, there will be a range of numbers, for example "101-110". Take the high~~ number ~~in this range~~. ~~We'll call~~ this TARGET_FEERATE.		# Go to https://estimatefee.com/. Around the middle-right of the page it'll say something "nnn satoshis/byte", where nnn is some number. Remember this number as TARGET_FEERATE.
	# We need to estimate the additional size of your replacement or CPFP transaction. We'll call this value NEWTX_SIZE. If the transaction you're trying to unstick is one that you sent, estimate NEWTX_SIZE as 100. If the transaction you're trying to unstick is one that you received, estimate NEWTX_SIZE as 500. Later on this page, the section for your specific wallet might give you a different value for NEWTX_SIZE, in which case you should use that value instead.		# We need to estimate the additional size of your replacement or CPFP transaction. We'll call this value NEWTX_SIZE. If the transaction you're trying to unstick is one that you sent, estimate NEWTX_SIZE as 100. If the transaction you're trying to unstick is one that you received, estimate NEWTX_SIZE as 500. Later on this page, the section for your specific wallet might give you a different value for NEWTX_SIZE, in which case you should use that value instead.
	# Compute the following: [(TARGET_FEERATE / 100000000) * (TOTAL_SIZE + NEWTX_SIZE)] - TOTAL_FEES. The result is an estimate of the '''total''' fee that your new transaction will need to pay in BTC. For mBTC, multiply by 10<sup>-3</sup>; for bits/uBTC, 10<sup>-6</sup>; for satoshi, 10<sup>-8</sup>. This number is '''not''' per kB. If your wallet only allows you to specify fees in BTC/bits/satoshi per kB/byte, multiply the result by one of the following estimated conversion factors (we conservatively assume the worst-case 192-byte transaction for this estimation):		# Compute the following: [(TARGET_FEERATE / 100000000) * (TOTAL_SIZE + NEWTX_SIZE)] - TOTAL_FEES. The result is an estimate of the '''total''' fee that your new transaction will need to pay in BTC. For mBTC, multiply by 10<sup>-3</sup>; for bits/uBTC, 10<sup>-6</sup>; for satoshi, 10<sup>-8</sup>. This number is '''not''' per kB. If your wallet only allows you to specify fees in BTC/bits/satoshi per kB/byte, multiply the result by one of the following estimated conversion factors (we conservatively assume the worst-case 192-byte transaction for this estimation):

Theymos: Add guides category

2017-02-12T21:08:59Z

Add guides category

← Older revision		Revision as of 21:08, 12 February 2017
Line 109:		Line 109:

	Note that sending your entire balance like this totally destroys your privacy by linking together all of the coins in your wallet.		Note that sending your entire balance like this totally destroys your privacy by linking together all of the coins in your wallet.

			[[Category:Guides]]

Theymos: /* I received the stuck transaction */

2017-02-02T01:44:30Z

I received the stuck transaction

← Older revision		Revision as of 01:44, 2 February 2017
Line 108:		Line 108:
	Send slightly more than the ''confirmed'' balance of your entire wallet to yourself. For example, if you have a 2 BTC confirmed balance and a stuck transaction causing an unconfirmed balance of 0.5 BTC, send 2.01 BTC to yourself. This forces the usage of some of your unconfirmed balance, which is what you want. (Some wallets might not allow this, in which case nothing can be done without switching wallets.) Send this transaction with a very high fee.		Send slightly more than the ''confirmed'' balance of your entire wallet to yourself. For example, if you have a 2 BTC confirmed balance and a stuck transaction causing an unconfirmed balance of 0.5 BTC, send 2.01 BTC to yourself. This forces the usage of some of your unconfirmed balance, which is what you want. (Some wallets might not allow this, in which case nothing can be done without switching wallets.) Send this transaction with a very high fee.

	Note that this totally destroys your privacy by linking together all of the coins in your wallet.		Note that sending your entire balance like this totally destroys your privacy by linking together all of the coins in your wallet.

Theymos: /* Other wallets */ Note about "wallets" that are actually banks

2017-02-02T01:43:52Z

Other wallets: Note about "wallets" that are actually banks

← Older revision		Revision as of 01:43, 2 February 2017
Line 101:		Line 101:

	==== I received the stuck transaction ====		==== I received the stuck transaction ====

			If you're using a "wallet" that is actually a Bitcoin bank (eg. Coinbase, Gemini, etc.), then there's no way to do it.

			For real Bitcoin wallets:

	Send slightly more than the ''confirmed'' balance of your entire wallet to yourself. For example, if you have a 2 BTC confirmed balance and a stuck transaction causing an unconfirmed balance of 0.5 BTC, send 2.01 BTC to yourself. This forces the usage of some of your unconfirmed balance, which is what you want. (Some wallets might not allow this, in which case nothing can be done without switching wallets.) Send this transaction with a very high fee.		Send slightly more than the ''confirmed'' balance of your entire wallet to yourself. For example, if you have a 2 BTC confirmed balance and a stuck transaction causing an unconfirmed balance of 0.5 BTC, send 2.01 BTC to yourself. This forces the usage of some of your unconfirmed balance, which is what you want. (Some wallets might not allow this, in which case nothing can be done without switching wallets.) Send this transaction with a very high fee.

	Note that this totally destroys your privacy by linking together all of the coins in your wallet.		Note that this totally destroys your privacy by linking together all of the coins in your wallet.