The Graph is a decentralized protocol for indexing and querying data from blockchains. Using subgraphs, developers can reliably query blockchain data, ensuring fast, consistent, and permissionless access.

Key Roles in The Graph

• Subgraph Developers
  • Build and maintain subgraphs.
  • Deploy subgraphs using Studio or directly via CLI.
• Curators
  • Signal on high-quality subgraphs with GRT, indicating to Indexers that these subgraphs are valuable to the ecosystem.
  • Earn a portion of query fees based on the subgraphs they curate.
• Indexers
  • Operate The Graph’s indexing nodes and stake GRT to secure their right to serve queries.
  • Earn query fees and indexing rewards for providing quality service.
• Gateways
  • Allows consumers to query data made available by Data Suppliers.
  • Routes queries from data consumers to Indexers, providing payment and supplier abstraction
  • Offers a single endpoint to data consumers for accessing subgraphs.
• Data Consumers
  • Use subgraphs to query on-chain data for front-ends, analytics, or other services.
  • Pay query fees when querying subgraphs on the decentralized network.

The Graph Building Blocks

In The Graph ecosystem, building, publishing, and serving on-chain data revolves around three key building blocks: The Studio, the decentralized Network of Indexers, and specialized Gateways.

The Studio provides a user-friendly environment in which to develop subgraphs before going live. Once published, subgraphs are signaled on, by Curators, and picked up by a global pool of Indexers on the Network incentivized to do so as a function of the signal. Gateways—such as the GraphOps Gateway— mediate payments and routing between the customer and the decentralized network, adding an extra layer of performance and resilience by routing queries to top-tier Indexers. Together, these elements create a fast, robust, and truly decentralized data experience for any dApp.

Subgraphs

Subgraphs are open APIs on The Graph that organize and serve blockchain data to applications. Using subgraphs, developers and data consumers alike benefit from speedy access to indexed data.

Learn more: https://thegraph.com/docs/en/subgraphs/quick-start/

What’s Needed for a Subgraph to be Indexed

1. Deployment to IPFS
   • Subgraphs are compiled into a set of files that define the indexing logic; these files are published to IPFS (via Studio or the CLI).
2. Registration on the Network
   • Once you publish the subgraph, it becomes visible to Indexers.
   • Curators may stake GRT to signal its value, attracting Indexers to allocate resources.
3. Indexer Allocation
   • At least one Indexer must allocate stake to your subgraph so that it can be actively indexed.
   • More allocations typically mean more available capacity and faster queries.

About GraphOps

In 2022, we proudly joined The Graph as a Core Developer, where our commitment to advancing protocol economics, streamlining network operations, and enhancing the Indexer experience has driven significant impact for The Graph Network.

Drawing on deep experience in building tools for web3 consumers and operators, GraphOps delivers resilient infrastructure that supports ongoing growth and scalability. We spearhead initiatives like GraphSeer, Graphcast, Launchpad, and the GraphOps Gateway while also contributing significantly to the Indexer Stack and operating the GraphOps Indexer.