Implement ADR-0026 beta readiness remediation#10
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
Implements the ADR-0026 P0 beta-readiness remediation pass for ZeroJ.
This PR hardens BBS secret handling, fixes the gnark negative e2e path, pins PlonK on-chain protocol constants, promotes a TxOutRef-bound Groth16 validator into main sources, updates the Yaci e2e harness for the known DevKit BLS-costing issue, and documents the remaining production gates.
Key Changes
BbsSecretKey/BbsKeyPairtoString()output.signature.e()multiplication through the secret-scalar provider path.fr, G1 generator, and G2 generator checks.Groth16BLS12381TxOutRefBindingVerifierin main sources.blstJNIBLS-costing failure.zeroj-blst.zeroj-blstdocs from FFM to JNI/SWIG.