- The Graph Overview
- Asset Role and Supply
- Market Structure
- YearBull Perspective
- Key Risks
- Primary Sources and Review Scope
- The Graph: A Decentralized Data Layer Moving Beyond Subgraphs
- What The Graph does
- How the network is organized
- What Graph Horizon changes
- GRT's actual role
- Governance and upgrade control
- Users, dependencies, and limitations
- Key takeaways
- Risks and open questions
- YearBull Rank overview
The Graph Overview
The Graph (GRT) is tracked under the-graph. The local profile associates it with Artificial Intelligence (AI), Business Services, Infrastructure, Analytics. The source profile maps it to ethereum, harmony-shard-0, near-protocol.
Asset Role and Supply
Its role should be evaluated through network or product use, supply design, governance, liquidity, and trading-venue quality. The reviewed record shows circulating supply about 10.94 billion GRT, total supply about 11.61 billion GRT, maximum supply about 10.80 billion GRT. It classifies supply as capped. Supply fields may change through issuance, burns, migrations, or source revisions and should be checked against project records.
Market Structure
At the 2026-09-12 review, the local snapshot placed The Graph at market-cap rank #177, with market capitalization about $196.66 million and reported 24-hour volume of $10.18 million. These values describe observed scale and turnover, not fair value or guaranteed executable liquidity.
YearBull Perspective
The dated snapshot recorded YearBull Rank #118, Bull Score 69/100, Risk Low, and Cycle Early. Rank, Bull, Risk, and Cycle answer different questions and should be read together.
Key Risks
Material risks include market volatility, liquidity deterioration, protocol or governance failure, concentration, and regulatory change. Historical prices, rankings, and classifications do not predict future performance. Verify contract addresses, network support, custody, and venue availability before acting.
Primary Sources and Review Scope
YearBull methodology · Official website · Source repository. Profile and market fields were checked against locally stored source records on 2026-09-12. The live snapshot above may be newer than this editorial review.
The Graph: A Decentralized Data Layer Moving Beyond Subgraphs
The Graph turns blockchain activity into queryable APIs through Subgraphs, independent Indexers, and GRT-based economic coordination. Its Horizon upgrade broadens that design toward multiple blockchain data services, but the network still depends on reliable infrastructure, accurate indexing, and sustained demand from applications.
What The Graph does
The Graph is an indexing and query protocol for blockchain data. Instead of requiring every application to scan blocks and reconstruct protocol state independently, developers can publish Subgraphs that define which on-chain events, entities, and relationships should be indexed. Applications then retrieve that structured data through GraphQL endpoints. This makes The Graph primarily a data-access system rather than a general-purpose execution network.
A Subgraph is built from a manifest, schema, and mapping logic. The manifest identifies the data sources and indexing configuration, while the GraphQL schema defines the entities that applications can query. Graph Node reads blockchain data, applies the Subgraph's mappings, stores the resulting records, and exposes them through GraphQL. The design is useful for decentralized applications, analytics products, wallets, and other services that need structured historical blockchain data without operating a complete indexing stack themselves.
How the network is organized
The decentralized network separates data production from data consumption. Indexers operate infrastructure, synchronize selected Subgraphs, and answer queries. Curators use GRT to signal which Subgraphs they consider useful, while Delegators assign GRT to Indexers and share in eligible rewards. Consumers access data through Gateways, which route requests to Indexers and handle payment and service selection. This creates several specialized roles instead of placing all data hosting under one operator.
Graph Node also has practical dependencies outside the protocol contracts. An Indexer generally needs blockchain RPC access, database capacity, IPFS access for deployment metadata, monitoring, and operational controls. Some Subgraphs require archive-node or tracing functionality. These requirements mean that decentralization of the payment and coordination layer does not remove the need for professional infrastructure operators.
What Graph Horizon changes
Graph Horizon is a major protocol upgrade that changes The Graph from a Subgraph-focused network into a modular framework for multiple data services. The Subgraph Service remains the existing core service, while the Horizon architecture is intended to support additional services such as specialized APIs, streaming data, and other blockchain-data products. The protocol's staking, payment, allocation, and dispute primitives are being designed for reuse across those services.
For users and developers, the upgrade is designed to preserve Subgraph query access. For Indexers, however, Horizon is a breaking infrastructure change: operators must upgrade their software to continue opening new allocations and participating fully in rewards and query fees. Delegation is now associated with a particular data service, currently the Subgraph Service in the documented user flows. This makes the protocol more flexible, but also increases the importance of software compatibility and migration management.
GRT's actual role
GRT is used to coordinate the supply and demand sides of the network. Indexers stake GRT to provide indexing and query-processing services, Delegators delegate GRT to support Indexers, and Curators signal on Subgraphs. Network participants can receive rewards connected to indexing activity and query fees, although the outcome depends on factors such as service demand, allocation choices, Indexer settings, and the applicable data-service rules. GRT therefore has a functional role inside the protocol rather than serving only as a transferable asset.
The token economics combine issuance with fee-related burns and penalties. Current documentation describes indexing rewards funded by approximately 3% annual protocol-wide issuance, while query fees and other protocol activity can create burn flows. Horizon also removes the former 0.5% delegation tax and changes the treatment of slashing: delegation slashing is not enabled by default, while Indexer penalties can be determined under the arbitration framework. Older explanations of the token model should therefore be read carefully against the post-Horizon documentation.
Governance and upgrade control
Protocol upgrades and the community treasury are overseen by The Graph Council through the Graph Improvement Proposal process. Proposals are discussed publicly, may receive community voting or consensus signals, and require Council approval before implementation. The governance structure gives the Council a decisive role in technical and economic changes, while the Foundation, core contributors, and community participate in development and review.
The public contracts repository provides a separate view of the implementation surface. It contains the original protocol contracts as well as Horizon and Subgraph Service packages, and its deployment documentation describes an audited main branch and review requirements for production Solidity changes. This is evidence of a formal engineering process, not a guarantee that deployed contracts or the wider network are free from defects.
Users, dependencies, and limitations
The intended users are developers and data providers that need consistent access to blockchain information, including decentralized applications, wallets, analytics platforms, enterprise data services, and potentially AI-oriented interfaces. Gateways can package access through usage-based, subscription, enterprise, or other pricing models, while the underlying protocol coordinates Indexers and data-service payments. The Graph's usefulness consequently depends on more than raw query capability: the relevant Subgraph or service must be available, sufficiently synchronized, and economically worthwhile for Indexers to support.
The main limitation is that indexed data is not automatically equivalent to ground truth. A Subgraph reflects its schema and mapping logic, and an Indexer can face chain reorganizations, RPC failures, software bugs, synchronization delays, or infrastructure outages. Economic security and dispute mechanisms can create incentives for accurate service, but users still need to evaluate the specific Subgraph, deployment, Gateway, and data freshness requirements of an application.
Key takeaways
- The Graph converts blockchain activity into structured, queryable APIs through Subgraphs and GraphQL.
- Indexers, Curators, Delegators, Gateways, and developers perform different roles in the network.
- Graph Node depends on RPC providers, databases, IPFS metadata, and specialized chain infrastructure.
- Graph Horizon broadens the protocol toward multiple data services while preserving the Subgraph Service.
- GRT coordinates staking, delegation, curation, payments, and network rewards; its economics changed under Horizon.
- The Graph's data quality depends on Subgraph logic, synchronization, infrastructure, and the specific Gateway serving a request.
Risks and open questions
- Demand for decentralized blockchain data may not translate into sufficient paid query or indexing activity for all Indexers and data services.
- Subgraph data can be incomplete, stale, incorrectly mapped, or affected by chain reorganizations and RPC or database failures.
- Graph Horizon increases the protocol's scope and introduces migration, compatibility, and operational risks for Indexers and service developers.
- GRT rewards depend on Indexer performance, delegation settings, allocation choices, service demand, issuance, and applicable governance decisions; they are not fixed returns.
- Governance retains authority over technical upgrades, economic parameters, treasury decisions, and arbitration-related rules.
- The protocol's broader multi-service strategy remains dependent on the successful development, adoption, and economics of services beyond Subgraphs.
YearBull Rank overview
Most recent YearBull Rank reading for the-graph is #47.
Rank change (reference points).
Reading rule: a smaller rank number indicates stronger placement.
- 7d window (2026-09-13): #159 → #47 (up by 112).
- 30d window (2026-08-21): #1119 → #47 (up by 1072).
YearBull Rank is an internal ordering on YearBull that positions a coin relative to the rest of the tracked universe. It is best read as relative context across time windows, not as a guarantee.
Orderflow context: a steadier line can indicate steadier access. If the line reacts in bursts, watch for calendar-driven liquidity.
Cycle framing: sideways periods still reshuffle relative placement. If both are flat, the coin may be tracking its peer basket.
Risk framing: a calm line with small steps can be healthier than spikes. If it moves only on certain days, it can be update cadence.
Exchange footprint: venue mix can alter rank without changing the narrative. If rank can’t hold gains, it can be concentrated pressure.
Practical note: compare across windows before concluding.
