fix(dashmate): form accepts invalid BLS key - #961
Merged
Conversation
shuplenkov
changed the title
shumkov
requested changes
Apr 24, 2023
markin-io
pushed a commit
that referenced
this pull request
Apr 28, 2023
6 tasks
HashEngineering
pushed a commit
to HashEngineering/platform
that referenced
this pull request
Aug 20, 2026
Brings in dashpay/rust-dashcore#961, which stops a never-broadcast transaction from crediting money that does not exist, plus the seven commits ahead of the previous pin. dashpay#961 adds `WalletEvent::TransactionsSwept`, the first subtractive event on the wallet bus: it names transactions the wallet removed because a later, final transaction provably beat them to their inputs. Three consumers matched exhaustively on `WalletEvent` and now handle it. - The balance handler routes it like any other balance-bearing variant. A sweep is the one event that can lower the balance, and its snapshot is post-removal like every other; dropping it would leave the corrected-away amount on screen until some later event happened to arrive. - The DashPay payment hooks ignore it: it carries txids, not records. A sent payment whose transaction was swept stays `Pending` — the hooks only advance a payment forward, and inventing a failure transition is a change to the payment state machine, not to event routing. - The core bridge projects it into a new `CoreChangeSet.swept_txids`, the only subtractive field on that type, and `is_empty_no_records` counts it — that filter decides whether the persister is called at all, so a sweep-only round has to survive it on the strength of the txids alone. Nothing consumes `swept_txids` yet; the persistence seam follows.
llbartekll
added a commit
that referenced
this pull request
Aug 22, 2026
…arsing) Pin fix/mnemonic-any-language-173ffac: the cherry-pick of dashpay/rust-dashcore#980 onto 173ffac0, the rev v4.2-dev already pins. This lands the BIP-39 fix without crossing the breaking key-wallet sweep changes (rust-dashcore #961/#962/#966/#969) that #4406 adapts platform to; once #4406 bumps onto rust-dashcore dev proper, the pin rejoins dev and this branch can be deleted. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
5 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue being fixed or feature implemented
Dashmate setup allow to input invalid BLS private key
What was done?
Fixed BLS private key validation function usage
How Has This Been Tested?
Manual
Breaking Changes
No
Checklist:
For repository code-owners and collaborators only