TRANSPORT
JSON configuration for an HTTP or HTTPS JSON-RPC client. It contains type, url, and chain_id, plus an optional config object. The caller supplies chain_id; constructing a TRANSPORT does not call eth_chainId or verify the endpoint.
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
Builds a TRANSPORT for an HTTP or HTTPS JSON-RPC endpoint. It records the endpoint, declared chain id, and request policy without contacting the provider.
scalar function Offline 3 overloads - transport
Builds a TRANSPORT containing type, url, and chain_id without contacting the endpoint. Unlike http_transport, it does not add a config object.
scalar function Offline 2 overloads