-
Notifications
You must be signed in to change notification settings - Fork 55
fix(platform-wallet): build shielded spends against a Platform-recorded anchor #3977
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
Merged
QuantumExplorer
merged 6 commits into
v4.0-dev
from
fix/shielded-withdrawal-stranded-reservation
Jul 2, 2026
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
6959fe9
test(shielded): reproduce the withdrawal anchor-mismatch root cause (…
shumkov 1d1d21b
fix(shielded): build spends against a Platform-recorded anchor
shumkov 6a845c2
refactor(platform-wallet): address PR review on the shielded anchor p…
shumkov 91e0be4
test(drive-abci): pin acceptance of a real-proof spend at an older re…
QuantumExplorer 684bf84
chore: cargo fmt
QuantumExplorer 6a356ca
docs: drop investigation/spec working notes from the tree
QuantumExplorer 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
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.
💬 Nitpick: Third near-duplicate copy of the real-proof bundle-building boilerplate
Carried forward from prior-3, verified STILL VALID at 6a356ca (tests.rs unchanged in this delta).
test_valid_proof_with_older_recorded_anchor_succeeds(line 626) repeats, almost verbatim, the ~40-line real-proof construction already present intest_valid_shielded_withdrawal_proof_succeeds(line 409) andtest_valid_proof_with_unrecorded_anchor_returns_invalid_anchor_error(line 529): spending key/fvk/recipient/ask setup, note with fixed rho, memory commitment tree, build+prove+sign the Orchard bundle, compute the platform sighash, serialize the authorized bundle. This file already has aHelper Functions (transition-specific)section (line 23) for exactly this kind of shared scaffolding. With three copies in the same file, a future change to the bundle-building sequence (new required field, changed sighash input) is likely to be updated in two of the three copies and silently drift the third out of sync with what production code actually does. Consider extracting abuild_real_spend_bundle(tree, checkpoint_depth, notes_after_checkpoint) -> (bundle, anchor, ...)helper into that section.source: ['claude']