Transaction replacement - Revision history

Thoragh: Bitcoin core 28.0 changed the default rbf behavior

2025-01-11T16:06:31Z

Bitcoin core 28.0 changed the default rbf behavior

← Older revision		Revision as of 16:06, 11 January 2025
Line 98:		Line 98:
	\| Bitcoin Core 0.19.0 - 23.x \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}}		\| Bitcoin Core 0.19.0 - 23.x \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}}
	\|-		\|-
	\| '''Bitcoin Core 24.0 & later''' \|\| {{No}} \|\| {{No}} \|\| {{~~Yes~~}} \|\| {{No}} \|\| {{No}} \|\| {{~~Prefer\|\|Default~~}}		\| Bitcoin Core 24.0 - 27.x \|\| {{No}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}
			\|-
			\| '''Bitcoin Core 28.0 & later''' \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}} \|\| {{No}} \|\| {{No}} \|\| {{Yes}}
	\|}		\|}

Luke-jr: /* Software support for replacement policies */ Bold current versions

2022-11-24T08:43:59Z

Software support for replacement policies: Bold current versions

← Older revision		Revision as of 08:43, 24 November 2022
Line 88:		Line 88:
	\| Satoshi RBF 0.11.0 \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}}		\| Satoshi RBF 0.11.0 \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}}
	\|-		\|-
	\| Satoshi RBF 0.11.1 & later \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}}		\| '''Satoshi RBF 0.11.1 & later''' \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}}
	\|-		\|-
	\| Bitcoin Core 0.12.0 - 0.18.x \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}		\| Bitcoin Core 0.12.0 - 0.18.x \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}
Line 94:		Line 94:
	\| Bitcoin Knots 0.12.0 - 0.15.1 \|\| {{Yes}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}		\| Bitcoin Knots 0.12.0 - 0.15.1 \|\| {{Yes}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}
	\|-		\|-
	\| Bitcoin Knots 0.16.0 & later \|\| {{Yes}} \|\| {{No}} \|\| {{Prefer\|\|Default}} \|\| {{No}} \|\| {{No}} \|\| {{Yes}}		\| '''Bitcoin Knots 0.16.0 & later''' \|\| {{Yes}} \|\| {{No}} \|\| {{Prefer\|\|Default}} \|\| {{No}} \|\| {{No}} \|\| {{Yes}}
	\|-		\|-
	\| Bitcoin Core 0.19.0 - 23.x \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}}		\| Bitcoin Core 0.19.0 - 23.x \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}}
	\|-		\|-
	\| Bitcoin Core 24.0 & later \|\| {{No}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}		\| '''Bitcoin Core 24.0 & later''' \|\| {{No}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}
	\|}		\|}

Luke-jr: /* Software support for replacement policies */

2022-11-24T08:42:25Z

Software support for replacement policies

← Older revision		Revision as of 08:42, 24 November 2022
Line 94:		Line 94:
	\| Bitcoin Knots 0.12.0 - 0.15.1 \|\| {{Yes}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}		\| Bitcoin Knots 0.12.0 - 0.15.1 \|\| {{Yes}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}
	\|-		\|-
	\| Bitcoin Knots 0.16.0 & ~~latter~~ \|\| {{Yes}} \|\| {{No}} \|\| {{Prefer\|\|Default}} \|\| {{No}} \|\| {{No}} \|\| {{Yes}}		\| Bitcoin Knots 0.16.0 & later \|\| {{Yes}} \|\| {{No}} \|\| {{Prefer\|\|Default}} \|\| {{No}} \|\| {{No}} \|\| {{Yes}}
	\|-		\|-
	\| Bitcoin Core 0.19.0 - 23.x \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}}		\| Bitcoin Core 0.19.0 - 23.x \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}}

Luke-jr: /* Software support for replacement policies */

2022-11-24T01:50:32Z

Software support for replacement policies

← Older revision		Revision as of 01:50, 24 November 2022
Line 78:		Line 78:
	\| Bitcoin 0.1 - 0.3.11 \|\| {{No}} \|\| {{Prefer\|\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}}		\| Bitcoin 0.1 - 0.3.11 \|\| {{No}} \|\| {{Prefer\|\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}}
	\|-		\|-
	\| Bitcoin 0.3.12 & later \|\| {{Prefer\|Exclusive}} \|\| {{No\|Disabled (DoS risk)}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}}		\| Bitcoin 0.3.12 & later \|\| {{Prefer\|\|Exclusive}} \|\| {{No\|Disabled (DoS risk)}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}}
	\|-		\|-
	\| Bitcoin Core 0.3.20 - 0.11.x \|\| {{Prefer\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}}		\| Bitcoin Core 0.3.20 - 0.11.x \|\| {{Prefer\|\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}}
	\|-		\|-
	\| Bitcoin Knots 0.3.21 - 0.11.x \|\| {{Prefer\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}}		\| Bitcoin Knots 0.3.21 - 0.11.x \|\| {{Prefer\|\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}}
	\|-		\|-
	\| Satoshi RBF 0.8.6 - 0.10.x \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}}		\| Satoshi RBF 0.8.6 - 0.10.x \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}}
	\|-		\|-
	\| Satoshi RBF 0.11.0 \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|Default}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}}		\| Satoshi RBF 0.11.0 \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}}
	\|-		\|-
	\| Satoshi RBF 0.11.1 & later \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}}		\| Satoshi RBF 0.11.1 & later \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}} \|\| {{No}} \|\| {{No}} \|\| {{No}}
	\|-		\|-
	\| Bitcoin Core 0.12.0 - 0.18.x \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|Default}}		\| Bitcoin Core 0.12.0 - 0.18.x \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}
	\|-		\|-
	\| Bitcoin Knots 0.12.0 - 0.15.1 \|\| {{Yes}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|Default}}		\| Bitcoin Knots 0.12.0 - 0.15.1 \|\| {{Yes}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}
	\|-		\|-
	\| Bitcoin Knots 0.16.0 & latter \|\| {{Yes}} \|\| {{No}} \|\| {{Prefer\|Default}} \|\| {{No}} \|\| {{No}} \|\| {{Yes}}		\| Bitcoin Knots 0.16.0 & latter \|\| {{Yes}} \|\| {{No}} \|\| {{Prefer\|\|Default}} \|\| {{No}} \|\| {{No}} \|\| {{Yes}}
	\|-		\|-
	\| Bitcoin Core 0.19.0 - 23.x \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|Exclusive}}		\| Bitcoin Core 0.19.0 - 23.x \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Exclusive}}
	\|-		\|-
	\| Bitcoin Core 24.0 & later \|\| {{No}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|Default}}		\| Bitcoin Core 24.0 & later \|\| {{No}} \|\| {{No}} \|\| {{Yes}} \|\| {{No}} \|\| {{No}} \|\| {{Prefer\|\|Default}}
	\|}		\|}

Luke-jr: Rework page

2022-11-24T01:37:43Z

Rework page

Show changes

Luke-jr: Update & clarifications

2022-11-24T00:31:22Z

Update & clarifications

← Older revision		Revision as of 00:31, 24 November 2022
Line 1:		Line 1:
	'''Transaction ~~replaceability~~''' occurs when a ~~full~~ node ~~allows one or~~		'''Transaction replacement''' occurs when a transaction seen by a node is conflicted with and ultimately replaced by another transaction.
	~~more of~~ the transactions ~~in its memory pool~~ (~~mempool~~) to be replaced		Typically, the replaced transaction had been unconfirmed, though it can happen sometimes in a [[blockchain reorganisation]] that a transaction with a few blocks confirmation can also be replaced.
	~~with~~ a ~~different transaction that spends some or all~~ of ~~the same inputs~~.		Transactions in the canonical blockchain must always replace conflicting transactions (a blockchain with two conflicting transactions is invalid).
	~~Transaction replaceability was enabled~~ in the first version of
			Unconfirmed transactions that do not conflict with the blockchain can, however, be replaced by other unconfirmed transactions at the whim of nodes, determined by the node operator's own policies.
			Hypothetically, a node could also keep track of and relay multiple conflicting transactions, though this is not typically done due to DoS risks.

			Unconfirmed transaction replacement has been included in the first version of
	Bitcoin<ref>[https://github.com/trottier/original-bitcoin/blob/master/src/main.cpp#L434 Replacement in original Bitcoin source code], Satoshi Nakamoto, GitHub, ''Retrieved 2015-12-08''</ref> but was disabled in the 0.3.12 release with the comment,		Bitcoin<ref>[https://github.com/trottier/original-bitcoin/blob/master/src/main.cpp#L434 Replacement in original Bitcoin source code], Satoshi Nakamoto, GitHub, ''Retrieved 2015-12-08''</ref> but was disabled in the 0.3.12 release with the comment,
	"Disable replacement feature for now".<ref>[https://github.com/bitcoin/bitcoin/commit/05454818dc7ed92f577a1a1ef6798049f17a52e7#diff-118fcbaaba162ba17933c7893247df3aR522 Commit disabling replacement "for now"], Satoshi Nakamoto, GitHub, ''Retrieved 2015-12-08''</ref> Since then, there have been various attempts to make		"Disable replacement feature for now".<ref>[https://github.com/bitcoin/bitcoin/commit/05454818dc7ed92f577a1a1ef6798049f17a52e7#diff-118fcbaaba162ba17933c7893247df3aR522 Commit disabling replacement "for now"], Satoshi Nakamoto, GitHub, ''Retrieved 2015-12-08''</ref> Since then, there have been various attempts to make
Line 14:		Line 18:
	== Node policies ==		== Node policies ==

	~~Transaction~~ replacement is optional (it is not, and cannot be,		Unconfirmed transaction replacement is optional (it is not, and cannot be,
	a consensus rule), but widespread adherence to the same basic policy		a consensus rule), but widespread adherence to the same basic policy
	among nodes can help predict a popular network-wide mempool policy		among nodes can help predict a popular network-wide mempool policy
Line 25:		Line 29:
	* Consistent mempools may help nodes more quickly validate newly-received blocks as well as reduce the bandwidth used to announce new blocks in the future.		* Consistent mempools may help nodes more quickly validate newly-received blocks as well as reduce the bandwidth used to announce new blocks in the future.

	=== Bitcoin Core 0.3.12 to 0.11.x ===		=== Bitcoin 0.1 to 0.3.11===

			Unconfirmed transactions can be replaced at-will by the sender, regardless of fee increase or reduction, or output destinations.

			=== Bitcoin 0.3.12 to 0.3.19===

			Transaction replacability is accepted only in mined blocks, after which the replaced transaction can only be restored by a subsequent [[blockchain reorganisation]] containing a conflicting transaction (a reorganisation not conflicting will not rereplace the previously-mined replacement).

			=== Bitcoin Core & Knots 0.3.20 to 0.11.x ===

			Initially, Bitcoin Core did not modify, and continued the replacement policy of Bitcoin 0.3.19.

	~~Transaction replacability is disallowed in a running node.~~		=== Peter Todd's full-RBF patchset ===

	=== Bitcoin Core 0.12.0 to 0.16.0 ===		Peter Todd has historically maintained patchsets against Bitcoin Core
			0.8.x and later that implement full-RBF for all transactions in the
			mempool.
			Some older versions also provide an option to enable RBF First-Seen-Safe (RBF-FSS) only.

			Notably, the patchset also implements preferential peering that allows
			nodes implementing full-RBF to connect to each other so that replacements
			can circulate even if full-RBF nodes represent a small minority of the
			network.

			=== Bitcoin Core 0.12.0 to 0.18.x ===

	''Bitcoin Core 0.12.0 was released in Feb 2016.''		''Bitcoin Core 0.12.0 was released in Feb 2016.''

	Bitcoin Core 0.12.0 and ~~later use~~ the initial implementation of opt-in ~~full-~~RBF		Bitcoin Core 0.12.0 until 0.18.x included and used by default the initial implementation of opt-in RBF
	described in [https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki BIP 125].		similar to (but not identical with) that described in [https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki BIP 125].
			Users could turn off the feature, reverting to the old replacement-averse policy.

	The initial implementation of opt-in full-RBF may be seen in		The initial implementation of opt-in full-RBF may be seen in
Line 42:		Line 67:
	16a2f93629f75d182871f288f0396afe6cdc8504 (inclusive).		16a2f93629f75d182871f288f0396afe6cdc8504 (inclusive).

	=== Bitcoin Knots ===		=== Bitcoin Knots 0.12.0 to 0.15.1 ===

	Bitcoin Knots ~~allows~~ the ~~user to easily configure its~~ replacement ~~policy.~~		Bitcoin Knots 0.12.0 until 0.15.1 supported the same replacement-adverse and opt-in RBF policies as Bitcoin Core, but additionally offered the option for users to choose unconditional RBF, ignoring any policy preferences expressed using BIP 125.
	~~Opt~~-in RBF, ~~full~~ RBF, ~~and strict first-seen policies are supported~~.

	=== ~~Peter Todd's full-RBF patchset~~ ===		=== Bitcoin Knots 0.16.0 and later ===

	~~Peter Todd has historically maintained patchsets against Bitcoin Core~~		In 0.16.0, the default policy of Bitcoin Knots was changed to unconditional RBF, while support for both opt-in RBF and replacement-adverse policies have been maintained for users to choose at will.
	0.8.~~x and later that implement full-RBF for all transactions in~~ the
	~~mempool. (Later versions also provide an option~~ to ~~enable~~ RBF ~~First~~-~~Seen-Safe (~~RBF-~~FSS) only~~.)

	~~Notably, the patchset also implements preferential peering that allows~~		=== Bitcoin Core 0.19.0 to 23.x ===
	~~nodes implementing full-RBF to connect~~ to ~~each other so that replacements~~
	~~can circulate even if full-RBF nodes represent a small minority of the~~
	~~network~~.

	* [https://github.~~com/petertodd/bitcoin/branches/all?utf8=%E2%9C%93&query=replace-by-fee-v0~~.~~10 Replace by fee patches for~~ Bitcoin Core ~~0.10.x]~~		Beginning with 0.19.0, Bitcoin Core removed the option to revert to the replacement-averse policy, only supporting opt-in RBF.
	* [https://github.com/petertodd/bitcoin/branches/all?utf8=%E2%9C%93&query=replace-by-~~fee~~-~~v0.11 Replace by fee patches for Bitcoin Core 0.11~~.x]

	~~Policy<ref>[https://github~~.~~com/bitcoin/bitcoin/compare/~~0~~.11...petertodd:replace-by-fee-v0.11.0 RBF patchset for 0.11.2], Peter Todd, GitHub, ''Retrieved 2015-12-08''</ref>: one or more transactions currently in the mempool (original~~		=== Bitcoin Core 24.0 and later ===
	~~transactions) will be replaced by a new transaction (replacement~~
	~~transaction) that spends one or more of the same inputs if,~~

	~~# The replacement transaction pays an absolute higher fee than~~ the ~~original transactions.~~		Bitcoin Core 24.0 added the option to choose the unconditional RBF policy, though the default remains to apply only opt-in RBF.
	~~# The replacement transaction must pay for its own bandwidth in addition~~ to the amount paid by the original transactions at least by the rate set by the node's minimum relay fee setting. For example, if the minimum relay fee is 1 satoshi/byte and the replacement transaction is 500 bytes total, ~~then~~ the ~~replacement must pay a fee at least 500 satoshis higher than the originals~~.
	~~# No more than 100 original transactions are replaced by the replacement transaction~~

	== See Also ==		== See Also ==

Luke-jr: Updates

2018-03-06T01:02:40Z

Updates

← Older revision		Revision as of 01:02, 6 March 2018
Line 7:		Line 7:
	transaction replaceability widely available again.<ref>[https://bitcointalk.org/index.php?topic=199947.0 Initial replace-by-fee implementation available for testnet], BitcoinTalk forum, posted 2013-05-09, ''retrieved 2015-12-09''</ref>		transaction replaceability widely available again.<ref>[https://bitcointalk.org/index.php?topic=199947.0 Initial replace-by-fee implementation available for testnet], BitcoinTalk forum, posted 2013-05-09, ''retrieved 2015-12-09''</ref>

	Beginning with Bitcoin Core 0.12.0 (~~eta~~ Feb 1 2016), ~~it is expected~~		Beginning with Bitcoin Core 0.12.0 (released Feb 2016), one type of transaction replaceability, [[Replace by fee\|replace-by-fee]] (RBF), became widely available.
	~~that~~ one type of transaction replaceability, [[Replace by fee\|replace-by-fee]] (RBF), ~~will become~~ widely available. This page		This page
	attempts to document the current state of transaction replaceability for		attempts to document the current state of transaction replaceability for
	wallet authors who want to use that feature.		wallet authors who want to use that feature.
Line 16:		Line 16:
	Transaction replacement is optional (it is not, and cannot be,		Transaction replacement is optional (it is not, and cannot be,
	a consensus rule), but widespread adherence to the same basic policy		a consensus rule), but widespread adherence to the same basic policy
	among nodes ~~will~~ help ~~maintain~~ a ~~consistent~~ network-wide mempool policy		among nodes can help predict a popular network-wide mempool policy
	with the following expected benefits:		with the following expected benefits:

Line 27:		Line 27:
	=== Bitcoin Core 0.3.12 to 0.11.x ===		=== Bitcoin Core 0.3.12 to 0.11.x ===

	Transaction ~~replaceability~~ is disallowed in a running node.		Transaction replacability is disallowed in a running node.

	=== Bitcoin Core 0.12.0 ===		=== Bitcoin Core 0.12.0 to 0.16.0 ===

	''Bitcoin Core 0.12.0 ~~has been~~ released in Feb 2016.''		''Bitcoin Core 0.12.0 was released in Feb 2016.''

	Bitcoin Core 0.12.0 ~~uses~~ the initial implementation of opt-in full-RBF		Bitcoin Core 0.12.0 and later use the initial implementation of opt-in full-RBF
	described in [https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki BIP 125].		described in [https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki BIP 125].

Line 41:		Line 41:
	5891f870d68d90408aa5ce5b597fb574f2d2cbca to		5891f870d68d90408aa5ce5b597fb574f2d2cbca to
	16a2f93629f75d182871f288f0396afe6cdc8504 (inclusive).		16a2f93629f75d182871f288f0396afe6cdc8504 (inclusive).

			=== Bitcoin Knots ===

			Bitcoin Knots allows the user to easily configure its replacement policy.
			Opt-in RBF, full RBF, and strict first-seen policies are supported.

	=== Peter Todd's full-RBF patchset ===		=== Peter Todd's full-RBF patchset ===
Line 47:		Line 52:
	0.8.x and later that implement full-RBF for all transactions in the		0.8.x and later that implement full-RBF for all transactions in the
	mempool. (Later versions also provide an option to enable RBF First-Seen-Safe (RBF-FSS) only.)		mempool. (Later versions also provide an option to enable RBF First-Seen-Safe (RBF-FSS) only.)
	~~A rebased version of the most recent patch is also available for~~
	~~contemporary [http://luke.dashjr.org/programs/bitcoin-ljr/ Bitcoin LJR] releases.~~

	Notably, the patchset also implements preferential peering that allows		Notably, the patchset also implements preferential peering that allows
Line 54:		Line 57:
	can circulate even if full-RBF nodes represent a small minority of the		can circulate even if full-RBF nodes represent a small minority of the
	network.		network.

	~~As of 2015-12-08, there are no known large miners or mining pools that~~
	~~implement full-RBF.~~

	* [https://github.com/petertodd/bitcoin/branches/all?utf8=%E2%9C%93&query=replace-by-fee-v0.10 Replace by fee patches for Bitcoin Core 0.10.x]		* [https://github.com/petertodd/bitcoin/branches/all?utf8=%E2%9C%93&query=replace-by-fee-v0.10 Replace by fee patches for Bitcoin Core 0.10.x]

Sgornick: /* See Also */ Add entry for Fee bumping, which is not related to RBF but is an alternative to RBF that might be considered.

2018-03-05T23:55:07Z

See Also: Add entry for Fee bumping, which is not related to RBF but is an alternative to RBF that might be considered.

← Older revision		Revision as of 23:55, 5 March 2018
Line 71:		Line 71:
	== See Also ==		== See Also ==

			* [[Fee bumping]]
	* [https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki BIP 125]		* [https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki BIP 125]
	* [https://www.reddit.com/r/Bitcoin/comments/3urm8o/optin_rbf_is_misunderstood_ask_questions_about_it/ Reddit: Questions about opt-in RBF]		* [https://www.reddit.com/r/Bitcoin/comments/3urm8o/optin_rbf_is_misunderstood_ask_questions_about_it/ Reddit: Questions about opt-in RBF]

Sgornick: Add phrase Replace by fee as a form of transaction replacement, and link to that wiki article.

2018-03-05T23:50:36Z

Add phrase Replace by fee as a form of transaction replacement, and link to that wiki article.

← Older revision		Revision as of 23:50, 5 March 2018
Line 8:		Line 8:

	Beginning with Bitcoin Core 0.12.0 (eta Feb 1 2016), it is expected		Beginning with Bitcoin Core 0.12.0 (eta Feb 1 2016), it is expected
	that transaction replaceability will become widely available. This page		that one type of transaction replaceability, [[Replace by fee\|replace-by-fee]] (RBF), will become widely available. This page
	attempts to document the current state of transaction replaceability for		attempts to document the current state of transaction replaceability for
	wallet authors who want to use that feature.		wallet authors who want to use that feature.

Polve: /* Bitcoin Core 0.12.0 */

2016-06-17T08:19:25Z

Bitcoin Core 0.12.0

← Older revision		Revision as of 08:19, 17 June 2016
Line 31:		Line 31:
	=== Bitcoin Core 0.12.0 ===		=== Bitcoin Core 0.12.0 ===

	''Bitcoin Core 0.12.0 has ~~not~~ been released ~~yet. It is expected~~ in ~~Jan/~~Feb 2016.''		''Bitcoin Core 0.12.0 has been released in Feb 2016.''

	Bitcoin Core 0.12.0 uses the initial implementation of opt-in full-RBF		Bitcoin Core 0.12.0 uses the initial implementation of opt-in full-RBF