Reference
Operator requirements
Current values for quick lookup. Protocol parameters can change; verify them against the live dashboard and contracts before committing capital.
| Requirement | Current documented value |
|---|---|
| FOLD bond | 32,000 FOLD on mainnet |
| Ticket collateral | 1,000 sUSDS shares per available ticket on mainnet |
| Gas | ETH on the target network |
| CPU | 8+ cores |
| Memory | 32GB+ DDR5 |
| Storage | 500GB+ NVMe SSD |
| OS | Linux or macOS |
| Network | Stable connection with open UDP port |
| Ethereum access | WebSocket RPC endpoint |
Operational distinction
isCiphernodeBonded and “can register” are not identical checks. The protocol can consider a node bonded at the active-maintenance floor while still requiring the full configured bond for a new registration. Use the current required bond when testing registration readiness.
Operating margin
The official operator guidance recommends keeping 10–20% above the minimum bond and maintaining extra tickets. A slash or ticket removal can otherwise push a just-at-minimum position directly into Inactive.
Verify the current requirements in the official operator overview.
Checked 3 Sep 2026 against Interfold operator documentation.