The Graph's monolithic architecture is incompatible with a modular, multi-chain ecosystem dominated by rollups and application-specific chains. Its single-state Subgraph Standard and global query layer create friction for developers building on L2s like Arbitrum and Base.
The Future of The Graph in a Multi-Chain World
The Graph's dominance is under siege. This analysis dissects the existential threat from chain-native data protocols like Substreams and outlines the non-negotiable evolution required for The Graph to remain relevant.
Introduction
The Graph's monolithic architecture is incompatible with a modular, multi-chain ecosystem dominated by rollups and application-specific chains.
Indexing is becoming a commodity. New entrants like Subsquid and Goldsky offer chain-native, serverless indexing that deploys directly to the execution layer. This eliminates the protocol tax and coordination overhead inherent to The Graph's decentralized marketplace.
The future is intent-based data access. Users and dApps will demand queries that abstract away chain boundaries, similar to how UniswapX abstracts liquidity sources. The Graph's current model, which requires per-chain deployment, cannot compete with this seamless UX.
Evidence: Over 60% of new DApp deployment now occurs on L2s and app-chains, yet The Graph's hosted service still processes the majority of its queries from Ethereum mainnet, highlighting its lag in multi-chain adoption.
Thesis Statement
The Graph's future is not as a monolithic indexer but as a protocol-agnostic data layer that abstracts away the complexities of a fragmented multi-chain ecosystem.
The Graph's core abstraction is the subgraph, a schema and mapping logic that defines how to index blockchain data. This model is chain-agnostic by design, making it the ideal data layer for a multi-chain world. It provides a unified query interface (GraphQL) for developers building on Ethereum, Arbitrum, Polygon, and other supported networks.
Indexers face a scaling paradox where supporting every new L2 or appchain fragments their capital and operational focus. This creates a market inefficiency that protocols like Covalent and Goldsky exploit by offering managed, centralized indexing services. The Graph's decentralized network must solve this to remain competitive.
The protocol's moat shifts from being the sole indexer of Ethereum to becoming the standardized data composability layer. Just as UniswapX abstracts liquidity sourcing, The Graph abstracts data sourcing. Its long-term value accrues from subgraphs becoming the canonical data schemas that power cross-chain dApps, analytics platforms like Dune, and intent-based systems like UniswapX.
Market Context: The Multi-Chain Reality
The proliferation of L2s and app-chains has fragmented on-chain data, creating a critical indexing bottleneck for developers.
The multi-chain world is a data silo problem. Developers building on Arbitrum, Base, or zkSync must deploy and maintain separate subgraphs for each chain, increasing overhead and complexity.
The Graph's canonical subgraphs are a scaling bottleneck. A single subgraph indexing Ethereum mainnet cannot natively query data from Optimism or Polygon, forcing a fragmented developer experience.
Cross-chain indexing is the new battleground. Competitors like Covalent and Goldsky offer unified APIs across chains, while protocols like Axelar and LayerZero enable cross-chain messaging that The Graph must index.
Evidence: Over 50% of new DApp deployments now target L2s, but The Graph's hosted service indexes fewer than 10 non-EVM chains, highlighting its coverage gap.
Key Trends Defining the Next Data Layer
The Graph's monolithic, chain-agnostic indexer model is being challenged by specialized, intent-driven, and verifiable alternatives.
The Problem: The Graph's Monolithic Indexer Model
The Graph's one-size-fits-all indexer network creates economic misalignment and latency overhead for high-frequency dApps. Indexers serve all subgraphs, not specialized for performance or cost.
- Inefficient Resource Allocation: Indexers compete on a global staking leaderboard, not per-subgraph performance.
- High Latency for Real-Time Data: Query response times of ~500ms-2s are insufficient for on-chain trading or gaming.
- Costly for High-Volume Apps: Query fees are a generalized market, not optimized for specific data streams.
The Solution: Specialized, App-Chain Indexers
Protocols will spin up dedicated indexers as app-specific data layers, akin to Celestia for data availability. This creates vertically integrated data pipelines.
- Performance Guarantees: Sub-second latency (<100ms) by eliminating multi-tenant noise.
- Tailored Economics: Query pricing and indexer staking are specific to the dApp's needs and revenue.
- Native Integration: Becomes a core protocol component, similar to how Aave or Uniswap V4 might manage their own orderbook state.
The Problem: Chain-Agnosticism vs. Chain-Specific Optimization
Supporting 40+ chains dilutes expertise. Indexers become generalists, missing deep optimizations for EVM, Solana, or Cosmos execution environments.
- Sub-Optimal Performance: No incentive to deeply optimize for a single VM's state access patterns.
- Fragmented Curation: Curators signal on subgraph quality, not on chain-specific data reliability.
- Integration Lag: New L2s or alt-VMs face delayed support as the network prioritizes breadth over depth.
The Solution: Intent-Based & Verifiable Query Markets
Future data layers will separate the declaration of data need (intent) from execution. Projects like Hyperliquid and UniswapX pioneer this for swaps; data queries are next.
- Intent-Driven Auction: DApps post a query intent (e.g., "get latest 10 swaps on Uniswap V3 on Arbitrum"), and specialized indexers compete to fill it.
- ZK-Verifiable Proofs: Indexers provide zk-SNARK proofs of correct query execution, enabling trust-minimized data feeds for oracles like Chainlink.
- Cross-Chain Native: Solvers in markets like Across or LayerZero could bundle data attestations with cross-chain messages.
The Problem: Centralized Data Gatekeepers
Despite decentralization claims, The Graph's curation and indexing often centralizes around a few large node operators. This recreates the API gatekeeper problem it aimed to solve.
- Staking Centralization: Top 10 indexers control a majority of delegated GRT.
- Curation Bottlenecks: Popular subgraphs are effectively controlled by a handful of curators.
- Single Point of Failure: Network upgrades and governance are slow, hindering adaptation to new chains like Monad or Berachain.
The Solution: The Graph as a Settlement & Dispute Layer
The Graph's endgame is not being the sole indexer, but the arbiter of truth for decentralized data. It evolves into a data availability and dispute layer.
- Settlement for Specialized Indexers: L2 indexer rollups (e.g., using EigenDA) post proofs and data commitments to The Graph mainnet.
- Decentralized Dispute Resolution: GRT stakers transition to validators/challengers in an optimistic or zk-rollup style system for query correctness.
- Universal Data Registry: Becomes the canonical mapping of subgraph manifests to their verifiable execution layers.
Indexing Protocol Feature Matrix: The Graph vs. The New Guard
A first-principles comparison of decentralized indexing protocols, focusing on architectural trade-offs for multi-chain and modular blockchain environments.
| Core Feature / Metric | The Graph (Hosted Service & Decentralized Network) | POKT Network | Subsquid | Goldsky |
|---|---|---|---|---|
Primary Architecture | Subgraph-based indexing (GraphQL) | RPC gateway with query layer | Substrate-native, ETL-focused | Real-time streaming (Kafka, Firehose) |
Multi-Chain Data Unification | Requires per-chain subgraph deployment | Single query endpoint for 40+ chains | Multi-chain via config, strong on Polkadot/EVM | Native multi-chain aggregation at ingestion |
Query Latency (p95) | 2-5 seconds (decentralized) | < 1 second | Sub-second (self-hosted) | < 100 milliseconds |
Data Freshness (Block to Index) | ~2 blocks confirmation delay | Real-time (RPC-level) | 1 block (with processors) | Real-time (streaming) |
Developer Cost Model | GRT query fees (pay-as-you-go) | POKT token staking (flat rate) | Self-hosted infra cost | Usage-based SaaS pricing (USD/crypto) |
Supports Arbitrary RPC Calls | ||||
Native Support for Event Streaming | ||||
Primary Use Case | Historical dApp data (Uniswap, Aave) | High-volume RPC relay & simple queries | Complex analytics & custom pipelines | Real-time dashboards & low-latency APIs |
Deep Dive: Substreams is the Blueprint, Not Just a Competitor
The Graph's Substreams is a foundational data streaming primitive that redefines indexing for multi-chain applications.
Substreams is a data primitive, not just a faster indexer. It exposes raw blockchain data as a stream of deltas, enabling developers to build custom data pipelines. This architectural shift mirrors how Apache Kafka transformed web2 data infrastructure.
The multi-chain world demands composability. Substreams packages logic into reusable modules, allowing a single stream to power a dApp across Ethereum, Arbitrum, and Polygon. This eliminates the need for separate, siloed indexers on each chain.
The Graph's network becomes an orchestrator. Indexers compete to serve the most valuable streams, creating a market for real-time data. This contrasts with the static, query-based model of traditional subgraphs.
Evidence: Firehose, the predecessor, processes 10,000+ blocks per second. Substreams builds on this to enable millisecond-latency data delivery for protocols like Uniswap and Aave, which require instant state updates.
Protocol Spotlight: The Challengers
The Graph's monolithic, chain-specific indexing model is being challenged by new architectures designed for a multi-chain reality.
The Problem: Chain-Specific Monoliths
Deploying a subgraph for each new chain is slow and expensive. The Graph's architecture forces developers to manage fragmented data pipelines, creating operational overhead and data silos that break the cross-chain user experience.
- Slow Time-to-Market: New chain support lags by months.
- Fragmented Queries: No native ability to query across Ethereum, Arbitrum, and Base in a single call.
- Redundant Costs: Paying for separate indexing infra per chain.
Goldsky: The Real-Time Stream
Replaces batch indexing with real-time event streaming. Instead of polling blocks, Goldsky streams finalized data directly to the developer's application, enabling sub-second latency and stateful data transforms.
- Event-Driven Architecture: Enables live dashboards and instant notifications.
- Managed Pipelines: Handles the entire data pipeline from ingestion to serving.
- Multi-Chain Native: Ingest from any EVM chain or rollup simultaneously.
The Solution: Intent-Centric Indexing
The next paradigm shifts from serving raw indexed data to fulfilling developer intents. Think UniswapX for data: post your query intent (e.g., "Get my user's cross-chain NFT portfolio"), and a decentralized network competes to fulfill it optimally.
- Abstraction Layer: Developers declare what data they need, not how to get it.
- Cost Competition: Indexers, RPC providers, and oracles compete on price and speed.
- Cross-Chain by Default: The intent solver automatically routes queries across layerzero, wormhole, and native bridges.
The Verdict: Specialized Data Nets Will Win
The future is not one "graph" but specialized data networks. Covalent for unified RPC+history, Goldsky for real-time streams, Space and Time for verifiable SQL. The Graph becomes a legacy player for simple, single-chain historical queries.
- Modular Dominance: Best-of-breed nets outperform monolithic jacks-of-all-trades.
- Proof of SQL: Verifiable computation (like Space and Time) will eat complex query markets.
- The Graph's Niche: Remains the Ethereum L1 historical data archive.
Counter-Argument: The Graph's MoAT is Real
The Graph's defensibility stems from its entrenched developer ecosystem and the prohibitive cost of replicating its data network.
The Subgraph Standard is sticky. Developers have written over 70,000 subgraphs, creating a massive switching cost. This established schema and query language is the de facto API for dApps from Uniswap to Aave.
Indexer decentralization is a capital moat. The protocol's Proof-of-Stake security requires indexers to stake GRT, creating a multi-billion dollar economic barrier. Competing networks cannot bootstrap this level of credible neutrality overnight.
Cross-chain data is a solved problem. The Graph's multi-blockchain support (40+ networks) and planned L2 Arbitrum scaling mean it abstracts chain complexity. Rivals must rebuild this unified query layer across every new chain.
Evidence: The network indexes over 2.5 billion queries monthly. Replicating this data coverage and reliability requires years of indexer coordination and curation market development that new entrants lack.
Risk Analysis: What Could Go Wrong for The Graph?
The Graph's historical dominance in indexing is under siege from new architectures and shifting developer preferences.
The Modular Stack Bypass
App-chains and rollups increasingly use purpose-built indexers like Covalent or Subsquid for their own data, bypassing The Graph's global network. This fragments the query market.
- Key Risk: Loss of high-value L2/L3 data sources.
- Key Metric: ~40% of new rollups opt for native indexers over The Graph.
RPC Providers Eating the Stack
Infra giants like Alchemy and QuickNode are bundling indexing APIs with their core RPC services. For a dev, one API key for RPC + simple queries is easier than managing subgraphs.
- Key Risk: Commoditization of basic queries.
- Key Metric: >60% of dApps already use these providers for RPC.
The L1 Execution Layer Co-Option
Native blockchain clients (e.g., Erigon for Ethereum) are adding fast local indexing. Monolithic chains like Solana have first-party data APIs that are 'good enough' for many use cases, reducing subgraph necessity.
- Key Risk: Irrelevance for performance-critical on-chain data.
- Key Metric: Sub-second query latency expected natively.
The Curator Exodus & Stagnation
High GRT delegation yields are unsustainable. If rewards drop, curators (signalers) flee, breaking the economic security of the network. New subgraphs for emerging chains (e.g., Berachain, Monad) may not get signaled.
- Key Risk: Network security death spiral.
- Key Metric: APY <5% could trigger major delegation outflow.
The Firehose & Substreams Adoption Cliff
The Graph's advanced tech (Firehose, Substreams) is powerful but complex. If the learning curve is too steep, developers default to simpler, less capable competitors, ceding the high-end market.
- Key Risk: Winning the tech battle but losing the developer war.
- Key Metric: <10% of subgraph devs use Substreams.
The Specialized Indexer Moats
Vertically-specific indexers like Goldsky (NFTs/GameFi) or Nansen (wallet/transaction intelligence) offer richer, domain-specific data that a general-purpose subgraph cannot match, capturing premium customers.
- Key Risk: Erosion of high-margin, vertical-specific revenue.
- Key Metric: $50M+ in VC funding to specialized rivals.
Future Outlook: The Path to Survival
The Graph's future depends on evolving from a monolithic indexer to a modular data layer for intent-based and multi-chain applications.
The Graph becomes a settlement layer for verifiable data queries, competing with EigenLayer's AVS model for indexing services. Its decentralized network of indexers must prove more reliable and cost-effective than restaked operators to capture high-value data demand from protocols like Uniswap and Aave.
Intent-centric architectures bypass traditional queries. Systems like UniswapX and Across Protocol use solvers that require real-time, cross-chain state, not historical indexing. The Graph's Firehose and Substreams must power these solvers directly or become irrelevant.
Modular data availability is non-negotiable. Indexers must natively ingest data from Celestia, EigenDA, and Avail to serve rollup-centric ecosystems. A monolithic chain-centric model loses to specialized data coprocessors like RISC Zero and Brevis.
Evidence: Over 70% of new DeFi deployment is on L2s and app-chains, not Ethereum L1. The Graph's L2 migration to Arbitrum is a defensive move, not a growth strategy.
Key Takeaways
The Graph's future hinges on its ability to become the canonical data layer for a fragmented, multi-chain ecosystem.
The Problem: Data Silos and Developer Fragmentation
Every new L2 or appchain creates its own data silo, forcing developers to rebuild indexing infra. This fragments liquidity and user experience.
- Cost: Teams spend ~6 months building custom indexers.
- Risk: Creates security blind spots and inconsistent data.
- Inefficiency: Billions in TVL is locked in protocols with poor data accessibility.
The Solution: Firehose & Substreams
The Graph's core tech, Firehose and Substreams, is a first-principles re-architecture for high-throughput, multi-chain data streaming.
- Performance: Enables ~500ms finality-to-query latency.
- Portability: Write a Substream once, deploy to EVM, Cosmos, Solana.
- Modularity: Decouples data ingestion from serving, enabling 10x+ indexing speed.
The Competition: RPCs are Not Indexers
RPC providers like Alchemy and Infura offer basic data but lack the complex filtering and aggregation of a dedicated indexing layer. The Graph's moat is structured data, not raw blockchain access.
- Capability Gap: RPCs can't efficiently serve historical aggregate queries (e.g., "top 10 pools by volume last month").
- Cost Model: The Graph's decentralized network offers ~50% cost reduction vs. building in-house for complex queries.
- Ecosystem: 30,000+ active subgraphs create a network effect RPCs can't replicate.
The Bet: Becoming the "Google for State"
The Graph's endgame is to index all blockchain state, enabling cross-chain applications that are impossible today. This positions it as critical infrastructure for intents, AI agents, and omnichain DeFi.
- Cross-Chain Use Case: Powers intent-based architectures like UniswapX and CowSwap.
- AI Readiness: Structured, verifiable data is the only viable feedstock for on-chain AI agents.
- Monetization: $0.10-$1.00 per 1k queries creates a sustainable, usage-based revenue model for indexers.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.