TRANSPORT
Typed JSON transport configuration consumed by RPC helpers. It carries endpoint, chain_id, and optional HTTP policy; it is not an RPC response. chain_id is trusted caller metadata and is never discovered implicitly. Prefer explicit chain_id and pinned block options for reproducible reads.
Used by functions
Derived from generated function parameters and return types.
Accepted as input
- attach_transport
Attaches transport authority to a pinned or execution CLIENT so missing state can be fetched without changing the CLIENT's durable state identity.
scalar function Live RPC RPC 1 overload - client
Creates a live CLIENT from a TRANSPORT or restores retained execution state by execution ID. An optional expected chain ID rejects state from another chain.
scalar function Live RPC RPC 2 overloads
Returned as output
- http_transport
Creates an HTTP TRANSPORT from an endpoint and optional chain ID. The JSON-config overload adds timeouts, retries, throttling, concurrency, TLS verification, and get_logs page-size controls.
scalar function Offline 3 overloads - transport
Creates a lightweight TRANSPORT from an RPC endpoint and optional chain ID. Use http_transport when you need timeouts, retries, throttling, TLS settings, or log-pagination controls.
scalar function Offline 2 overloads