Clients and state contexts
Create transports and CLIENT values. Pin a client to one block or restore retained execution state.
- attach_transport(CLIENT, 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
- client(TRANSPORT) 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
- client_context(CLIENT) Returns the state identity and hydration status carried by a CLIENT, including its kind, chain, block, chain profile, and identity hash.Scalar
- http_transport(VARCHAR, UBIGINT) 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
- pin(CLIENT, VARCHAR) Resolves a live CLIENT to one exact block and returns a pinned CLIENT for repeatable state reads. Pin by tag, number, hash, or a matching number/hash pair, with optional canonicality enforcement. Identical normalized requests using the same constructed live-CLIENT wrapper share one resolution within a SQL statement; separate client(transport) constructions resolve independently, and a later statement resolves the selector again.Scalar
- rpc_call(CLIENT, VARCHAR, JSON) Sends a low-level JSON-RPC request and returns the response's result value as JSON. Provider errors and transport failures are raised as SQL errors.Scalar
- transport(VARCHAR, UBIGINT) Builds a TRANSPORT containing type, url, and chain_id without contacting the endpoint. Unlike http_transport, it does not add a config object.Scalar