fix: exercise vendored proof-tool compatibility - #2
Merged
Conversation
mellowcroc
marked this pull request as ready for review
August 20, 2026 13:44
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
1 participant
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
Why
proof-tool carries its MPC parallelization in deterministic gnark vendor patches. Building with
-mod=modbypassed those patches, so Relay compatibility CI could pass without testing the shipped ceremony implementation. Whole-second timestamps could also makeaccepted_atequal todestroyed_at, which proof-tool correctly rejects.Verification
go test ./...RELAY_PROOF_TOOL_FULL=1k=21 contribute-and-accept lane passed against rebased proof-tool with vendored gnark (13m20s)Companion to zksecurity/proof-tool#8.