What Can a The Graph Subgraph Index on an EVM Chain?

When building a subgraph, start with the contract events you need to query. As a guide published on November 4, 2026, at 10:37 a.m. UTC+8 explains, event handlers are the primary and most reliable way to index those events, along with transaction and block metadata.

If events do not provide enough information, the guide describes several other options:

  • Read contract state: A mapping can use eth_call, but the result reflects state at the block level. Historical reads require an archive node that supports EIP-1898.
  • Handle contract calls: A call handler can track calls to contract functions that emit no event. It depends on trace_filter, which many networks and RPC providers do not offer.
  • Sample state by block: A block handler can poll state on every block or at a fixed interval.

These options do not turn a standard subgraph into a complete chain index. Full execution traces, internal transfers, pending transactions and chain-wide transaction history are outside its standard capabilities. The guide points to debug_traceTransaction, Substreams or a custom indexing pipeline when those requirements arise. It also distinguishes querying historical subgraph entities from reading historical on-chain state, and notes isolation limits for IPFS and Arweave file data sources.

The practical order is to check events first, then consider state reads or call and block handlers, and only then evaluate tracing or chain-wide indexing.