Deep Dive
1. CLI Dependency Updates & New Command (0.98.1)
Overview: This update to The Graph's command-line interface (CLI) focuses on maintenance and a new utility for developers. It keeps the toolchain current and adds a command to simplify setting up a local development environment.
The release, version 0.98.1, is primarily a patch containing updates to numerous underlying dependencies, ensuring compatibility and security. The minor new feature is the gnd command, which installs a graph-node development binary locally. This makes it faster for developers to start building and testing subgraphs without complex environment setup.
What this means: This is neutral for GRT as it represents routine maintenance. However, it improves the developer experience by making the toolchain more reliable and easier to use, which could encourage more development on the network over time.
(Source)
2. Horizon Upgrade Goes Live (11 December 2025)
Overview: The Horizon upgrade was a foundational shift for The Graph's protocol, moving it from a single-service indexing network to a modular, multi-service data layer. This allows new products like real-time data streams and pre-indexed APIs to be built on the same secure foundation.
This upgrade did not replace the existing Subgraph service but expanded the underlying protocol's capacity. It enables future services like Substreams for high-speed streaming and the Token API for standardized token data to operate natively within The Graph's ecosystem, all powered by GRT.
What this means: This is bullish for GRT because it significantly expands the protocol's potential use cases and utility. By becoming a platform for multiple data services, The Graph can attract more developers and applications, potentially increasing demand for GRT to pay for queries and secure the network.
(Source)
3. Infrastructure & Network Operations (July 2025)
Overview: This period saw focused work on the network's core infrastructure, including deploying new software versions for node operators and fixing critical data integrity issues across chains like Arbitrum and Scroll.
The GraphOps team released new Helm charts for Kubernetes deployments and updated key components like the graph-node and indexer software. A significant fix resolved an issue where the Arbitrum One network was reporting incorrect block numbers to Scroll, ensuring accurate cross-chain data. The team also began performance comparisons between different data ingestion technologies like RisingWave and ClickHouse.
What this means: This is bullish for GRT because it strengthens network reliability and data accuracy—critical factors for developers building serious applications. Robust infrastructure reduces downtime and errors, making The Graph a more dependable service and supporting long-term adoption.
(Source)
Conclusion
The Graph's recent development trajectory emphasizes robust infrastructure, developer-friendly tooling, and a strategic expansion into a multi-service data platform. While the most transformative protocol upgrade (Horizon) occurred last year, ongoing refinements to the developer CLI and network operations continue to solidify its foundation. How will the rollout of new services like the Token API and Substreams on the Horizon architecture translate into increased network usage and query fee demand?