Validators
Validator operation requires the selected network configuration, identity and stake policy, custody, synchronization, and activation checks. Read the current set instead of assuming a fixed validator count.
Activation gate
Query sigil_getValidatorSet and sigil_getNetworkActivationStatus for current validator records and activation requirements. Preserve the endpoint, chain ID, software version, and observation time alongside your results.
The network can be active before it is fully decentralized. Public decentralized labeling is separate from block production and requires the independent operator roster, stake distribution, provider distribution, ASN distribution, region distribution, and attestation URL checks to pass.
Operator flow
Use the approved network-specific onboarding procedure to establish root lineage, bind the validator DID, configure custody, and meet staking and registry policy. Generic identity lifecycle commands are not interchangeable with the supported typed paths.
Operators should keep infrastructure configuration, key custody, operator records, and distribution evidence current. Complete synchronization and activation checks before serving a node as an operational dependency.
Read the current validator set
The response includes validators and count. Preserve the response as observed; do not fill an unavailable set with sample operators.
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_getValidatorSet","params":{}}'