|
|
|
@ -412,7 +412,7 @@ The use and meaning of this field has changed over time.
|
|
|
|
|
[[original_tx_replacement]]
|
|
|
|
|
===== Original sequence-based transaction replacement
|
|
|
|
|
|
|
|
|
|
The sequence field was originally intended to allow creation of
|
|
|
|
|
The ((("sequence-based transaction replacement", id="sequence-replace")))sequence field was originally intended to allow creation of
|
|
|
|
|
multiple versions of the same transaction, with later versions replacing
|
|
|
|
|
earlier versions as candidates for confirmation. The sequence number
|
|
|
|
|
tracked the version of the transaction.
|
|
|
|
@ -500,7 +500,7 @@ sequence-based transaction replacement was disabled in an early version
|
|
|
|
|
of the Bitcoin software. For several years, Bitcoin full nodes would
|
|
|
|
|
not allow an unconfirmed transaction containing a particular input (as
|
|
|
|
|
indicated by its outpoint) to be replaced by a different transaction
|
|
|
|
|
containing the same input. However, that situation didn't last forever.
|
|
|
|
|
containing the same input. However, that situation didn't ((("sequence-based transaction replacement", startref="sequence-replace")))last forever.
|
|
|
|
|
|
|
|
|
|
[[sequence-bip125]]
|
|
|
|
|
===== Opt-in transaction replacement signaling
|
|
|
|
|