Every method. One reference.
Search the canonical method catalog by name or purpose. Verified read examples are copyable; method presence and network activation are separate.
Request and response contract
Send JSON-RPC 2.0 over HTTP POST to the selected /rpc endpoint. Include jsonrpc, id, method, and params. Check HTTP status, then inspect error before consuming result.
{
"jsonrpc": "2.0",
"id": 1,
"method": "sigil_getNodeInfo",
"params": {}
}Handle failures as first-class results
Do not replace missing chain state with sample records or interpret a failed query as a zero balance. Preserve enough request context to diagnose errors without logging keys, tokens, or private payloads.
| Item | Details |
|---|---|
| HTTP / timeout | The service could not complete the request. Show an unavailable state and use bounded retry. |
| -32601 | The requested method is not supported by this endpoint/version. |
| -32602 | Parameters are missing or invalid. Check the named fields and types. |
| -32603 | An internal or backing-state failure occurred; retain the error message. |
Make your first Sigil request.
Identify a node, check network activation, and read a block window. These requests query public state and do not submit transactions.
Use the right client for the job.
Start with JSON-RPC for reads. Use the Rust SDK for typed configuration, transaction construction, identity resolution, and dedicated protocol helpers.