JSON-RPC
Sigil public clients use canonical JSON-RPC method names checked into the shared client contract.
Canonical call shape
Every public endpoint accepts JSON-RPC 2.0 over HTTP POST at /rpc. Unsupported or unsafe state should fail closed instead of returning mock data.
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_getNodeInfo","params":{}}'Core methods
These are the first methods clients should use when bootstrapping a network session.
| Item | Details |
|---|---|
| sigil_getNodeInfo | chain_id, version, and protocol_version. Use dedicated methods for other state. |
| sigil_getNetworkActivationStatus | Boot/stake/active/stabilized activation gate. |
| sigil_getLatestBlock | A blocks array with latest_height and count; use count: 1 for one record. |
| sigil_getValidatorSet | Active validator records. |
| sigil_getBalance | Base-unit account balance. |
| sigil_sendTransaction | Submit a signed transaction. |
Full method reference
The searchable method catalog groups the interface by namespace and provides verified read-only parameter examples. HTTP success and JSON-RPC success are separate checks.
System Contracts
Sigil uses WASM system contracts as the policy gate for core chain features while preserving deterministic native execution for state mutation.
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.