eth_getLogs Limits Across Chains, Measured
Twenty chains measured on 2026-10-11: the widest eth_getLogs block span that succeeded on each, and why every figure is a floor rather than a cap.
Read →4 posts.
Twenty chains measured on 2026-10-11: the widest eth_getLogs block span that succeeded on each, and why every figure is a floor rather than a cap.
Read →There is no single eth_getLogs limit per chain. Two caps, block span and result count, and five different error shapes decide whether a query succeeds.
Read →Story's IP Assets, licenses, and derivative trees are ordinary contract state on an EVM chain. A hands-on guide to indexing the IP graph with eth_getLogs, eth_call, and a WebSocket.
Read →You can fetch logs with eth_getLogs and eth_subscribe — but the raw log is address + topics + data, not a readable event. This tutorial explains how logs are encoded (topic0 = the event signature hash, indexed params in topics, the rest in data), how to decode them in viem/ethers/web3.py, and the traps: indexed dynamic types, address padding, and anonymous events.
Read →