Sigil documentation
ReferenceJSON-RPC

sigil_searchUsername

Search usernames by ASCII prefix, with limit.

Method

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

Search usernames by ASCII prefix, with limit.

Request binding

Source handler: rpc_username::handle_search_username in sigil/node/sigil-node/src/rpc_username.rs, line 110.

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

    let prefix = match extract_string_param(&req.params, 0, "prefix") {
        Some(p) => p,
        None => return RpcResponse::error(req.id.clone(), -32602, "missing 'prefix' parameter"),
    };

        .or_else(|| req.params.get(1).and_then(|v| v.as_u64()))
        .unwrap_or(DEFAULT_SEARCH_LIMIT as u64) as usize;

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