Sigil documentation
ReferenceJSON-RPC

sigil_verifyArtifact

Verify bytes against a Weave/Sigil artifact commitment.

Method

sigil_verifyArtifact 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.

Verify bytes against a Weave/Sigil artifact commitment.

Request binding

Source handler: rpc_server::handle_verify_artifact in sigil/node/sigil-node/src/rpc_server.rs, line 971.

The handler directly reads these named fields: bytes_hex, commitment, payload_hex. 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 commitment_value = match req.params.get("commitment").cloned() {
        Some(value) => value,
        None => {
            return RpcResponse::error(req.id.clone(), -32602, "missing 'commitment' parameter")
        }
    };

        .or_else(|| req.params.get("payload_hex"))
        .and_then(|v| v.as_str())
    {
        Some(value) => value.strip_prefix("0x").unwrap_or(value),
        None => return RpcResponse::error(req.id.clone(), -32602, "missing 'bytes_hex' parameter"),
    };

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