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 asLASSO_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
ethers v6
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; aneth_blockNumber response does not
qualify those workloads.