aztec-rpc

JSON-RPC HTTP transport shared by the node client (and internally by other clients that speak HTTP JSON-RPC).

Source: crates/rpc/src/.

Public Surface

One module: rpc, re-exported at the crate root.

RpcTransport

pub struct RpcTransport { /* private */ }

impl RpcTransport {
    pub fn new(url: String, timeout: Duration) -> Self;
    pub fn url(&self) -> &str;
    pub fn timeout(&self) -> Duration;

    pub async fn call<T: DeserializeOwned>(
        &self, method: &str, params: serde_json::Value,
    ) -> Result<T, Error>;

    pub async fn call_optional<T: DeserializeOwned>(
        &self, method: &str, params: serde_json::Value,
    ) -> Result<Option<T>, Error>;

    pub async fn call_void(
        &self, method: &str, params: serde_json::Value,
    ) -> Result<(), Error>;
}

• call — deserializes the result into T.
• call_optional — returns Ok(None) when the server returns null.
• call_void — discards the result; used for notifications.

All three produce aztec_core::Error on transport, JSON, or RPC-level failure.

Error Handling

The crate re-exports aztec_core::Error. See Errors for the unified error taxonomy.

Typical Use

RpcTransport is used internally by aztec-node-client and aztec-ethereum. Direct use is rare; prefer the typed clients.

Full API

Bundled rustdoc: api/aztec_rpc/. Local regeneration:

cargo doc -p aztec-rpc --open