summaryrefslogtreecommitdiff
path: root/bip-0125.mediawiki
diff options
context:
space:
mode:
Diffstat (limited to 'bip-0125.mediawiki')
-rw-r--r--bip-0125.mediawiki10
1 files changed, 3 insertions, 7 deletions
diff --git a/bip-0125.mediawiki b/bip-0125.mediawiki
index 7dfdcbe..8cd7649 100644
--- a/bip-0125.mediawiki
+++ b/bip-0125.mediawiki
@@ -132,7 +132,7 @@ confirmed, and so some users advocated that replacement should be
disallowed.
To address those concerns, a variation on RBF was created that
-required that the replacement transaction pay all of same outputs as
+required that the replacement transaction pay all of the same outputs as
the original transaction in equal or greater amount. This was called
RBF First Seen Safe (RBF-FSS), and the original RBF became known as
full-RBF. Although agreeable to recipients who relied on the
@@ -171,13 +171,9 @@ Actual replacement may be unreliable until two conditions have been satisfied:
# Enough hash rate has upgraded to support replacement, allowing for reasonable probability that a replacement can be mined.
-==Client support==
+==Backwards compatibility==
-No known wallet currently creates transactions by default with
-nSequence set below (0xffffffff - 1), so no known existing wallet
-explicitly signals replaceability by default. No known popular wallet
-spends other users' unconfirmed transactions by default, so no known
-existing wallets signals inherited replaceability.
+At the time opt-in RBF support was added/proposed, no known wallet created transactions by default with nSequence set below (0xffffffff - 1), so no known wallet explicitly signaled replaceability by default. Also no known popular wallet spent other users' unconfirmed transactions by default, so no known wallets signaled inherited replaceability.
==See also==