Sigil documentation
ReferenceJSON-RPC

sigil_getProposal

Fetch a governance proposal by ID.

Method

sigil_getProposal 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 a governance proposal by ID.

Request binding

Source handler: rpc_server::handle_get_proposal in sigil/node/sigil-node/src/rpc_server.rs, line 2072.

The handler directly reads these named fields: id, proposal_id. 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.

        .or_else(|| req.params.get("proposal_id"))
        .or_else(|| req.params.get(0));

        .or_else(|| req.params.get(0));

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.

On this page