Reference
Operator lifecycle
Use this state map when software is running but the operator is not behaving as expected onchain.
- UnbondedNo ciphernode bond; cannot register.
- BondedFull FOLD position established, but not registered.
- RegisteredIn the registry, but not yet ticket-eligible.
- ActiveEligible to participate in committee sortition.
InactiveRegistered, but below current bond or ticket requirements.
ExitPendingDeregistered; collateral remains queued until the exit delay passes.
Slashing eventMay penalize collateral, affect committee duty, deactivate, or ban.
| State | Protocol meaning |
|---|---|
| Unbonded | No ciphernode bond deposited; registration is unavailable. |
| Bonded | FOLD is deposited, but the operator is not registered. |
| Registered | The operator is in the registry but does not meet every active requirement. |
| Active | Registered, sufficiently bonded and ticket-funded, and eligible for sortition. |
| Inactive | Still registered, but below a current bond or ticket requirement. |
| ExitPending | Deregistration was requested; collateral is waiting through the exit delay. |
Slashing intersects the lifecycle
Slashed is not a registry state in the official lifecycle table. A slash policy can burn tickets, confiscate bond, remove a node from committee duty, ban it, or reduce its collateral enough to make it inactive.
Appeal behavior is also policy-specific. A zero-second appeal window means immediate execution, so operators should monitor SlashProposed rather than assuming every penalty includes time to respond.
State-changing actions
| Action | Likely transition |
|---|---|
| Bond the full required FOLD | Unbonded → Bonded |
| Register the operator | Bonded → Registered |
| Meet ticket and bond minimums | Registered or Inactive → Active |
| Fall below an eligibility minimum | Active → Inactive |
| Deregister | Registered or Active → ExitPending |
Checked 3 Sep 2026. Sources: Ciphernode Operators and Exits, Rewards & Slashing.