Skip to main content
Lasso Cloud · For application and infrastructure teams. Put configured EVM providers behind one standard JSON-RPC endpoint. Lasso selects an eligible upstream for each request and can fail over when replay is safe for that work.

​
What happens to a read

Lasso first filters providers by chain, method, transport, configured limits, and known health. The requested strategy orders the eligible providers. A replay-safe read can use another upstream when execution safety, dispatch certainty, failure cause, remaining deadline, and live availability permit. The entire attempt sequence stays within one request deadline and work budget. For a trial, use a method your app already calls, such as eth_blockNumber or an ordinary contract read. Run it through the old endpoint and Lasso under the same workload. Compare correctness, error rate, latency, head freshness, and which upstream served the response. Two configured URLs may share a vendor, quota, or underlying infrastructure, so test the failure you need to survive.

​
See the provider that served the request

The dashboard shows provider state and recent activity. For an individual HTTP request, opt into routing metadata with ?include_meta=body. In the following illustrative excerpt, the optional executed_channel identifies the upstream that served a successful response:
Keep the raw JSON-RPC envelope when inspecting lasso_meta; an SDK may return only result. Managed routes can withhold provider fields, and some outcomes have no executing upstream. Record absent attribution as unknown. The routing evidence guide explains header mode, optional fields, and request ID correlation.

​
Treat writes and streams separately

Lasso sends eth_sendRawTransaction to one selected upstream and does not automatically retry or fan out after dispatch. If the response is lost, your application reconciles by transaction hash and owns nonce, replacement, receipt, and finality handling. Provider-local HTTP filter IDs cannot move between upstreams; use eth_getLogs or a supported WebSocket subscription. See the workload behavior guide for the full method contract. For a surviving downstream WebSocket connection, Lasso can replace a provider and reconcile a bounded replay window within one profile. A controlled 30-minute newHeads test with 50 clients and 119 forced replacements recorded zero gaps or replay-created duplicates. That result covers the tested window; clients still need checkpoints and recovery after disconnection. Read the WebSocket continuity evidence and subscription recovery limits.

​
Try one application path

Start with your existing providers or a managed profile. Keep the previous RPC URL available while you test. The routing guide describes strategy and health behavior, while versions and evidence separates released Lasso RPC Core from the managed deployment.