Operate with evidence.
Confirm identity, configuration, synchronization, and activation before making a node part of an operational workflow.
Check the network before you write
Read the node identity and compare chain_id with the network you selected. Then read activation status. An endpoint responding successfully does not establish that every feature is enabled, that a transaction will be accepted, or that the node is synchronized.
curl --fail-with-body --show-error --silent --max-time 15 'https://rpc.sigil.ml/rpc' \
-H 'content-type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"sigil_getNetworkActivationStatus","params":{}}'Inspect synchronization and peers
Read sync status and peer state from the intended endpoint. Preserve chain ID, software version, observed height, timestamps, and errors in your incident evidence.
curl --fail-with-body --show-error --silent --max-time 15 'https://rpc.sigil.ml/rpc' \
-H 'content-type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"sigil_getSyncStatus","params":{}}'Keep custody and operations distinct
A validator requires the right lineage, staking and registry policy, software configuration, and key custody. Independent operator and distribution evidence is separate from a node being online or producing blocks.