At a glance: This page reviews the original 2018 version 0.2 paper, then distinguishes that early design from The Graph as it operates today. The paper introduced a way to turn selected blockchain data into open, queryable APIs called subgraphs. The modern network retains that core idea, but its products, payment design, and governance have changed substantially.
| Original paper | The Graph: A Decentralized Query Protocol for Blockchains |
|---|---|
| Authors | Yaniv Tal, Brandon Ramirez, and Jannis Pohlmann |
| Version and date | Version 0.2, March 21, 2018 |
| Project | The Graph |
| Focus | Indexing and querying selected blockchain data through subgraphs |
| License | Not stated in the original paper |
| Official paper | Read the original paper on GitHub |
The paper is an early protocol design, not a current operating manual. Its description of roles and incentives should be read as the proposed system at that time. The Graph’s documentation and later network changes are better references for present-day behavior.
The problem the paper set out to solve
Blockchains record transactions and state, but application developers often need organized answers: a user’s token transfers, a market’s trading history, or a protocol’s current positions. Repeatedly scanning chain data or building a separate database for every application can be slow, costly, and difficult to maintain. A centralized data API can make this easier, but it places an intermediary between the application and the underlying public data.
The paper proposed a shared way to define how blockchain data is selected, transformed, stored, and queried. Instead of asking every application to build the same indexing pipeline, a developer could publish a reusable data definition that other applications and network operators could work with.
How a subgraph works
A subgraph describes a particular view of data from a blockchain. In the current developer workflow, its manifest identifies the network and contracts to follow, the events to process, and the mappings that convert those events into structured records. A GraphQL schema defines the records and the shape of queries. Indexing software processes the selected chain data and makes the resulting API queryable.
This is useful when an application needs a predictable data model instead of repeatedly interpreting raw blocks and logs. It is also a deliberate boundary: a subgraph only covers the networks, contracts, events, and fields its authors define. It is not an automatic index of every fact on every chain, and an application still has to check that its chosen subgraph contains the data and history it needs.
The original paper describes a marketplace around these data definitions. Developers publish subgraphs; Indexers run infrastructure to synchronize and serve them; Curators signal which subgraphs they consider useful; and Delegators allocate stake to Indexers. Applications then query an endpoint for the indexed data. These roles remain useful for understanding The Graph, but the original paper’s specific payment and incentive mechanics should not be mistaken for today’s complete implementation.
What changed after the paper
The original design has since become a live protocol and product ecosystem. The centralized Hosted Service, which helped developers try the model, is no longer active: The Graph’s sunset notice says it ended on June 12, 2024. That history matters because older articles sometimes describe the Hosted Service as a normal production route. Current developer documentation instead describes publishing subgraphs to The Graph Network and querying through network gateways.
Graph Horizon is a later architectural change. It separates reusable staking and payment foundations from the data services built on top of them. The official Horizon documentation describes SubgraphService as the first service in this framework and, in its current documentation, the only deployed data-service implementation. The Graph’s broader product suite also includes tools such as Substreams and Firehose; their existence does not mean each one is interchangeable with a Subgraph or uses every part of the same service flow.
Queries are not necessarily paid one transaction at a time. The current Graph Tally documentation describes signed off-chain receipts that are accumulated and settled in batches between gateways and Indexers. It calls the system trust-minimized, which is a narrower claim than fully trustless: operators still manage endpoints, payment infrastructure, and service quality.
The network’s current governance and reward arrangements also continue to evolve. The Graph Foundation’s October 1, 2026 quarterly recap says the Foundation took on a more direct operating role for the Subgraph Gateway, Subgraph Studio, and Graph Explorer; describes the Rewards Eligibility Oracle; and reports Council approval of an Innovation Allocation funded by 20% of protocol issuance. The same recap says Studio staging queries for BNB Smart Chain and Polygon ended October 8, 2026, with developers expected to use the network route. These are dated changes, not promises that every future rule or product will remain the same.
GRT, incentives, and practical trade-offs
Indexers provide and maintain indexing capacity; Delegators can assign stake to an Indexer without operating one themselves; and Curators can signal subgraphs. GRT participates in the network’s staking, signaling, and payment systems. Depending on the product and route, developers or data providers handle query charges; ordinary users of an application do not necessarily buy GRT or submit a blockchain transaction for every data request.
There are trade-offs. Developers must select or build a suitable subgraph, wait for indexing, and keep its mappings current. A query depends on the subgraph’s coverage and correctness, the Indexers serving it, and the gateway or endpoint used to reach it. Rewards, fees, delegation outcomes, and token value can change; none is a guaranteed return. Graph Tally’s payment design reduces the need for per-query on-chain settlement, but does not remove operational or counterparty risk.
For that reason, The Graph is best understood as blockchain data infrastructure with a decentralized network component, not as a guarantee that all chain data is complete, instantly available, or independently verified for every use case. Users should inspect a subgraph’s scope and update behavior and should understand which service or endpoint their application relies on.
Social Media Sentiment
A small sample of recent r/thegraph posts is mostly builder-focused. One post discusses making it easier to discover a relevant subgraph, while another walks through deploying one on a newly supported chain and points out practical issues such as checking network support and attracting indexing signal. The October 2026 network recap is more upbeat about migration and new services, but it is an official project update. These examples suggest constructive interest alongside real discovery and deployment friction; they are anecdotal and too small to represent the wider community or measure opinion about GRT.
Last updated: 2026-10
Related Terms
- Subgraphs — custom data definitions that turn selected chain activity into a queryable API.
- IPFS — a peer-to-peer content-addressed storage network used in parts of The Graph’s tooling and history.
- Node — software that participates in reading, indexing, or serving blockchain data.
See Also
- Ethereum: A Secure Decentralised Generalised Transaction Ledger — the foundational proposal for Ethereum, the first network where The Graph’s indexing model became widely relevant.
- Chainlink: A Decentralized Oracle Network — a different approach to connecting smart contracts with external data and services.
- IPFS: Content Addressed, Versioned, P2P File System — background on the content-addressed storage idea referenced in The Graph’s ecosystem.
Sources
- The Graph whitepaper, version 0.2 (March 21, 2018) — the primary source for the paper’s title, authors, date, and original protocol design.
- The Graph: Subgraphs overview — explains manifests, schemas, mappings, publishing, and querying in the current developer workflow.
- The Graph: Indexing overview — documents current network participants and indexing responsibilities.
- The Graph: Graph Horizon overview — describes the modular service framework, staking and payment foundations, and SubgraphService.
- The Graph: Graph Tally for Gateway Operators — details signed receipts, batched settlement, and the system’s trust-minimized design.
- The Graph: The Road to Sunsetting the Hosted Service — records the Hosted Service transition and its June 2024 end date.
- The Graph Foundation: Q3 2026 on The Graph — summarizes the October 2026 operating, reward, governance, and product updates.
- Reddit: An MCP server that finds the right subgraph by meaning — one builder’s September 2026 discussion of subgraph discovery; an individual post, not a representative survey.
- Reddit: It has never been easier to ship a subgraph — one September 2026 deployment account that also notes practical chain and indexing constraints.