Fix/browser capability gate - #359
Open
BigEngine-code wants to merge 5 commits into
Open
Conversation
…TREE_LEVELS in client; add benchmark script and README guidance
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
2 participants
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.
Closes #315
What changed
Added a browser capability gate that checks for WebAssembly, BigInt,
crypto.subtle, and a secure context before the app mounts. Added clear, localized messages for unsupported capabilities and insecure HTTP usage, with styling based on the app's existing design tokens.Why
Closes #315
This prevents unsupported browsers and insecure LAN connections from reaching proof-generation flows and instead provides actionable guidance to the user.
Testing
cd circuits && npm test)cd contracts && cargo test)npm run e2e)cd app && npm run dev)Screenshots