Fix ZK verifier mode handling#1647
Merged
Merged
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.
Summary
proof.claims.is_zk()in helper/example/generated verifier paths.Root Cause
Some verifier call sites passed
zk = falseunconditionally after the modular verifier split. That causes valid ZK proofs to fail consistency checks as if they were clear proofs.Validation
cargo fmt -qcargo check -q -p jolt-sdk --tests --features hostcargo check -q -p recursioncargo check -q -p jolt-evalcargo check -q --features hostcargo clippy --all --features host -q --all-targets -- -D warningscargo clippy --all --features host,zk -q --all-targets -- -D warningscargo nextest run -p jolt-prover-legacy muldiv --cargo-quiet --features hostcargo nextest run -p jolt-prover-legacy muldiv --cargo-quiet --features host,zkPosted by the assistant on behalf of Quang Dao using GPT-5.