forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat(wallet): let a deliberate unlock opt out of the automatic coin locks #7635
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.
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
Open
UdjinM6
wants to merge
3
commits into
dashpay:develop
Choose a base branch
from
UdjinM6:wallet-user-unlock-optout
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| Wallet changes | ||
| -------------- | ||
|
|
||
| - Unlocking an output with `lockunspent` (or through the Dash-Qt coin control | ||
| dialog) now also opts that output out of the automatic masternode-collateral | ||
| and dust-protection locks until you lock it again. Previously those automatic | ||
| locks were reapplied on every wallet load, which silently undid the unlock and | ||
| left the output unspendable with no indication why. Locking the output again | ||
| hands it back to the automatic protection, as long as that lock is persistent: | ||
| `lockunspent` writes a lock to the wallet file only when asked to, and a | ||
| memory-only lock leaves the decision standing. The opt-out is stored in the | ||
| wallet file; an older Dash Core release reading the same wallet ignores the | ||
| record and reapplies the automatic locks as it did before. (#7635) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the registration wizard cancels, destroys, or fails a prepared registration, its existing cleanup paths (
src/qt/masternodewizard.cpp:223,:1709, and:1782) callunlockCoin()solely to release the temporary hold acquired byCollateralLockGuard. Routing that API toUnlockCoinByUser()now persists an automatic-lock opt-out; if the same collateral is subsequently registered, the kept in-memory lock masks the problem until restart, after whichAutoLockMasternodeCollaterals()skips it and leaves live collateral eligible for spending. Those wizard cleanup paths should usereleaseCoinLock(..., false), as the guard itself now does, rather than recording user intent.AGENTS.md reference: AGENTS.md:L15-L17
Useful? React with 👍 / 👎.