Block delivery depends on healthy peers, correct network configuration, sufficient hardware, and a node that can keep up with consensus and execution.

Operator checks

AreaWhat to monitor
Peer connectivityPeer count, peer churn, failed dials, and seed availability
Block lagLocal height compared to trusted public RPC or explorer height
Execution healthRepeated execution, mempool, or application errors in logs
Resource pressureCPU, memory, disk I/O, and storage capacity
Network exposureP2P, RPC, and WebSocket ports exposed only as intended

Peer sources

deploy.sh reads seeds, persistent peers, state-sync RPCs, and snapshot peer hosts from https://resources.c8ntinuum.io/peers.json, selected by chain ID. For deployment scripts and peer-list details, see Deployment Scripts. For install and state-sync workflows, see Full Node Installation and State Sync. P2P normally uses port 26656. If the node is behind NAT or a load balancer, set external_address = "<public-ip-or-host>:26656" in the [p2p] section.