sigil_getNftEvents
List NFT lifecycle events with optional filters.
Method
sigil_getNftEvents 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.
List NFT lifecycle events with optional filters.
Request binding
Source handler: rpc_nft::handle_get_nft_events in sigil/node/sigil-node/src/rpc_nft.rs, line 222.
The handler uses no directly named params.get fields, or delegates input parsing to a typed helper. Use the request types below rather than assuming an empty parameter object.
Parsing excerpt
These source excerpts show binding and validation; they are not runnable client code.
let filter: NftEventFilter = if req.params.is_null() || req.params == serde_json::Value::Null {
NftEventFilter::default()
} else {
match serde_json::from_value(req.params.clone()) {
Ok(f) => f,
Err(e) => {
return RpcResponse::error(
req.id.clone(),
-32602,
format!("invalid filter params: {e}"),
)
}
match serde_json::from_value(req.params.clone()) {
Ok(f) => f,
Err(e) => {
return RpcResponse::error(
req.id.clone(),
-32602,
format!("invalid filter params: {e}"),
)
}
}
};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.