Sigil documentation
ReferenceJSON-RPC

sigil_getComputeAuditTrail

Fetch compute audit events.

Method

sigil_getComputeAuditTrail 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 compute audit events.

Request binding

Source handler: rpc_compute::handle_get_compute_audit_trail in sigil/node/sigil-node/src/rpc_compute.rs, line 404.

The handler directly reads these named fields: after_seq, aggregate, limit. 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.

        after_seq: req.params.get("after_seq").and_then(Value::as_u64),
        limit: req
            .params
            .get("limit")
            .and_then(Value::as_u64)
            .map(|n| n.min(u32::MAX as u64) as u32),
    };

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