How-to guide

Verify active operator status

Separate three questions: is the process running, is the onchain position active, and is the network currently accepting E3 requests?

1. Check the local process

interfold nodes ps

interfold nodes logs cn1

Replace cn1 with the configured node name. This verifies software state only.

2. Read the onchain position

interfold ciphernode status --chain mainnet

An eligible position should report the expected operator and bond-owner addresses, Registered: true, Active: true, Exit pending: false, sufficient bond, and at least the minimum available tickets.

3. Diagnose a failed check

Signal	Meaning	Next action
`Registered: false`	The operator is not in the ciphernode registry.	Register from the authorized bond-owner configuration.
`Active: false + low tickets`	The ticket balance is below the current minimum.	Add ticket collateral, then read status again.
`Active: false + low bond`	The bond is below the active-maintenance floor.	Top up FOLD from the bond owner.
`Exit pending: true`	A deregistration or collateral exit is in progress.	Inspect pending exits and wait for the configured delay before re-registering.
`Requirements changed`	Cached eligibility may be stale after governance changes.	Use the dashboard or call BondingRegistry.refreshOperatorStatus; the CLI currently has no command for it.

4. Check request availability separately

Active: true means the operator meets registry eligibility requirements. It does not prove that new E3 requests are currently enabled. During onboarding, mainnet requests can remain paused while operators bond, register, and add tickets; check requestsPaused() or the current dashboard before assuming live workload flow.

Checked 3 Sep 2026. Sources: Ciphernode Operators and Registration & Bonding.