Reference
Mainnet contracts
Fast lookup for the current documented Network Alpha deployment. Always run interfold config check or inspect the official deployment manifest before using these values operationally.
| Contract/token | Address |
|---|---|
| Interfold | 0x28cF63B459e6218C69EA97ea7D90541cf648c715 |
| CiphernodeRegistry | 0xC927A5B2d8F68697bC28C0670df05178c93df2d7 |
| BondingRegistry | 0x0ec90465095C21830BEcED07e032809A2Bd2915F |
| SlashingManager | 0x974E865B1BB24AF2a9ef8204AdEA9251Cc7C5FD9 |
| E3RefundManager | 0x1940eF168f4E0B3dA24BEca539856684793B0F6e |
| InterfoldTicketToken | 0xC0B5b49a3949eC4B520eF21BaCFE16e3695F3B5D |
| FOLD | 0xE172e9B6cfBeeB5593bDcE3f077356FDb33af904 |
| USDS | 0xdC035D45d973E3EC169d2276DDab16f1e407384F |
| sUSDS | 0xa3931d71877C0E7a3148CB7Eb4463524FEc27fbD |
What each core contract does
- Interfold: coordinates E3 requests and lifecycle.
- CiphernodeRegistry: tracks operators and committee formation.
- BondingRegistry: manages FOLD bonds, ticket collateral, registration, and exits.
- SlashingManager: handles slash proposals, appeals, penalties, and bans.
- E3RefundManager: allocates failure-path refunds and compensation.
Mainnet E3 requests may be paused during operator onboarding while bonding, registration, and ticket deposits remain available. Check requestsPaused() before assuming request flow is open.
Verify the current deployment in the official operator overview.
Addresses checked against Interfold docs on 3 Sep 2026. These are intentionally labeled volatile operational data.