Repository navigation
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.
Moves the circuits to Noir 1.0.0-rc.3 and barretenberg 6.0.0-rc.6, the toolchain Aztec v6 ships with, and releases them as version 0.22.0. bb 6 derives Honk Fiat-Shamir challenges differently from bb 5 (AztecProtocol/aztec-packages#500), so every verification key, the circuit root and the Solidity verifiers change.
@aztec-foundation/bb.js6.0.0-rc.6 (the npm name of@aztec/bb.jsfrom bb 6 on) and the Noir JS packages at 1.0.0-rc.3.BoundedVec::from_parts_uncheckedcalls insig-check/commonbecomeBoundedVec::from_parts, which in Noir 1.0.0-rc.3 has the same body.noir_json_parserv0.4.0-5 (chore: merge noir-lang/main for Noir 1.0.0-rc.3 compatibility noir_json_parser#2) andnoir_base64from upstream v0.5.1, which make the same change.0x0efa41b1…f7f6a73b), outer Solidity verifiers,DeploySubVerifier.s.solvkey hashes and Solidity test fixtures.Deploying the new sub-verifiers and recording them in
deployments/addresses-*.jsonfollows the merge.