Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 2 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
ctrlc03
force-pushed
the
large/release-large
branch
from
November 19, 2026 22:58
e0a1b99 to
c9c0294
Compare
ctrlc03
force-pushed
the
large/release-large
branch
from
November 19, 2026 23:30
c9c0294 to
8a8a29c
Compare
ctrlc03
force-pushed
the
large/release-large
branch
from
November 20, 2026 08:50
64c47fb to
47c91d0
Compare
ctrlc03
force-pushed
the
large/release-large
branch
from
November 20, 2026 09:11
47c91d0 to
72eeddb
Compare
…ts circuits Register insecure-64/large and secure-8192/large as testnet and local deployment routes, and require both pairs in the circuit release. - utils.ts exports INSECURE_LARGE_BFV_CONFIG and SECURE_LARGE_BFV_CONFIG and adds them to TESTNET_BFV_CONFIGS. The mainnet routes stay secure-only minimum, micro and small. - The example and Sepolia protocol configurations set the Large thresholds (quorum 34 of 45). The mainnet configuration is unchanged. - supported-configurations.json lists the eight pairs, so the release workflow and the installer require the Large artifacts. - check:committee, the circuit tooling tests and the docs expect eight pairs. Upgrade class: new verifier deployments and artifacts. The Large Honk verifiers and the verification-key commitments are generated from a full circuit build.
Large is a testnet route now, so the mock local deploy configures size 3. Probe it and expect sizes 0 1 2 3.
`pnpm store:circuits push` requires a build stamp for each of the eight release pairs, so the six listed builds no longer pass. The secure large pair is for Sepolia; mainnet committees are unchanged.
…d fixture The mock-verifier local deployment configures size 3 ([34, 45]) now that Large is a testnet route, so the fixture that mirrors it lists all four sizes.
ctrlc03
force-pushed
the
large/release-large
branch
from
November 20, 2026 09:48
72eeddb to
4904ab1
Compare
This branch was successfully deployed
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.
What and why
Split from #2398 (Zara's work). Stacked on #2536 (
large/committee-large); review that one first.Makes the Large committee requestable on Sepolia and local chains and adds it to the release.
utils.tsexportsINSECURE_LARGE_BFV_CONFIGandSECURE_LARGE_BFV_CONFIGand adds them toTESTNET_BFV_CONFIGS. The mainnet routes stay secure-only minimum, micro and small.mainnet configuration is unchanged.
supported-configurations.jsonlists eight pairs, so the release workflow,verify-releaseandthe installer require the Large artifacts.
check:committee, the circuit tooling tests, thescripts/circuits/README.mdpush steps, theCOMMITTEE_THRESHOLDS_ONCHAINfixture and the docs list Large and expect eight pairs.SCHEMA_VERSIONare not raised here. Main already declares both as 9,and no tag carries
SCHEMA_VERSION9 yet. Note for the release: tagv0.20.0-dev.3alreadydeclares (protocol 9, node generation 2), and live Sepolia's
NodeReleaseRegistryrequires thatpair, so governance cannot require a build of this stack there without raising a counter or
redeploying. That decision belongs to the release PR.
Verification
Static checks only; CI runs the tests.
bash scripts/checks/committee.sh,node scripts/blueprint/check.mjs, prettier,tsc --noEmitforinterfold-contracts,cargo check --all-targetsfore3-zk-prover,e3-cliande3-zk-build.fixture and layout-lock fixtures are in chore(circuits): regenerate the circuit outputs of the large stack #2541 (
large/circuit-outputs), near the top ofthe stack; until then the circuit and hardhat deployment
checks fail by design.
Compatibility
Breaking within the unreleased protocol-9 cutover (no separate counter change).
the circuit release carries eight pairs instead of six. Mainnet is unaffected.
insecure-64/largeandsecure-8192/large.dkgWindow, the threshold batch) is in fix(contracts): prepare the Sepolia cutover for the large committee #2540.Follow-ups (not in this stack)
crates/net/src/ingress_limits.rs,event_buffer.rs) are sized forN = 19.