chore: update sepolia contracts

[ctrlc03]

Summary by CodeRabbit

• Documentation

  • Updated operator setup and running guides with refreshed Sepolia contract addresses and deployment block numbers.

• Chores

  • Updated deployed-contract metadata across the enclave ecosystem to reflect the latest deployment snapshot (addresses, block numbers, proxies/init configs, token references).
  • Adjusted an operational parameter (submission window) from 300 to 10.
  • Renamed a verifier entry in the deployment metadata.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

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

Project	Deployment	Review	Updated (UTC)
enclave-docs	Ready	Preview, Comment	Jan 15, 2026 9:48am

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
crisp	Skipped		Jan 15, 2026 9:48am

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates Sepolia deployment metadata across docs and deployment manifests: contract addresses, deployment block numbers, proxy records, and initData. No functional code, API, or signature changes; edits are data- and documentation-only. (50 words)

Changes

Cohort / File(s)	Summary
Documentation docs/pages/ciphernode-operators/index.mdx, docs/pages/ciphernode-operators/running.mdx	Updated Sepolia contract addresses and deploy_block/chain config values for Enclave, CiphernodeRegistry, BondingRegistry and related entries in examples.
CRISP deployed manifest examples/CRISP/packages/crisp-contracts/deployed_contracts.json	Large update of Sepolia deployment snapshot: new addresses and blockNumber for numerous contracts (tokens, registries, verifiers/programs); updated proxy records (proxyAddress, proxyAdminAddress, implementationAddress), rewritten initData hex strings, token reference swaps, and RiscZeroGroth16Verifier → MockRISC0Verifier.
Enclave deployed manifest packages/enclave-contracts/deployed_contracts.json	Updated block numbers and addresses across many contracts; refreshed proxy metadata and initData; swapped base/ticket/license token references; submissionWindow adjusted (300 → 10); consolidated verifier/program entries to reflect new snapshot.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• chore: update sepolia contracts #1154 — Overlapping edits to Sepolia deployment JSONs and CRISP/enclave proxy implementation entries.
• chore: verify proxy and implementation contracts #1005 — Related changes introducing/adjusting proxyRecords, implementationAddress and proxy-aware deployment metadata.
• new sepolia deployment #166 — Updates to Sepolia deployment artifacts (MockComputeProvider/MockDecryptionVerifier/MockE3Program) similar to manifests changed here.

Suggested labels

documentation

Suggested reviewers

• hmzakhalid
• 0xjei

Poem

🐇
I hopped through JSON, hex and block,
Swapped addresses — click, tick, tick-tock.
Proxies hugged and tokens in line,
Sepolia’s snapshot set to shine,
A rabbit’s patch — quick, neat, and slick ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'chore: update sepolia contracts' directly and accurately reflects the main changes in the changeset, which consist entirely of updating contract addresses, deployment blocks, and related configuration data across multiple Sepolia deployment files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cae8541 and 8ab5445.

📒 Files selected for processing (4)

• docs/pages/ciphernode-operators/index.mdx
• docs/pages/ciphernode-operators/running.mdx
• examples/CRISP/packages/crisp-contracts/deployed_contracts.json
• packages/enclave-contracts/deployed_contracts.json

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/pages/ciphernode-operators/index.mdx

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: cedoor
Repo: gnosisguild/enclave PR: 752
File: packages/enclave-contracts/contracts/Enclave.sol:15-17
Timestamp: 2025-09-19T11:16:53.825Z
Learning: The Enclave contract in the gnosisguild/enclave repository has not been deployed yet as of September 2025, so storage layout considerations for upgradeable contracts don't apply to current changes.

📚 Learning: 2025-09-19T11:16:53.825Z

Learnt from: cedoor
Repo: gnosisguild/enclave PR: 752
File: packages/enclave-contracts/contracts/Enclave.sol:15-17
Timestamp: 2025-09-19T11:16:53.825Z
Learning: The Enclave contract in the gnosisguild/enclave repository has not been deployed yet as of September 2025, so storage layout considerations for upgradeable contracts don't apply to current changes.

Applied to files:

• packages/enclave-contracts/deployed_contracts.json
• examples/CRISP/packages/crisp-contracts/deployed_contracts.json
• docs/pages/ciphernode-operators/running.mdx

🪛 Gitleaks (8.30.0)

packages/enclave-contracts/deployed_contracts.json

[high] 23-23: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 41-41: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 42-42: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 81-81: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

examples/CRISP/packages/crisp-contracts/deployed_contracts.json

[high] 23-23: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 41-41: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 42-42: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 81-81: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: build_sdk
• GitHub Check: build_ciphernode_image
• GitHub Check: build_e3_support_dev
• GitHub Check: integration_prebuild
• GitHub Check: build_crisp_sdk
• GitHub Check: build_enclave_cli
• GitHub Check: rust_unit
• GitHub Check: rust_integration
• GitHub Check: test_net

🔇 Additional comments (3)

docs/pages/ciphernode-operators/running.mdx (1)

103-110: LGTM! Documentation config examples are consistent.

Both CLI and Docker configuration blocks are updated with matching addresses and deploy blocks. The values align with the deployment manifest in packages/enclave-contracts/deployed_contracts.json.

Also applies to: 169-176

packages/enclave-contracts/deployed_contracts.json (1)

1-109: LGTM! Deployment manifest is internally consistent.

All contract address cross-references are correctly wired:

• Token references (baseToken, ticketToken, licenseToken, feeToken) correctly point to their respective token contract addresses
• Registry references in Enclave correctly point to the proxy addresses

The submissionWindow: "10" (line 64) is notably short but appropriate for a testnet deployment where faster iteration is needed.

Regarding the Gitleaks static analysis alerts: these are false positives. The flagged values are public Ethereum contract addresses on Sepolia testnet, not API keys or secrets.

examples/CRISP/packages/crisp-contracts/deployed_contracts.json (1)

1-131: LGTM! CRISP deployment manifest is consistent.

The base contract addresses (lines 1-108) match the main deployment manifest in packages/enclave-contracts/deployed_contracts.json.

CRISP-specific contract wiring is correct:

• CRISPProgram.enclave correctly references the Enclave proxy address
• CRISPProgram.verifierAddress references MockRISC0Verifier (appropriate for testnet)
• CRISPProgram.honkVerifierAddress correctly references HonkVerifier

Both RiscZeroGroth16Verifier and MockRISC0Verifier are deployed, with the mock being used by CRISPProgram - sensible for testnet.

The Gitleaks alerts are false positives (public contract addresses, not secrets).

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}