Sigil documentation
Operator runbooks

Consensus Halt

Collect evidence, follow the approved recovery path, and verify the result when investigating consensus halt.

Immediate procedure

  1. Check sigil_getNetworkActivationStatus on all public RPC endpoints.

  2. Compare ready validator roles and stake with the approved topology and current activation requirements before changing deployment state.

  3. Inspect validator logs for genesis hash mismatch, liveness probe restart loops, and peer connectivity.

Capture network evidence

Record the endpoint, returned chain ID, node version, timestamps, current height, and observed error. Compare the affected node with healthy nodes on the same chain; retain logs and signed evidence before making changes.

curl --fail-with-body --show-error --silent --max-time 15 'https://sigil-velocity-canary-root-1.fly.dev/rpc' \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"sigil_getNodeInfo","params":{}}'

Verify recovery

Repeat the original failing check. Confirm expected synchronization and activation state, and compare the relevant block hashes or state roots at the same height. Record the recovery action, evidence, and remaining uncertainty in the incident record.

curl --fail-with-body --show-error --silent --max-time 15 'https://sigil-velocity-canary-root-1.fly.dev/rpc' \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"sigil_getSyncStatus","params":{}}'

On this page