Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BIP 125: Change 'Client support' to 'Backwards compatibility' #1004

Merged
merged 1 commit into from Mar 3, 2021
Merged

BIP 125: Change 'Client support' to 'Backwards compatibility' #1004

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions bip-0125.mediawiki
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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==

Expand Down