-
Notifications
You must be signed in to change notification settings - Fork 13
fix(key-wallet, dash-spv): re-emit late knowledge — record corrections, durable rescans, address-pool repair #979
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
HashEngineering
wants to merge
6
commits into
dev
Choose a base branch
from
fix/key-wallet-rescan-changeset
base: dev
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
6 commits
Select commit
Hold shift + click to select a range
39300ae
fix(key-wallet): correct born-wrong records when a rescan re-attribut…
HashEngineering 80e07b8
fix(dash-spv): durable pending-sweep set — replay interrupted script …
HashEngineering afba7af
feat(key-wallet): AddressPool::ensure_contiguous_to — repair sparse p…
HashEngineering 530c178
fix(key-wallet): attribute born-spent funding outputs onto their spen…
HashEngineering c3e8e0e
feat(key-wallet): expose the account's spent-outpoint set for store r…
HashEngineering 9a68e65
fix(key-wallet, dash-spv): review round — wallet-scope born-spent att…
HashEngineering 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
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.
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.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
The doc comment still describes the defect in the present tense.
Lines 585-587 state that
confirm_transactionre-emits only when the context changed, "so neither the in-memory record nor any event carries the correction". The test name and every assertion require the correction. Rewrite these sentences as historical context, for example "before the fix,confirm_transactionre-emitted only when the context changed", so a reader can tell which behavior the test pins.🤖 Prompt for AI Agents