Web3 New Added 19 September 2026

Web3: query returned more than 10000 results (eth_getLogs)

The RPC provider caps how much a single log query may return or how many blocks it may span, and the limit is per provider rather than part of the JSON-RPC spec. The same code works against a local node and fails on a hosted endpoint, usually at the point where an indexer starts from the contract deployment block.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

// Page the range rather than asking for all of history at once
const STEP = 2000n;               // stay under the provider block span limit
for (let from = startBlock; from <= head; from += STEP) {
  const to = from + STEP - 1n > head ? head : from + STEP - 1n;
  const logs = await provider.getLogs({ address, topics, fromBlock: from, toBlock: to });
  await handle(logs);
}

// Narrow the filter before widening the range: an indexed topic costs nothing
const topics = [id("Transfer(address,address,uint256)"), null, pad(recipient)];

// Halve the window when the provider complains, rather than failing the job
try { await provider.getLogs(f); }
catch (e) { if (/more than|range/i.test(e.message)) return split(f); throw e; }

# Check the published limits before tuning the constant, they differ by plan
# and a pruned node returns an empty result rather than an error for old blocks

How to diagnose Web3 errors

Web3 errors are unusually terse because the EVM reports failure without explanation by default. execution reverted means a require or revert triggered. The reason string is present in the return data but most libraries discard it. Nonce errors reflect the strict sequential ordering of transactions per account, so a stuck transaction blocks every one behind it.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Simulate before sending: eth_call against the same block returns the revert reason string that a submitted transaction hides.
Use a transaction tracer (Tenderly, Foundry's cast run, or a node's debug_traceTransaction) to see the exact opcode and contract where execution reverted.
For nonce errors, query the account's pending nonce (eth_getTransactionCount with the pending tag) rather than tracking it locally.
To replace a stuck transaction, resend with the same nonce and a materially higher gas price: most nodes require at least a 10% increase.
Check the chain ID matches the network you intend. Signing for the wrong chain produces confusing rejection messages.

Tools worth reaching for

cast (Foundry)
eth_call simulation
Tenderly / block explorer tracer
debug_traceTransaction

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

ethereum.org docs.ethers.org

Related Web3 errors

See all 10 Web3 errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.