If you’re choosing how to index data for a smart-contract application, start with the contract’s events. In a November 4, 2026 explanation of The Graph’s subgraphs on EVM chains, event handlers were identified as the primary and most reliable approach. They can also access transaction and block metadata associated with an event.
When events do not provide enough information, the options have different limits:
- Contract state: A mapping can use
eth_callto read state, but the result reflects state at the block level. Historical reads require an archive node that supports EIP-1898. - Contract calls: A call handler can track calls to functions that emit no event. It depends on
trace_filter, which many networks and RPC providers do not offer. - Periodic sampling: A block handler can check state at every block or at a fixed interval.
Querying a subgraph’s historical entities is not the same as reading historical state directly from the chain. IPFS and Arweave file data sources also have isolation limits; they are not a substitute for unrestricted access to on-chain data.
Standard subgraphs do not cover complete execution traces, internal transfers, pending transactions or a chain’s entire transaction history. Those needs may call for debug_traceTransaction, Substreams or a custom indexing pipeline. The practical order is to check events first, then consider state reads and call or block handlers, and turn to tracing or chain-wide indexing only when those approaches cannot supply the required data.