Skip to main content
Lasso RPC Core is an Elixir/Phoenix application. Clients use HTTP JSON-RPC or WebSocket endpoints; the dashboard reports provider and request observations.

​
Request path

A request resolves its profile and chain, applies transport and method policy, filters eligible providers, and selects an upstream using the requested strategy. Execution safety and a request deadline bound further attempts. A supported method is still subject to the selected provider’s plan, parameters, history, and current capacity. Signed transaction submission receives one upstream dispatch. A lost response can be indeterminate; clients reconcile the transaction hash. See Supported methods.

​
Runtime ownership

Profiles own routing configuration and client subscription scopes. Identical upstreams can share physical HTTP/WebSocket resources, health observations, and circuit breakers. Shared runtime reduces duplicated work; it does not create quota isolation. See Profiles and reload. Subscriptions are multiplexed for matching streams and use bounded recovery. Ordinary RPC requests do not require an upstream subscription. See WebSocket endpoints.

​
Multiple nodes

Each node routes from local upstream measurements. Clustering aggregates observability; it does not forward client RPC requests between nodes. Configure a load balancer to reach the desired Lasso region. Each node needs its own matching profile files and reload. See Clustering.

​
Product boundary

RPC Core does not provide Cloud accounts, billing, API-key authentication, or incoming customer quotas. Protect all externally exposed endpoints through your deployment boundary. Lasso Cloud provides the managed product.