-
Notifications
You must be signed in to change notification settings - Fork 600
feat: generic key validation request #6474
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
benesjan
merged 37 commits into
master
from
05-16-feat_generic_key_validation_request_2
May 21, 2024
Merged
Changes from all commits
Commits
Show all changes
37 commits
Select commit
Hold shift + click to select a range
098018d
feat: generic key validation request 2
benesjan c93c9bf
more renamings
benesjan ed0e1be
fix
benesjan 81c2397
WIP
benesjan 5548256
more renamings
benesjan 29d6341
WIP
benesjan 96416a6
more fixes
benesjan c9f9728
fix
benesjan 27c17e9
remake-constants
benesjan eff9321
cleanup
benesjan dc77185
fix
benesjan dcb03b3
fixes
benesjan 9c501fc
WIP
benesjan 63bb79a
final touches
benesjan 1f284dd
Apply suggestions from code review
benesjan 851182c
naming fix
benesjan 6c0163d
addressing review comments
benesjan ec36d20
WIP
benesjan 2e4c27c
fix
benesjan 6d9ef2e
key store refactor
benesjan 081d39a
separating nsk_app scheme test
benesjan d59ea6b
gets ovsk_app test
benesjan 3120c5c
final touches
benesjan 4823e56
re-enabling validate_arrays_malformed_key_validation_requests_fails test
benesjan 4f79f88
minor key store test improvements
benesjan e9057c7
Merge branch 'master' into 05-16-feat_generic_key_validation_request_2
benesjan 94486a9
fixes after merge
benesjan 88f2749
updated comments
benesjan 734ed36
more comments
benesjan f762ef8
linking TODO
benesjan b06b25b
adding a todo
benesjan 2eaa631
Merge branch 'master' into 05-16-feat_generic_key_validation_request_2
benesjan bf27e44
WIP on fixing conflicts
benesjan 34648b2
more fixes
benesjan 35668d6
fixes
benesjan f41719f
nargo fmt
benesjan fd7f456
yarn fmt
benesjan 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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -52,7 +52,7 @@ The statically-sized nature the kernel & rollup circuits will restrict the quant | |
| | `MAX_ENCRYPTED_NOTE_PREIMAGE_HASHES_PER_CALL` | 128 | | ||
| | `MAX_NOTE_HASH_READ_REQUESTS_PER_CALL` | 128 | | ||
| | `MAX_NULLIFIER_READ_REQUESTS_PER_CALL` | 128 | | ||
| | `MAX_NULLIFIER_KEY_VALIDATION_REQUESTS_PER_CALL` | 1 | TODO: we shouldn't need this, given the reset circuit. | | ||
| | `MAX_KEY_VALIDATION_REQUESTS_PER_CALL | 16 | TODO: we shouldn't need this, given the reset circuit. | | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Following comment earlier. If we don't run into these limits because of the reset circuits, we can probably keep it is as for now but add a comment on it to make sure it is not forgotten and breaks applications in the future? 👀 |
||
| | `MAX_PRIVATE_CALL_STACK_LENGTH_PER_CALL` | 32 | | ||
| | `MAX_PUBLIC_CALL_STACK_LENGTH_PER_CALL` | 32 | | ||
|
|
||
|
|
@@ -71,7 +71,7 @@ The statically-sized nature the kernel & rollup circuits will restrict the quant | |
| | `MAX_ENCRYPTED_NOTE_PREIMAGE_HASHES_PER_TX` | 128 | | ||
| | `MAX_OPTIONALLY_REVEALED_DATA_LENGTH_PER_TX` | 4 | | ||
| | `MAX_NOTE_HASH_READ_REQUESTS_PER_TX` | 128 | TODO: we shouldn't need this, given the reset circuit. | | ||
| | `MAX_NULLIFIER_KEY_VALIDATION_REQUESTS_PER_TX` | 4 | TODO: we shouldn't need this, given the reset circuit. | | ||
| | `MAX_KEY_VALIDATION_REQUESTS_PER_TX` | 64 | TODO: we shouldn't need this, given the reset circuit. | | ||
| | `MAX_PRIVATE_CALL_STACK_LENGTH_PER_TX` | 32 | | ||
| | `MAX_PUBLIC_CALL_STACK_LENGTH_PER_TX` | 32 | | ||
|
|
||
|
|
||
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.
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.
Not related to your PR, just me being confused here, why is it ia note preimage hash here? What is that actually used for 🤔 @dbanks12 I might annoy you with this? Why is it a pre-image hash? We are usually providing a hash of the full log which is a full section of encrypted data for the notes.
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.
I would say it's just stale.
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.
I have no clue! I am very out of the loop with how logs / log-hashes work....
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.
Oh, sorry for tagging you @dbanks12, just saw now it was the private kernel 😬 I tagged you in.