Skip to content

fix(contracts): prepare the Sepolia cutover for the large committee - #2540

Open
ctrlc03 wants to merge 3 commits into
large/release-largefrom
large/sepolia-cutover-large
Open

ctrlc03 wants to merge 3 commits into
large/release-largefrom
large/sepolia-cutover-large

Conversation

@ctrlc03

@ctrlc03 ctrlc03 commented Nov 20, 2026

Copy link
Copy Markdown
Collaborator

What and why

Split from #2398 (Zara's work). Stacked on #2537 (large/release-large); review that one first.

Prepares live Sepolia for the Large committee that #2537 routes there.

  • sepolia-protocol.config.json raises dkgWindow to 7200 s: one Large node measured 1,213 s of
    DKG proving on secure-8192. Live Sepolia holds 1800 s (the file's earlier 1200 s was stale). The
    value applies to every Sepolia E3: the worst-case committee setup, and CRISP's
    earliestVotingStart(), become 8,316 s after the request.
  • upgrade:v19 now prepares a batch when the live implementation predates a configured committee
    size (Sepolia, size 3): it treats the revert as an unset threshold instead of stopping.
  • docs/architecture/upgrades.md states the Sepolia cutover steps for Large.

Verification

Static checks only; CI runs the tests.

  • tsc --noEmit for interfold-contracts, prettier, node scripts/blueprint/check.mjs.
  • Live Sepolia read-only: getTimeoutConfig = (1800, 604800, 21600).

Compatibility

  • A Sepolia in-place batch carries setCommitteeThresholds(3, [34, 45]) (prepared by
    upgrade:v19) and setTimeoutConfig (added by hand); see docs/architecture/upgrades.md.
  • Mainnet is unaffected.

Follow-ups (not in this stack)

  • The Sepolia resume gates (nodeRelease.ts, resumeVrfSortition.ts) now need 45 active
    operators.

@coderabbitai

coderabbitai Bot commented Nov 20, 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 4904ab1 and fe5e972.

Files selected for processing: 3

  • docs/architecture/upgrades.md
  • packages/interfold-contracts/deploy/protocol/sepolia-protocol.config.json
  • packages/interfold-contracts/scripts/upgrade/v19Cutover.ts
  • 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

@vercel

vercel Bot commented Nov 20, 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

One Large node measured 1,213 s of DKG proving on secure-8192. Live
Sepolia holds a 1,800 s window (this file said 1,200 s), which leaves
little margin. Use the 7,200 s the example configuration uses.
…onfigured size

The Sepolia configuration now lists committee size 3. `upgrade:v19` reads each configured size from the implementation that the batch replaces, and the live Sepolia Interfold reverts without data on size 3, because its `CommitteeSize` has three members. Read that revert as an unset size, so the batch sets it after the upgrade.
…mittee

`upgrade:v19` applies the committee thresholds of the configuration but not its timeout windows. Live Sepolia holds a 1800 s DKG window, so the 7200 s of the configuration needs `setTimeoutConfig` in the Sepolia batch.

This branch was successfully deployed

2 active deployments
Preview – interfold-dashboard — fe5e9726 Deployed Nov 20, 2026 by vercel[bot]
Preview – interfold-docs — fe5e9726 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.

1 participant