-
Notifications
You must be signed in to change notification settings - Fork 548
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
Don't check zkApp proofs in the snark if application will fail anyway #12490
Conversation
!ci-build-me |
!ci-build-me |
3 similar comments
!ci-build-me |
!ci-build-me |
!ci-build-me |
132eb1a
to
09f12b6
Compare
@deepthiskumar your new changes here seem to have broken the CI, and this change is safe as a standalone -- it weakens the snark constraints, but leaves the current verification alone. I've reverted them and merged develop; your changes are in I'm going to open a follow-up PR that skips the verification of those proofs. |
!ci-build-me |
!ci-build-me |
This PR proposes an alternative approach to #12397. This allows us to skip verification of failed zkApp commands' proofs in both the snark and the block verification logic.
Checklist: