-
Notifications
You must be signed in to change notification settings - Fork 49
feat(drive): add shielded pool storage, actions, and verification (Medusa part 2) #3198
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
Merged
Changes from all commits
Commits
Show all changes
30 commits
Select commit
Hold shift + click to select a range
855d593
feat(drive): add shielded pool storage, actions, and verification
QuantumExplorer 2c74098
fix(drive): use RootTree enum instead of magic number 72u8 (#3205)
QuantumExplorer c93ae0e
fix(drive): guard against max_elements=0 in encrypted notes verificat…
QuantumExplorer 73c058a
fix(drive): replace expect/unwrap with error propagation in productio…
QuantumExplorer d1c1a61
fix(drive): import nullifier constants instead of duplicating them (#…
QuantumExplorer 357e9b0
fix(drive): replace unchecked integer casts with try_from (#3201)
QuantumExplorer 5218ddf
fix(drive): correct tree types in shielded pool estimated costs (#3200)
QuantumExplorer 743faeb
fix(drive): match min_depth between prove and verify for trunk query …
QuantumExplorer 95f8e04
Merge branch 'v3.1-dev' into feat/zk-drive
QuantumExplorer 77615a6
fix(drive): resolve clippy lints in shielded module
QuantumExplorer 2543341
fix(drive): fix CI failures for shielded module
QuantumExplorer 0432425
fix(drive): fix bugs found in CodeRabbit review of shielded module
QuantumExplorer 7221772
refactor(dpp): replace ProtocolError::Generic with specific error types
QuantumExplorer 7ca50a6
build(drive): update grovedb to latest develop (99a2ab01)
QuantumExplorer ea9e63c
refactor(drive): move per-block nullifier paths to shielded credit pool
QuantumExplorer f2b5338
refactor(drive): extract shielded pool ops into versioned functions a…
QuantumExplorer 0b82b6b
refactor(drive): derive notes and anchor from transition in try_from_…
QuantumExplorer 295f777
fix(drive): harden bincode decoding and fix limit==0 edge case in shi…
QuantumExplorer f483b62
Merge branch 'v3.1-dev' into feat/zk-drive
QuantumExplorer 3fb7801
refactor(drive): address review feedback on shielded nullifiers
QuantumExplorer a8de751
fix(drive): adapt proof verification for shielded pool tree structure…
QuantumExplorer 4d13397
refactor(drive): upgrade grovedb, fix estimated costs, and clean up d…
QuantumExplorer 0f5acd5
refactor(drive): replace nullifier tuple type aliases with structs
QuantumExplorer acf830a
Merge remote-tracking branch 'origin/v3.1-dev' into feat/zk-drive
QuantumExplorer b78d53e
Merge remote-tracking branch 'origin/v3.1-dev' into feat/zk-drive
QuantumExplorer 04c537e
feat(drive): adapt to grovedb SubelementsDeletionBehavior per-op enum…
QuantumExplorer 83ea01f
chore: update grovedb to b191ff27 with DontCheckWithNoCleanup
QuantumExplorer 160749d
fix(drive-abci): update version upgrade test for proper DeleteChildre…
QuantumExplorer 3220e43
Merge remote-tracking branch 'origin/v3.1-dev' into feat/zk-drive
QuantumExplorer 82eddb8
chore: update grovedb to dd99ed1d
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
Large diffs are not rendered by default.
Oops, something went wrong.
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
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.
🧩 Analysis chain
🌐 Web query:
In Rust semver, is adding a variant to a public enum without#[non_exhaustive]considered a breaking change for downstream crates?💡 Result:
Yes. In Rust, adding a new variant to a public enum that is not marked
#[non_exhaustive]is considered a SemVer-breaking change for downstream crates, because downstream code can (and often does) exhaustivelymatchon the enum, and a new variant makes those matches fail to compile. [1], [2]If the enum is
#[non_exhaustive], downstream crates are required to include a wildcard arm (or otherwise handle unknown variants), so adding variants is intended to be non-breaking. [1]Sources:
[1] Rust Cargo Book — SemVer Compatibility
[2] Effective Rust — SemVer discussion of adding enum variants
🏁 Script executed:
cat -n packages/rs-dpp/src/errors/protocol_error.rs | head -160Repository: dashpay/platform
Length of output: 6248
🏁 Script executed:
rg "AddressWitnessError|ShieldedBuildError" --type rust -B 2 -A 2Repository: dashpay/platform
Length of output: 22729
This is a breaking expansion of the public
ProtocolErrorsurface.ProtocolErroris public and not#[non_exhaustive], so addingAddressWitnessErrorandShieldedBuildErrorbreaks downstream exhaustivematches. These variants are returned from public builder and witness-verification functions, so callers that key offGenericspecifically will miss them unless this release is treated as breaking.🤖 Prompt for AI Agents