[zk-token-sdk] Add a length check on range proof commitment length #34165
Conversation
This file contains 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
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #34165 +/- ##
=========================================
- Coverage 81.9% 81.9% -0.1%
=========================================
Files 819 819
Lines 220122 220177 +55
=========================================
+ Hits 180386 180395 +9
- Misses 39736 39782 +46 |
samkim-crypto
added
v1.17
|
Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis. |
mergify bot
pushed a commit
that referenced
this pull request
Nov 20, 2023
…34165) add a length check on range proof commitment length (cherry picked from commit e251b86) # Conflicts: # zk-token-sdk/src/errors.rs # zk-token-sdk/src/instruction/batched_range_proof/batched_range_proof_u128.rs # zk-token-sdk/src/instruction/batched_range_proof/batched_range_proof_u256.rs # zk-token-sdk/src/instruction/batched_range_proof/batched_range_proof_u64.rs
samkim-crypto
added a commit
that referenced
this pull request
Nov 21, 2023
…ngth (backport of #34165) (#34182) * [zk-token-sdk] Add a length check on range proof commitment length (#34165) add a length check on range proof commitment length (cherry picked from commit e251b86) # Conflicts: # zk-token-sdk/src/errors.rs # zk-token-sdk/src/instruction/batched_range_proof/batched_range_proof_u128.rs # zk-token-sdk/src/instruction/batched_range_proof/batched_range_proof_u256.rs # zk-token-sdk/src/instruction/batched_range_proof/batched_range_proof_u64.rs * resolve conflict --------- Co-authored-by: samkim-crypto <skim13@cs.stanford.edu>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
#33525
Summary of Changes
When verifying range proof, I added a condition to check that the number of commitments are capped at
MAX_COMMITMENTS.This is a split PR from #34065.
Fixes #