A contract shipped without the event you needed. The data is all in the chain history, but the log was never emitted, so nothing indexes it.
The usual fix is to re-execute the range yourself and rebuild the state by hand.
Erigon's overlay namespace does it as a query instead.
Empowering industries with trustless, decentralized software innovations.
dsc.gg/erigon
- 📢Erigon v3.5.5 released! Security + bugfix release. Recommended for all users. Block proposers: Fulu blinded-block panic fixed Archive operators: logIndex regression fixed (v3.5.1–v3.5.4) External CL users: payload timing fix Plus 4 security bumps. Drop-in from v3.5.4, no
- Erigon pulls historical data over BitTorrent, not the Ethereum p2p network. The reason is incentives: nobody is paid to serve old blocks, so peers for that data are scarce and unreliable. Snapshots are immutable files, content-addressed, perfect for a distribution protocol. Two
- At institutional size, a public mempool turns intent into signal. That is where slippage, frontrunning, and copy trading start. Cocoon keeps the order book on operator infrastructure, so the trade never hits a shared mempool. ZK proofs still let regulators verify totals and
- Running RPC infra? Two things worth knowing: - Erigon serves RPC from a separate daemon process, so you can scale the query layer independently of the node following the chain, or run it remotely. - Every release since 3.1 has focused on performance and stability at chain tip:Replying to @lavanetxyz and @ErigonEththat makes total sense, it’s all about redundancy.


