-
Notifications
You must be signed in to change notification settings - Fork 187
feat(stark): add LogUp lookup argument module with bus abstraction #1159
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
base: main
Are you sure you want to change the base?
Changes from 9 commits
19c0612
068a1a0
67835fe
0dcbf8d
4fcdbef
08401b7
9a8717a
ed7287c
8a1496a
bc9e507
f3dfc00
356e109
d733b67
b791d9c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,6 +10,7 @@ pub mod examples; | |
| pub mod frame; | ||
| pub mod fri; | ||
| pub mod grinding; | ||
| pub mod lookup; | ||
| pub mod multi_table_prover; | ||
| pub mod multi_table_verifier; | ||
| pub mod proof; | ||
|
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. The code introduces a new module
Without the actual implementation code for the |
||
|
|
||
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.
Correctness
ByteConversionforFieldElement<Degree2GoldilocksExtensionField>handle edge cases correctly. Particularly, ensure the new implementation correctly handles the case where the input byte slice is exactly 16 bytes long.Security
get_random_field_element_from_rngfunction, ensure that the sample byte array is securely zeroized after use to avoid any leakage of sensitive data.if int_sample < GOLDILOCKS_PRIMEcheck due to branching based on secret data (the prime check).Performance
alloc::vec::Vec::<u8>::with_capacity(16)is efficient and necessary. Consider alternatives if allocations can be reduced.Bugs & Errors
unwraporpaniccould cause potential runtime issues; verify that this is expected behavior and double-check that all error cases are properly handled (e.g., unexpected byte lengths).Code Simplicity
from_bytes_beandfrom_bytes_leis quite similar; consider refactoring to avoid code duplication and improve maintainability.Overall, this pull request addresses the implementation of byte conversion traits and transcript support for cryptographic field elements. Correct attention is needed for edge case handling, potential security vulnerabilities, such as timing attacks and proper zeroization of sensitive data, and ensuring efficient memory usage. Address these concerns before merging.