Skip to Content
OperateOperations Playbook

Validator Operations Playbook

This runbook collects the key operational tasks for maintaining a production Sei validator, with emphasis on the latest mempool and consensus changes (sei-tendermint@02c9462f1).

Daily Checklist

Block productionVerify seid status | jq .SyncInfo.catching_up returns false and height increases steadily.
Mempool saturationMonitor mempool/size and mempool/cache_size metrics; ensure they are below configured maxima.
Validator signingCheck consensus/validators_signed > 0 in the last 100 blocks.
Oracle participationIf applicable, verify oracle votes landed within the window.

Configuration Highlights

mempool.cache_sizeDefault 10000. With sei-tendermint@02c9462f1, the cache cap is enforced precisely—raise gradually (e.g., 20000) if your validator absorbs heavy flow.
mempool.broadcastLeave enabled to propagate transactions quickly through your sentry layer. Disable only when debugging local replay loops.
consensus.create_empty_blocksKeep set to true to preserve liveness under low traffic. Disabling requires carefully monitored maintenance windows.
p2p.laddr + persistent_peersEnsure sentry peers stay pinned; update lists after rotations to avoid accidental isolation and downtime penalties.

Monitoring Metrics

consensus_height / consensus_roundDetect consensus stalls or proposer rotation issues. Alert on flatlining height for > 2 minutes.
consensus_validator_powerMonitor stake adjustments and make sure jailed status is cleared after unjails.
mempool_size / mempool_cache_sizeAlert when size approaches cache cap; combine with duplicate-tx warnings from Tendermint logs.
rpc_trace_pendingTrack tracer load if the validator exposes RPC to trusted partners; ensure the value stays under max_concurrent_trace_calls.

Slashing Guardrails

Penalty windows on Sei follow the Cosmos 5% missed-signing threshold. Keep the following checks in your daily workflow to avoid downtime or double-sign slashing.
Missed blocksRun seid q slashing signing-info <consensus_pubkey> and alert when missed_blocks_counter increases faster than expected.
Double-sign watchdogConfirm sentry nodes run duplicate vote detection or host a light client to halt on conflicting signatures.
Key custodyKeep HSM or KMS access logs; disable fallback keys once rotations finish to prevent unintended parallel signing.

Incident Response

⚠️
Always snapshot your validator before modifying configuration or restarting under duress.
  1. Consensus halt

    • Confirm majority of validators are on the same binary.
    • Check logs for nil vote extension or duplicate tx warnings.
    • Coordinate restart if required; use state sync if node falls far behind.
  2. Mempool overflow

    • Increase mempool.cache_size gradually (requires sei-tendermint@02c9462f1).
    • Prune invalid transactions by restarting with --mempool.recheck=true temporarily.
  3. RPC saturation

    • Scale out dedicated RPC nodes; validator should keep RPC closed to the public when possible.

Troubleshooting

ErrorCauseFix
Duplicate transaction rejected repeatedlyCache size too small for workload.Increase mempool.cache_size and restart during low traffic.
Validator missed blocksNode lagging or signing key offline.Check hardware load, ensure sentry nodes are reachable, and restart if necessary.
Vote extension warnings in logsExperimental flag toggled vote extensions.Revert configuration; once enabled, the protocol expects extensions.
Last updated on