Skip to main content
Lasso exposes standard EVM JSON-RPC. Start with one server-side read path in your Base application and replace its RPC URL with a Lasso endpoint. Keep your client library and application contract calls.

Prepare the endpoint

Check live managed chains for Base before choosing a managed profile. If you have existing Base provider URLs, configure a custom provider pool instead. Use the quickstart or the available agent workflow to obtain an endpoint. Store the complete endpoint as LASSO_RPC_URL in your existing server-side secret manager. Keep the previous RPC URL for rollback. An endpoint containing a key is a credential; exposing it in a browser bundle lets visitors use its access and quota.

viem

See the viem public client reference for client options. Configure application timeouts and retries around the operations you actually perform; transaction submission has different recovery needs from a read.

ethers v6

This evaluation sends individual requests and uses polling rather than provider-local HTTP filters. Lasso rejects those filters. Once the flow works, choose batching within the live Lasso and upstream limits. The ethers JSON-RPC provider reference describes these options.

Verify the application flow

Run a representative read with the same block selector against both endpoints. For related state values, select one block hash so head movement does not masquerade as a routing discrepancy. Record latency, error rate and routing evidence without logging credentials. Move one request flow first. If its behavior fails your acceptance criteria, restore the previous URL. Test transaction sending, historical ranges and WebSocket subscriptions separately; an eth_blockNumber response does not qualify those workloads.