Sigil documentation

Networks

Sigil runs three network classes: production mainnet, Evolve canary, and a public developer testnet. All network labels, RPC URLs, and currencies are explicit.

Network table

Use the chain ID and currency from the selected network. Clients must not reuse balances, faucet flows, or signing previews across networks.

ItemDetails
Evolve Canaryevolve-canary-1 / BITS / https://sigil-velocity-canary-root-1.fly.dev/rpc
Sigil Mainnetsigil-mainnet-1 / MINT / https://rpc.sigil.ml/rpc
Sigil Velocity Testnetsigil-velocity-testnet-1 / SIG / https://sigil-velocity-root-1.fly.dev/rpc

Activation states

The network activation gate evaluates validator and stake requirements against current configuration. Render the exact phase and requirements returned by the selected endpoint. Configured targets, active validator counts, and independently verified operator distribution are separate facts.

Explorer and wallet clients should call sigil_getNetworkActivationStatus and render the exact phase returned by the selected network.

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_getNetworkActivationStatus","params":{}}'

Configuration and availability

These endpoints and currency labels come from the shared client network registry. A configured endpoint is not a live availability claim. Compare sigil_getNodeInfo result.chain_id with the expected value, and display request failures explicitly.

Wallet signing previews must bind the same network identity, currency, nonce, and authority used by the transaction. Never reuse a mainnet balance or signer context as a testnet context.

On this page