Skip to main content

​
Qualify historical RPC workloads

On September 20, 2026, Lasso checked what its managed providers answer for historical reads on Ethereum, Optimism, Unichain, Polygon, World, Base and Arbitrum, at 1, 7, 30 and 365 days back, by block number and block hash. Every result was compared with a known value. Use these results to choose a pool, then qualify your own queries before you move an indexer or backfill.

​
Results

Each fraction counts the chain, age and selector combinations that returned the known value. Premium answered every one.
  • Premium served historical state, receipts and logs at every age tested. Through Lasso’s own URL, it answered 54 of 56 historical calls; two Arbitrum calls returned errors on that date.
  • Public served receipts, logs and balances at every age, and most historical state. Public Arbitrum didn’t serve historical state on that date. Use premium or your own archive provider for state reads older than a day.
  • Tempo and Robinhood were checked at 1, 7 and 30 days, since their history is shorter than a year. BSC and testnets weren’t part of this check.
The dated results and method include every chain, age and selector.

​
Qualify your application

  1. Collect known answers from your own contracts: state values at old blocks, block hashes, and receipts and logs you’ve already indexed.
  2. Run them through your exact Lasso URL, with both block-number and block-hash selectors if your client uses both. An empty result doesn’t count as a pass.
  3. Check lasso_meta on any failure to see which provider answered (see routing evidence).
  4. Repeat from your deployment regions at your real request volume.

​
Next