Repository navigation
Sepolia protocol deployment predates the node release gate, so 0.18.0 ciphernodes cannot start #2011
Description
Summary
The Sepolia protocol deployment predates the node release gate. A 0.18.0 ciphernode cannot start against it.
Evidence (checked 2026-09-25)
- Sepolia
Interfoldproxy0x3E856E24c7a95d0e04d387f847DA6FA9f6F6c20Cpoints to implementation0x282eb30634c46ac6a1c00b25c1bc92cb7d011afd. The implementation bytecode does not contain thenodeReleaseRegistry()selector (0x06c29676). - The proxy has one
Upgradedevent, at deployment (block 11,534,994, 2026-08-21). The release gate merged on 2026-08-28 (feat(upgrades): node release gate [skip-line-limit] #1892). cast call 0x3E85…c20C 'nodeReleaseRegistry()(address)'reverts.bondingRegistry()andciphernodeRegistry()return values.crates/evm/src/node_release.rs:57-63reads all three at startup.ciphernode_builder.rs:655-668calls it for every enabled chain with no network exception.
Reproduce
- Run
interfold ciphernode setup --network sepolia …with a throwaway key. - Run
interfold start --config <dir>/interfold.config.yaml. - The node exits with
failed to read Interfold release dependencies.
Impact
No ciphernode on a release with the release gate can serve Sepolia E3s. The docs, ciphernode setup, and the Sepolia tutorials point to this deployment. PR #2010 adds a dated warning to the docs.
Activity
hmzakhalid commentedon Sep 30, 2026
Rechecked on 2026-09-30. Still open.
nodeReleaseRegistry()on the SepoliaInterfoldproxy0x3E856E24c7a95d0e04d387f847DA6FA9f6F6c20Cstill reverts. The implementation is0x282eb30634c46ac6a1c00b25c1bc92cb7d011afd.29fbd7152):crates/evm/src/node_release.rs:72). The check applies to every enabled ciphernode chain (crates/ciphernode-builder/src/ciphernode_builder.rs:720), and v0.17.0 has the same gate.start --bootstrapskips these components, so bootstrap nodes are not blocked.docs/pages/reference/contracts.mdx:138documents the failure.hmzakhalid commentedon Oct 8, 2026
Sepolia's
NodeReleaseRegistryis live now. On Sepolia,Interfold.nodeReleaseRegistry()returns0x772caB77BFc39690e13dA2995E926Fb090aD034B, and the registry reads protocol 7 and generation 2 (deployed with 0.19.0-test.1, #2184). So nodes can start there again. Closing this issue.For the v0.19 test, Sepolia gets a fresh protocol deployment: its parameter set 2 holds the parameters from before #2195, and a registered parameter set cannot be replaced.