fix(bb.js): cache compressed browser CRS - #25290
Open
Wondertan wants to merge 1 commit into
Open
Conversation
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
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.
What
Why
Crs.new(size)can preload CRS without constructing the WASM prover, but the compressed browser path currently writes nothing to IndexedDB untilsrsInitSrsdecompresses it. Navigation or reload after preload therefore repeats the large range request. This makes the existing CRS loader durable while leaving normalBarretenberg.new({ srsSize })behavior unchanged.Verification
cached_net_crs: 2/2 passing.CI is awaiting a maintainer-added
ci-externalorci-external-oncelabel.