Clients and state contexts
Reference functions grouped under Clients and state contexts, with signatures, examples, and metadata generated from the Determica catalog.
- 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
- 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
- client_context Returns the state identity and hydration status carried by a CLIENT, including its kind, chain, block, chain profile, and identity hash.Scalar
- 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
- pin 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 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 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