Skip to main content

This site is for educational purposes only. Nothing here constitutes financial advice.

Topic 107 of 189

Indexers and The Graph

How blockchain indexers turn raw chain data into fast, queryable APIs — The Graph's subgraphs, competing indexers, why every dApp uses one, and how the indexing layer shapes what applications can build.

Beginner
8 min readUpdated November 2026Block Clarity Hub Editorial Team

The basics

Why Blockchains Need Indexers

Blockchains store transaction data in a form optimised for consensus and verification, not for querying. If you want to know 'how many NFTs did address X buy last week', 'what's the total volume on Uniswap yesterday', or 'which addresses hold token Y', you cannot get that from an RPC node in any reasonable amount of time. You need an indexer — a piece of infrastructure that reads every block, extracts the events and state changes you care about, and stores them in a queryable database. Almost every non-trivial dApp uses an indexer either operated in-house or a third-party service.

The Graph as the Category Leader

The Graph is a long-running, widely used blockchain indexing protocol (its Foundation calls it 'the industry's leading protocol for blockchain data infrastructure'). It introduced the idea of a 'subgraph' — a small, declarative description of what data to index for a specific dApp, written by the dApp team and deployed to The Graph's indexer network. Once deployed, anyone can query that subgraph via GraphQL. Uniswap, Aave, Curve, Synthetix, and thousands of other protocols have subgraphs — often the same subgraph is used by the protocol's official interface and by dozens of third-party analytics tools.

Indexers Beyond The Graph

The Graph is not the only indexing option. Dune Analytics indexes chain data into SQL tables that anyone can query. Nansen, Arkham, and Chainalysis run proprietary indexers for their specific use cases. dApps that need lower latency or specific data shapes often build their own with tools like Ponder, Envio, or SQD (formerly Subsquid). Big blockchains (Solana, Aptos, Sui) each have their own indexing ecosystems adapted to their specific data models. The category has fragmented as the industry has grown.

  • Indexers translate raw chain data into queryable APIs
  • Every non-trivial dApp uses one — in-house or a service
  • The Graph is a general-purpose, decentralised indexing network
  • Dune, Nansen, and various proprietary indexers serve different niches

Key Takeaways

  • Blockchains store data for consensus, not for queries — indexers bridge the gap
  • Subgraphs are declarative descriptions of what to index for a specific dApp
  • The dApp UI you use is almost always reading from an indexer, not a chain directly
  • The category has fragmented — no single indexer covers all use cases well

Going deeper

How a Subgraph Works

A subgraph is defined by three files: a GraphQL schema describing the entities you want to query, a manifest mapping specific smart-contract events and state changes to indexing operations, and TypeScript-like AssemblyScript code that runs each time a mapped event fires and writes to the entity store. Indexers running The Graph's node software sync from chain genesis (or a chosen start block), replay every relevant event through your mapping code, and expose a GraphQL endpoint. Once synced, queries are fast.

The Graph's Two Modes

The Graph has had two modes. The hosted service was the original — a centralised service. It has been retired: the Sunrise of Decentralized Data ended on 12 June 2024 and hosted-service query endpoints are no longer available. The decentralised network is where independent indexers stake GRT to serve queries and are rewarded with query fees and indexing rewards, with curator signal pointing them to valuable subgraphs. Subgraph Studio's staging environment, served by a centralised Upgrade Indexer, kept carrying some production traffic; per The Graph Foundation, Studio staging queries for BNB Smart Chain and Polygon ended on 8 October 2026 and other chains are expected to follow. If you're building today, publish your subgraph to The Graph Network, set up billing and an API key in Studio, and query it through a Gateway endpoint.

Ponder, Envio, SQD — the Local-First Alternatives

The Graph is designed for shared, decentralised indexing; a lot of teams want the opposite — a local, fast, single-team indexer with easy schema iteration. Ponder (TypeScript), Envio (TypeScript/ReScript), and SQD, formerly Subsquid (TypeScript) fill this space. You write similar declarative-plus-code definitions, but the result is a Postgres database you host yourself. Iteration is much faster (no on-chain deployment), performance is often better, and you have full control. The trade-off is you're now running infrastructure — nobody else can query it, and you carry the operational burden.

'Small Reorgs Break Indexes' Is a Real Thing

Chain reorgs — when a block that was thought to be canonical gets replaced — force indexers to un-apply the events from the orphaned block. Every serious indexer handles this via reorg-aware writes and periodic reconciliation. If you build an in-house indexer that ignores reorgs, you will silently produce wrong data during network stress. Choose tools that make reorg handling explicit, and test them.

Key Takeaways

  • A subgraph = schema + event mappings + AssemblyScript logic
  • The Graph's hosted service has been retired; production traffic is moving from Subgraph Studio staging onto the decentralised network
  • Ponder / Envio / SQD are the local-first alternatives for teams who want control
  • Reorg handling is the invisible correctness problem every indexer must solve

Under the hood

Curation, Signal, and Query Fees

The Graph's decentralised network coordinates indexers, curators, and consumers through GRT-denominated economic flows. Curators signal which subgraphs are worth indexing by depositing GRT; their signal earns a share of future query fees. Indexers stake GRT to serve queries and earn fees plus inflationary rewards; since 2026 a Rewards Eligibility Oracle gives indexing rewards only to Indexers that serve queries. Consumers pay for queries by credit card or in GRT on Arbitrum, with a free tier of 100,000 queries a month. In theory this creates a market that routes indexing effort to valuable subgraphs. In practice, for a long time a large share of developer queries ran through a centralised staging environment that network Indexers never saw, and indexing rewards followed stake and signal rather than quality of service; The Graph Foundation's 2026 changes (moving Studio traffic onto the network, the Rewards Eligibility Oracle) aim to address both.

Substreams — Beyond Subgraphs

Substreams (from StreamingFast, now part of The Graph ecosystem) is a newer indexing primitive designed for parallel and composable data pipelines. Instead of one subgraph indexing one dApp, you compose reusable substream modules — one for token transfers, one for DEX swaps, one for governance events — and downstream consumers combine them. The result is significantly faster indexing (parallel processing) and better reuse. Substreams can also power subgraphs, speeding up indexing for large, complex protocols.

Non-EVM Indexing

Solana's account model is different enough from Ethereum's that Ethereum indexing patterns don't translate directly. Solana teams use Helius, Triton, Shyft, and custom Anchor IDL parsers. Aptos and Sui, with their Move-based object model, need different indexing again — Aptos has an official indexer stack and Sui offers a similar-shaped service. Cosmos chains often use the chain's own indexer combined with data services. Non-EVM indexing is more fragmented and generally more work per chain than EVM indexing, which limits how quickly cross-chain analytics can catch up.

Where the Indexing Layer Is Going

Three trends are shaping the future of indexing. First, specialisation — general-purpose indexers cannot match the performance of purpose-built pipelines for specific use cases (DEX aggregators, MEV analytics, on-chain KYC). Second, AI tooling — The Graph's documentation now describes a Subgraph MCP and agent skills for working with Subgraphs and Substreams from AI agents. Third, cross-chain composition — as more dApps go multi-chain, indexers that seamlessly aggregate across many chains become more valuable than any single-chain indexer.

How to Vet a Subgraph Before Trusting Its Data

Not all subgraphs are correct. Before building on someone else's subgraph, check: is it maintained by the protocol team or an unrelated party? When was it last updated? Are the entity counts consistent with on-chain reality (spot-check against Etherscan)? Does the schema handle protocol upgrades and re-deployments? A polished dashboard reading from a broken subgraph will confidently show wrong numbers — always verify the pipeline before trusting the output.

Key Takeaways

  • The Graph's decentralised market coordinates indexers, curators, and consumers via GRT
  • Substreams enable parallel, composable indexing pipelines
  • Non-EVM indexing is more fragmented and generally harder per chain
  • Specialisation, AI tooling, and cross-chain aggregation are shaping the future
  • Always verify the pipeline before trusting the output

Related Content

App-Chains and Rollup-as-a-Service

How Cosmos-style app-chains and modern Rollup-as-a-Service (RaaS) providers (Caldera, Conduit, AltLayer, Gelato) let applications deploy dedicated chains, and the trade-offs vs shared chains.

Cosmos IBC and Interchain Security

How Cosmos IBC enables cross-chain messaging without wrapped assets, how Interchain Security (ICS) let chains rent security from the Cosmos Hub before the Hub removed it in 2026, and what these primitives mean for Cosmos's app-chain thesis.

Polkadot Parachains

How Polkadot's parachain model works — shared security via the Relay Chain, XCM cross-chain messaging, agile coretime — and how the network has evolved from parachain auctions to coretime markets.

RPC Providers Compared

How RPC providers like Alchemy, Infura, QuickNode, and Ankr sit between wallets and blockchains — their business models, reliability differences, censorship risks, and how to think about decentralised alternatives.

Oracle Providers Compared

Chainlink, Pyth, RedStone, API3, and Tellor — how each oracle network sources and delivers off-chain data, their trust and economic models, and which use cases suit which oracle.

Bridge Architectures Compared

How Wormhole, LayerZero, Hyperlane, Axelar, and Across handle cross-chain messaging and asset transfer — their trust models, exploit histories, and the fundamental trade-offs between speed, security, and generality.

CBDCs by Jurisdiction

The state of central bank digital currency projects across China, EU, UK, US, and other major jurisdictions — retail vs wholesale designs, privacy trade-offs, and how CBDCs interact with existing stablecoins.

MiCA Stablecoin Detail

How the EU's Markets in Crypto-Assets Regulation (MiCA) treats stablecoins — the ART and EMT categories, issuer requirements, reserve rules, and the practical effect on Tether, Circle, and other stablecoin issuers in Europe.

References & further reading