sigil_getTransactionReceipt

Method

sigil_getTransactionReceipt is registered in the canonical JSON-RPC catalog. Use POST /rpc, Content-Type: application/json, JSON-RPC 2.0 and a caller-controlled request id. Node RPC profile, build feature and runtime activation checks still apply.

Fetch the receipt for a transaction.

Request binding

Source handler: rpc_server::handle_get_transaction_receipt in sigil/node/sigil-node/src/rpc_server.rs, line 2640.

The handler directly reads these named fields: hash. Additional typed parsing, aliases and nested validation are defined by its request types. Field presence alone does not establish optionality.

Parsing excerpt

These source excerpts show binding and validation; they are not runnable client code.

    let hash = match req.params.get("hash").and_then(|v| v.as_str()) {
        Some(hash) => hash,
        None => return RpcResponse::error(req.id.clone(), -32602, "missing 'hash' parameter"),
    };

Read example

hash: transaction hash string from the selected network. Returns status, receipt, block height, and transaction index.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "sigil_getTransactionReceipt",
  "params": {
    "hash": "YOUR_TRANSACTION_HASH"
  }
}

Named YOUR_* values must be replaced with identifiers from the selected chain.

Responses and failures

Check HTTP status, parse the JSON-RPC envelope, reject error, and require result on success. Preserve large base-unit integers without floating-point rounding. A catalog method does not bypass authentication, capability, policy or activation requirements.