Skip to content

feat(contracts)!: route the large committee on testnets and release it - #2537

Open
ctrlc03 wants to merge 8 commits into
large/committee-largefrom
large/release-large
Open

ctrlc03 wants to merge 8 commits into
large/committee-largefrom
large/release-large

Conversation

@ctrlc03

@ctrlc03 ctrlc03 commented Nov 19, 2026 •

Copy link
Copy Markdown
Collaborator

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.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 eight pairs, so the release workflow, verify-release and
    the installer require the Large artifacts.
  • check:committee, the circuit tooling tests, the scripts/circuits/README.md push steps, the
    COMMITTEE_THRESHOLDS_ONCHAIN fixture and the docs list Large and expect eight pairs.
  • The protocol version and SCHEMA_VERSION are not raised here. Main already declares both as 9,
    and no tag carries SCHEMA_VERSION 9 yet. Note for the release: tag v0.20.0-dev.3 already
    declares (protocol 9, node generation 2), and live Sepolia's NodeReleaseRegistry requires that
    pair, 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 --noEmit for interfold-contracts, cargo check --all-targets for e3-zk-prover,
    e3-cli and e3-zk-build.
  • The regenerated VK catalogue, Solidity verifiers (including the Large pairs), BFV VK-binding
    fixture and layout-lock fixtures are in chore(circuits): regenerate the circuit outputs of the large stack #2541 (large/circuit-outputs), near the top of
    the stack; until then the circuit and hardhat deployment
    checks fail by design.

Compatibility

Breaking within the unreleased protocol-9 cutover (no separate counter change).

  • New verifier deployments and artifacts: Sepolia and local deployments route two more pairs, and
    the circuit release carries eight pairs instead of six. Mainnet is unaffected.
  • The next release must publish insecure-64/large and secure-8192/large.
  • The Sepolia cutover for Large (dkgWindow, the threshold batch) is in fix(contracts): prepare the Sepolia cutover for the large committee #2540.

Follow-ups (not in this stack)

  • Network buffer limits (crates/net/src/ingress_limits.rs, event_buffer.rs) are sized for
    N = 19.
  • No code guard keeps Large off mainnet beyond the checked-in routes and configuration.
  • The nodes fold step and the 23-leaf C6 Chonk stack are not yet measured at n = 45.

@vercel

vercel Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
interfold-dashboard Ready Ready Preview Nov 20, 2026 9:49am UTC
interfold-docs Ready Ready Preview Nov 20, 2026 9:49am UTC

Request Review

@coderabbitai

coderabbitai Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You'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.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

Commits

Reviewing files that changed from the base of the PR and between d51a593 and 4904ab1.

Files selected for processing: 22

  • .github/workflows/releases.yml
  • RELEASING.md
  • circuits/README.md
  • crates/zk/prover/supported-configurations.json
  • docs/architecture/circuit-artifacts.md
  • docs/architecture/committee-selection.md
  • docs/architecture/upgrades.md
  • docs/pages/build/requesting-an-e3.mdx
  • docs/pages/index.mdx
  • docs/pages/learn/cryptography.mdx
  • docs/pages/operate/running.mdx
  • docs/pages/operate/tickets-and-sortition.mdx
  • packages/interfold-contracts/deploy/protocol/example.protocol.config.json
  • packages/interfold-contracts/deploy/protocol/sepolia-protocol.config.json
  • packages/interfold-contracts/scripts/utils.ts
  • packages/interfold-contracts/test/fixtures/constants.ts
  • scripts/checks/committee.sh
  • scripts/checks/integration-committee.test.ts
  • scripts/circuits/README.md
  • scripts/circuits/artifacts.test.ts
  • scripts/circuits/bfv-bindings.test.ts
  • tests/integration/lib/utils.sh
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

@ctrlc03
ctrlc03 force-pushed the large/release-large branch from e0a1b99 to c9c0294 Compare November 19, 2026 22:58
@ctrlc03
ctrlc03 force-pushed the large/release-large branch from c9c0294 to 8a8a29c Compare November 19, 2026 23:30
@ctrlc03 ctrlc03 changed the title feat(contracts)!: route the large committee on testnets and release its circuits feat(contracts)!: route the large committee on testnets and release it Nov 20, 2026
@ctrlc03
ctrlc03 force-pushed the large/release-large branch from 64c47fb to 47c91d0 Compare November 20, 2026 08:50
@ctrlc03
ctrlc03 added this pull request to stack #2538 November 20, 2026 08:50
@ctrlc03
ctrlc03 removed this pull request from stack #2538 November 20, 2026 09:11
@ctrlc03
ctrlc03 force-pushed the large/release-large branch from 47c91d0 to 72eeddb Compare November 20, 2026 09:11
@ctrlc03
ctrlc03 added this pull request to stack #2543 November 20, 2026 09:22
zahrajavar and others added 3 commits November 20, 2026 09:38
…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.

This branch was successfully deployed

2 active deployments
Preview – interfold-dashboard — 4904ab11 Deployed Nov 20, 2026 by vercel[bot]
Preview – interfold-docs — 4904ab11 Deployed Nov 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants