-
Notifications
You must be signed in to change notification settings - Fork 1
Feat/scaling improvements #483
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
Closed
Closed
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
bbe4dbc
docs: add scaling improvements spec (unified sizing + MMCS + shared FRI)
diegokingston d566602
perf(tables): cap LT/LOAD/BRANCH/MEMW_R max_rows at 2^20
diegokingston c3f5719
perf(stark): deduplicate LdeTwiddles by domain size in multi_prove
diegokingston 3aa03e6
perf(fri): parallelize fold_evaluations_in_place with Rayon
diegokingston ccb7548
perf(prover): eliminate per-row Vec alloc in commit_columns_bit_reversed
diegokingston 4b25ce3
Revert "perf(tables): cap LT/LOAD/BRANCH/MEMW_R max_rows at 2^20"
diegokingston 38a8100
feat(stark): shared FRI for multi-table proving
diegokingston 00d4ec4
feat(stark): unified-domain LDE for shared FRI across different table…
diegokingston 62ce50e
Merge branch 'main' into feat/scaling-improvements
gabrielbosio 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
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.
Low – Silent truncation vs. panic on length mismatch
The sequential path accesses
inv_twiddles[j]forj in 0..half, which panics with a clear index-out-of-bounds ifinv_twiddles.len() < half.The parallel path uses
par_chunks(2).zip(inv_twiddles.par_iter()), which silently truncates to the shorter of the two iterators. Ifinv_twiddlesis shorter than expected, fewer elements are folded,foldedhas the wrong length, and the resulting proof is silently incorrect — no panic, no error.Since FRI always operates on power-of-2-aligned data the lengths always match in practice. But for a cryptographic primitive, silent wrong-output is strictly worse than a loud panic. Consider adding a debug assertion: