Skip to main content

Lasso RPC Core

Lasso RPC Core is the open-source routing engine behind Lasso. Run it in front of your nodes and providers, and your apps get one JSON-RPC endpoint per chain over HTTP and WebSocket that picks the best upstream for each request, fails over on retryable errors and shows its work.

What it does

  • Routes by measurement. Health checks and circuit breakers decide which providers are eligible. fastest and balanced-fast then order them by recent latency, per chain, kind of request and transport; load-balanced spreads load across them. A provider route pins one upstream for debugging.
  • Fails over safely. Retries are bounded by the original deadline and by whether a method is safe to repeat.
  • Keeps subscriptions alive. Matching newHeads and logs subscriptions share one upstream stream and move to another provider with missed blocks backfilled.
  • Separates workloads. Profiles give each app or environment its own provider pool and routing settings, sharing upstream connections where the URL and credentials match.
  • Shows its work. Opt-in request metadata names the provider, latency and retries behind each response. A live dashboard, Prometheus metrics and OpenTelemetry traces cover the rest. Regional nodes route from their own measurements and can cluster for a combined view.
These docs describe RPC Core v0.7.0. For a hosted endpoint with keys, billing and managed providers, use Lasso Cloud.

Get started

Start the container and route your first request, then configure your own providers. Core has no built-in client authentication, so put exposed RPC, metrics and dashboard endpoints behind your network or reverse proxy; the production checklist covers it.