The Graph Academy
Master The GraphBug BountyExplorer
  • Welcome to The Graph Hub
  • FAQs
  • Official Docs
    • Get Started
    • About The Graph
      • Introduction
      • Network Overview
    • Developer
      • Mastering Subgraphs
      • Quick Start
      • Define a Subgraph
      • Create a Subgraph
      • Publish a Subgraph to the Decentralized Network
      • Query The Graph
      • Querying from an Application
      • Distributed Systems
      • AssemblyScript API
      • AssemblyScript Migration Guide
      • GraphQL API
      • Unit Testing Framework
      • Quick and easy subgraph debugging using forks
      • Deprecating a Subgraph
    • Indexer
      • What are Indexers?
      • Revenue Streams
      • Reward Distribution
      • Allocation Lifecycles
      • Indexing & Querying
      • Hardware requirements
      • IPFS hash converter
      • Vulnerabilities
      • Indexer Subgraph Selection Guide
      • Testnet
        • Graph Protocol Testnet Docker Compose
        • Graph Protocol Testnet Baremetal
          • Architecture Considerations
          • Deploy and Configure Database
          • Deploy and Configure Graph-node
          • Deploy and Configure Indexer stack
      • Monitoring
        • Ethereum Node Chainhead Monitoring - no third parties
      • Best Practices
        • Failed subgraphs - Manually Closing Allocations
    • Delegator
      • Choosing Indexers
        • Network Page
        • Tools
        • Guides
      • Reward Statuses
    • Curator
    • Subgraph Studio
      • How to Use the Subgraph Studio
      • Deploy a Subgraph to the Subgraph Studio
      • Billing on the Subgraph Studio
      • Managing your API keys
      • Subgraph Studio FAQs
      • Transferring Subgraph Ownership
    • The Graph Explorer
    • Supported Networks
      • Building Subgraphs on NEAR
      • Building Subgraphs on Cosmos
      • Building Subgraphs on Arweave
  • The Graph Ecosystem
    • Network
      • Core Developer Teams
        • Edge & Node
        • Streamingfast
        • Figment
        • Semiotic
        • The Guild
        • GraphOps
      • The Graph Foundation
      • The Graph Council
      • Graph Advocates
      • Graph Advocates DAO
    • Infrastructure
      • Mainnet
      • Testnet
      • Network Migration
      • Multichain Migration
      • Firehose
      • Substreams
      • The Graph Client
Powered by GitBook
On this page
  • Requirements
  • Function in the network
  • Indexer staking
  • Slashing risks
  • Delegation
  • Thawing period
  • Cooldown period

Was this helpful?

  1. Official Docs
  2. Indexer

What are Indexers?

What are Indexers in The Graph Network?

PreviousIndexerNextRevenue Streams

Last updated 2 years ago

Was this helpful?

Indexers operate nodes in The Graph Network and provide indexing and query processing services to customers. By staking Graph Tokens (GRT), Indexers earn indexing rewards and query fees for their services. Additionally, Indexers earn from a Rebate Pool that is shared with all network contributors proportional to their work, following the . See for more details on Indexer incentives.

The technical level to participate in the network as an Indexer is ADVANCED. To get started as an Indexer, follow the .

Requirements

Indexers need to stake at least 100k GRT tokens to run a node and participate in the network as an Indexer. Aside from the technical knowledge to run a node, Indexers also have to be able to provide the technical infrastructure for doing so.

Function in the network

Indexers select subgraphs in The Graph Network to index. Customers (typically end-users) query the indexed data by paying for their metered usage based on the laws of supply and demand. Indexers are running an indexer agent that programmatically monitors their resource usage, sets prices, and decides which subgraphs to index. Indexers can set their own pricing models and strategies to gain a competitive edge in the marketplace.

The selection of subgraphs by indexers is based on subgraph’s curation signal, where Curators stake GRT in order to indicate which subgraphs are high-quality and should be prioritized. Consumers (eg. applications) can also set parameters for which Indexers process queries for their subgraphs and set preferences for query fee pricing.

Indexer staking

The Graph utilizes a model. Based on this model, service providers to the network such as Indexers must stake Graph Tokens (GRT) in order to sell their services in the query market. The adoption of the work token model serves to primary functions:

  • Economic security: GRT that is staked can be slashed (see below for more information on slashing)

  • Sybil resistance: Only indexers who are willing to invest resources are able to participate

Indexers are incentivized to hold GRT roughly in proportion to the amount of work they seek to contribute to the network.

Slashing risks

Indexers in The Graph Network are incentivized to provide honest and reliable indexing and query processing services. In order to safeguard that Indexer misbehavior is discouraged, Indexers have to stake GRT that is subject to a thawing period. If Indexers act maliciously, serve incorrect data to applications or index incorrectly, their staked GRT can be slashed.

Slashing is a mechanism built into The Graph protocol to discourage and punish malicious Indexer behavior. Additionally, slashing incentivizes node security, availability, and network participation.

It is important to note that curators and delegators are not subject to slashing or other punishments for Indexer misbehavior.

Delegation

Indexers can also be delegated stake from Delegators, to contribute to the network. You can find further documentation about delegators here:

Thawing period

GRT that is staked by Indexers in the protocol is subject to a thawing period and can be slashed if Indexers act maliciously.

Cooldown period

Indexers have a “cooldown” that determines how often they can change delegation parameters. Indexers are free to decide the cooldown period but are subject to reprimands by the free market. All other things being equal, Indexers who set longer cooldowns should receive more delegation from delegators.

Cobb-Douglas Production Function
Revenue Streams
Indexer documentation
work token