Coin Alerts

GRT news archive

380 stories

Last checked

Refresh

Estimated news impact scores by coin. Scores are not price-change percentages.

Newest first

Check failed. Showing saved news from .

  7. Published Social post

    The Graph (@graphprotocol)

    The Graph was the most widely used tech at the hackathon with 354 submissions across our three tracks. 🏆 Can't wait to highlight the winners more in the coming days. Congrats to everyone that participated!

  9. Published Social post

    The Graph (@graphprotocol)

    Chain integrations have always been important part of The Graph ecosystem. As part of its new mandate, working with closely chains is now also a core function of The Graph Foundation. Bringing a chain's data onto the network, end to end: Subgraphs, Firehose, and Substreams - with Token API and Tycho built on top. One data supply chain, ready for indexing, streaming, and AI. It'll be an exciting week with four exciting chain-related announcements to boost blockchain builders potential!

  11. Published Social post

    The Graph (@graphprotocol)

    In 2025, 15.2% of indexing rewards went to Indexers serving little to no queries. The Graph’s community asked the ecosystem’s core teams to address those issues in the protocol’s economics. The Rewards Eligibility Oracle closes that gap: it reviews the queries each Indexer served and renews eligibility only for those still doing the work. Same issuance, better allocation. The rewards go to those that create value.

  14. Published Social post

    The Graph (@graphprotocol)

    Earlier this year, The Graph Foundation published the Technical Roadmap, Part 1 of a two-part series on the future of The Graph. Here’s Part 2: the official announcement of the Foundation’s new mandate, and how the Foundation will bring that roadmap to life. https://thegraph.com/blog/new-foundation-mandate/

  15. Published Social post

    The Graph (@graphprotocol)

    Earlier this year, The Graph Foundation published the Technical Roadmap, Part 1 of a two-part series on the future of The Graph. Here’s Part 2: the official announcement of the Foundation’s new mandate, and how the Foundation will bring that roadmap to life. https://thegraph.com/blog/new-foundation-mandate/

  18. Published Social post

    Wu Blockchain (@WuBlockchain)

    Coinbase to Suspend Trading for Six Pairs on August 6 Coinbase Markets will suspend trading for LSETH-ETH, MINA-EUR, GRT-GBP, MASK-GBP, CHZ-USDT and CRO-USDT on August 6, 2026. MINA-EUR, GRT-GBP, MASK-GBP, CHZ-USDT and CRO-USDT are already in limit-only mode.

  19. Published Social post

    Coinbase Markets 🛡️ (@CoinbaseMarkets)

    We regularly monitor the markets on our exchange. In an effort to improve overall market health and consolidate liquidity, we will be removing six non-USD trading pairs for supported assets. We will suspend trading on the LSETH-ETH, MINA-EUR, GRT-GBP, MASK-GBP, CHZ-USDT, and CRO-USDT trading pairs on 6 August 2026. Coinbase Advanced Trade users in eligible regions can still trade these assets in the USD order books.

  20. Published Social post

    The Graph (@graphprotocol)

    Searching for the blockchain data you need just got easier. http://Substreams.dev now organizes data collections by relevant categories so you can find the data you need for testing strategies, giving governance updates, or tracking funds across bridges and marketplaces. Datasets: DEX / AMMs, Lending, Liquid Staking, Perps, Prediction Markets, Governance, Oracles, Bridges, Stablecoins, NFTs, Core Data. Check it out: https://substreams.dev/datasets

  21. Published Social post

    The Graph (@graphprotocol)

    GraphTally: How The Graph Solved Micropayments for the Machine Economy The World Wide Web is one of the most consequential technologies humans have ever built. Yet the people who designed it overlooked one thing: they built it for humans to use, and that is becoming a problem as automation scales. The gap is most obvious in payments. Credit card forms, one-click checkout, and QR codes all assume a living person is at the screen, ready to authorize a transaction. Increasingly, that is not who is transacting. A growing machine-to-machine economy is taking shape, driven by autonomous protocols, decentralized applications, and software agents acting on people's behalf. These actors transact very differently from humans. They rarely hold a bank account, and they need to pay on demand only for what they consume, rather than committing to recurring subscriptions for every resource they touch. Traditional payment rails cannot support high-frequency, fraction-of-a-cent transactions. They are too slow and too expensive, and the fees would often cost more than the value being transferred. Even blockchains, with their promise of low fees, are not efficient enough on their own to settle the smallest payments one by one. The Graph ran into this problem early, and it had to solve it in production. The result is GraphTally, the trust-minimized payment system that lets The Graph Network settle high-frequency, sub-cent payments at scale. It is not a thought experiment. It has been the payment layer of a live decentralized network since early 2025. Why The Graph Needed GraphTally The Graph is the indexing and query layer of web3, a decentralized protocol for indexing and querying blockchain data. Indexers form the backbone of The Graph Network: they organize blockchain data and serve it to the dapps, analysts, and increasingly the AI systems that query it. Blockchains produce endless streams of data. Every time a dapp updates an asset price or reads a user's transaction history, it issues a query. Each query is worth only a fraction of a cent, but the most active Indexers serve hundreds of thousands of queries per day, and that number keeps climbing. Settling each one with its own blockchain transaction is infeasible. Even on a low-cost network, a simple transfer can cost several cents, so an Indexer serving 500,000+ queries a day could lose tens of thousands of dollars in fees alone. The Graph Network needed offchain payments with cheap onchain settlement. GraphTally is that solution. Previously known as the Timeline Aggregation Protocol (or TAP), it is now integrated into the core protocol through Graph Horizon. It rests on a simple idea: keep a running tab offchain, and touch the blockchain only when it is efficient to settle. How GraphTally Works In The Graph Network, payments flow in one direction, from a gateway (the Sender) to an Indexer (the Receiver). That one-way structure is what makes the system efficient. Instead of transferring tokens for every query, a gateway attaches a cryptographically signed Receipt to each request. A Receipt is a verifiable IOU, a signed promise to pay a small fee for the data requested. Because Receipts are created and signed offchain, they can be processed in microseconds with no gas fees. An Indexer cannot redeem hundreds of thousands of individual Receipts onchain; the cost would defeat the purpose. So GraphTally aggregates them. As an Indexer accumulates Receipts, it batches them into a single Receipt Aggregate Voucher (RAV), which represents the running total owed. When the time comes to settle, the Indexer submits one RAV to the blockchain, compressing a large batch of micropayments into a single transaction. GraphTally also keeps gateways honest through a threshold the Indexer controls: the maximum amount it is willing to risk in unaggregated Receipts. If a gateway keeps querying past that limit without settling, the Indexer stops serving it. Onchain, smart contracts verify each RAV, hold gateway funds in escrow, and release payment only against valid submissions. Gateway withdrawals require a thawing period, giving Indexers time to claim anything outstanding. The result meets every requirement the network had: high throughput, since the bottleneck is a fast cryptographic signature; stateless and horizontally scalable senders; trust minimization, since an Indexer can always claim what it is owed onchain without further cooperation from the gateway; and low cost, since the main onchain expense is verifying a single signature. The Same Ideas, Running in Production Early GraphTally was built to solve a specific, concrete problem: paying Indexers for the data they serve. But the problem it solves, trust-minimized micropayments between machines at high frequency, is exactly the problem the wider internet is now confronting as software agents come online. The clearest signal is x402, an open standard from Coinbase and Cloudflare that revives the dormant HTTP 402 "Payment Required" status code so that any service can charge per request. It is a genuinely important step toward internet-native payments. What is striking, for a broader audience trying to understand where this is heading, is how many of x402's core ideas were already live inside The Graph Network months before x402 was announced. The Graph did not follow this pattern; it shipped it early, because a decentralized network serving real query traffic forced the issue. Consider the parallels, none of which imply that one project derived from the other: There is even a place where GraphTally went a step further. High-frequency payment is only half the problem; the harder half is settling all that activity onchain without the fees swallowing the value. GraphTally's answer, aggregating many Receipts into a single RAV so that a large batch of micropayments settles in one transaction, is precisely the optimization a network serving hundreds of thousands of queries a day cannot live without. It is the kind of detail you only solve when you are running the system for real. The two systems are not rivals; they are complementary layers of the same pipeline, and The Graph runs both. Subgraphs on The Graph Network now accept x402 payments directly. At the consumer-facing layer, x402 lets agents and applications pay a Subgraph Gateway for per-query access in USDC over HTTP, with no API key, account, or session. At the layer beneath it, GraphTally is the system that lets Indexers accept trust-minimized payments from those gateway operators for the queries they actually serve. A request can flow end to end as machine-native payment: an agent pays a gateway through x402, and the gateway settles with its Indexers through GraphTally. The Graph both helped prove the pattern early and adopts the emerging open standard where it fits, rather than treating the two as a choice. This is the point worth making for a general audience. Permissionless, machine-native payments are not a future feature The Graph is waiting on; they are infrastructure The Graph already builds, ships, and operates at network scale. The Graph set out to pay its own Indexers, and in doing so it battle-tested a piece of the machine-to-machine economy that the rest of the industry is now standardizing in the open.

  24. Published Social post

    The Graph (@graphprotocol)

    Big launch from @PropellerSwap: Turbine brings confidential, direct-to-solver swaps to Ethereum. Powering it is Tycho, their open-source liquidity indexer built on @graphprotocol's Substreams, the highest-throughput way to stream onchain data in real time. Congrats to the team!

  26. Published Social post

    The Graph (@graphprotocol)

    Blockchain data has always been transparent. Accessing it hasn't been. MCP servers and new AI agent skills for both Subgraphs and Substreams mean anyone can now query live onchain data in plain natural language. No GraphQL. No SQL. No custom infrastructure. Here's what's available and what's coming next ⬇️ https://thegraph.com/blog/querying-blockchain-data-natural-language-mcp-skills/

  33. Published Social post

    The Graph (@graphprotocol)

    How The Graph Network's Economics Are Evolving in 2026 Decentralized infrastructure is only sustainable if the economic model that supports it actually works. Token incentives can bootstrap supply, but long-term viability requires that the demand side grows to match, and that the mechanisms connecting supply and demand create real alignment between participants. The Graph Network has operated as a two-sided market since launch: Indexers and Delegators on the supply side, developers and applications on the demand side. The Technical Roadmap addresses structural improvements to both sides. The Supply-Demand Imbalance The Graph's token incentive mechanisms have been effective at scaling supply. Indexers have joined The Graph Network, deployed infrastructure, and served data. But the demand side has historically been constrained by the size of the addressable market: blockchain developers building on Subgraphs. The expansion of The Graph's product suite changes that calculus. Substreams serves DeFi protocols and analytics platforms. Token API serves wallets and block explorers. Amp targets institutions and regulated enterprises. Tycho serves trading systems and solvers. Each product reaches a different audience, and together they expand the total demand that flows through The Graph Network. Rewards Eligibility Oracle (REO) The Rewards Eligibility Oracle is one of the most structurally significant changes in the roadmap. Its purpose is to establish a proof-of-work standard that ties Indexing rewards to demonstrated value delivery rather than token holding. Under the current model, Indexers receive rewards partly based on their stake, which does not always correlate with the quality or volume of data they actually serve. REO introduces a measurable standard: Indexers must demonstrate they are actively and accurately serving data to qualify for rewards. This change is planned for both Subgraphs (Q1) and Substreams (Q4), with additional data services to follow. For the network, REO means that rewards flow to participants who are genuinely contributing to the quality of the service. For Indexers, it creates clearer incentives to invest in infrastructure performance. Direct Indexer Payments (DIPs) DIPs introduce a flexible protocol mechanism that allows consumers, chains, and ecosystem participants to pay Indexers more directly for their work. Rather than relying solely on protocol issuance and query fees, DIPs create additional revenue pathways that can be targeted toward specific data services or workloads. For Indexers, DIPs represent additional income streams tied to specific value delivery. For data consumers, they provide a mechanism to ensure their preferred data services are well-served by the network. Liquid Staking The liquid staking initiative addresses a specific friction point for large token holders and centralized exchanges: the complexity of participating in network delegation. The initiative aims to offer a native API in a single interface for centralized exchanges, making it easier for their users to delegate GRT without navigating multiple steps or interfaces. The rollout follows three phases: testnet in Q2, mainnet in Q3, and a Morpho launch in Q4. Cross-Chain GRT Utility GRT has been bridged to Arbitrum, Base, and Avalanche via Chainlink's CCIP protocol, with Solana planned. This expansion of where GRT can be held and used increases its utility across the broader ecosystem and makes participation more accessible for users on different chains. The Aligned Incentive Thesis Underlying all of these changes is a consistent logic: economic mechanisms should reflect and reinforce actual value creation. REO ties rewards to proof of work. DIPs more directly connects Indexer income to consumer demand. Liquid staking makes participation more accessible. Cross-chain expansion makes the token itself more useful. The goal is a network where every participant's economic interest aligns with the health and growth of the overall system. The 2026 roadmap is a significant step toward that model.

  35. Published Social post

    The Graph (@graphprotocol)

    Crypto's Toughest Data Problems (And How The Graph Is Solving Them) Blockchain data is broken in ways most people don't see until they're deep inside the problem. At a recent panel on the hardest challenges in crypto data at Blockworks Digital Asset Summit, a question came up early: Is indexing a solved problem? The short answer is no. The longer answer explains why The Graph has spent seven years building, and why the 2026 Technical Roadmap looks the way it does. Here are the real problems, and where the solutions stand. Problem 1: Standardization is harder than it looks A transaction is a transaction. A transfer goes from A to B. Simple enough on the surface. But across 70+ blockchain networks, different virtual machines, different client implementations, and hundreds of protocol-specific contracts, nothing is really standardized yet. DEX trades alone required integrating against more than 150 protocols before any coherent data format emerged. Every vertical has its own version of this problem. And every time a standard feels settled, a new protocol arrives that doesn't fit. The Graph has been at the center of this since 2018, when Subgraphs became the first widely adopted open standard for indexing smart contract data. The open-source framework that came from that work is now used across web3 by thousands of developers. This reflects a deliberate commitment to open standards as infrastructure that belongs to the public, not to any single provider. The work isn't finished. As institutions enter the space, new standards are needed at the semantic layer: how token assets are classified, how metadata is structured, how data is named and described so that it travels cleanly across organizations and regulatory environments. The Graph 2026 Technical Roadmap directly addresses this, with a continued focus on network-first chain integration, expanded chain coverage, and data services designed to meet institutional requirements out of the box. Problem 2: Speed and scale broke the old model Three years ago, the core user of blockchain data infrastructure was a small to mid-sized DeFi team. Subgraphs served them well. The query volume was manageable. The chains were slow enough that sequential indexing kept up. That model hit a wall. High-throughput chains like Solana, Base, and BSC generate transaction volumes that sequential processing cannot keep pace with. Teams that needed to keep their frontend data fresh, run live analytics, or feed AI agents in real time found that the API-based model had a ceiling. The paradigm shifted from custom APIs to streaming. Substreams was built to solve exactly this. Parallelized processing, cursor-managed reconnection that never drops a data point, and latency in the 600ms to 1900ms range for trading and AI applications. What previously took weeks to reprocess can now be completed in hours. One analytics platform, Amberdata, saw a 72,000% performance improvement over its previous RPC-based infrastructure. The 2026 roadmap advances Substreams toward full protocol integration via Horizon, with trust-minimized payments, a provider selection mechanism, and a decentralized service architecture built for the teams that need blockchain data at the highest throughput. Problem 3: Quality is not the same as consensus Early approaches to blockchain data quality relied on determinism. If multiple independent providers index the same data and return the same result, the output can be trusted. That logic holds in principle. In practice, it has limits. Different Ethereum client implementations return different results for the same transactions. RPC providers have overlapping data sets without the redundancy and diversity that genuine decentralization requires. The underlying assumption that consensus equals accuracy turns out to be more fragile than it appears, especially when the raw input data itself may be inconsistent across providers. The thinking has evolved. The new frontier is cryptographic verifiability. Amp, developed by The Graph core dev Edge & Node, is the product built to clear that bar. A blockchain-native SQL platform with cryptographic verification from the block level up, built-in data lineage, audit-ready provenance, and enterprise-grade deployment options. The goal is a system where data quality is not assumed through agreement but proved through cryptography, and where a compliance team can trace any output back to its source without a blockchain engineer in the room. This is the infrastructure that makes blockchain data usable in regulated environments: payments, treasury oversight, risk management, and AI-driven automation where garbage in means serious consequences on the other side. Problem 4: The customer changed The institutionalization of the industry didn't just change who was buying data. It changed what the data needed to do entirely. The DTCC processes quadrillions in assets annually. It is now confronting a world where it needs position data across hundreds of chains within 5 seconds of each transaction settling. That is not a DeFi startup problem. That is not a problem Subgraphs alone were designed to solve. It is the problem The Graph's 2026 product suite was designed to scale toward. The DTCC's Great Collateral Experiment used The Graph's technology. Major financial institutions are not waiting for the infrastructure to mature. They are building now, and the data layer has to be ready. The Architecture Behind It All Each of these problems requires a different solution. No single indexing approach serves all of them. That is why Horizon matters. Launched in December 2025, Horizon transformed The Graph from a Subgraph-centric protocol into a modular platform where multiple purpose-built data services operate within a single economic and security framework. Subgraphs for structured, queryable APIs across 70+ networks. Substreams for high-throughput real-time streaming. Token API for pre-indexed token data without custom infrastructure. Tycho for real-time onchain liquidity data across DEXs. Amp for verifiable, SQL-native, enterprise-grade data with full audit lineage. Each service purpose-built. All of them operating within one protocol. The hardest problems in blockchain data don't have one answer. They have a stack. And building that stack, openly and at scale, is what The Graph has been doing since the start.

  36. Published Social post

    The Graph (@graphprotocol)

    Token API and the Case for Pre-Indexed Blockchain Data Nearly every consumer-facing blockchain application requires token balances, prices, transfers, swaps, and NFT metadata. Wallets need it. Block explorers need it. Portfolio trackers, marketplaces, and analytics dashboards all need it. The data requirements are not exotic or protocol-specific. They are standards that provide the backbone to most blockchain applications today. The problem is that until recently, accessing this standard data still required teams to build and maintain custom indexing infrastructure. That is a significant engineering investment for data that is fundamentally the same across thousands of applications. What The Graph Token API Does Differently The Graph’s Token API provides pre-indexed, production-ready access to common token data across multiple chains through a standardized interface. Rather than requiring teams to define indexing logic, deploy infrastructure, and manage uptime, Token API delivers the data directly. Built on the same Substreams infrastructure that powers high-performance streaming on The Graph Network, Token API benefits from the parallel processing architecture and low-latency delivery that Substreams enables. The result is token data that is both standardized and performant, available across 10 networks with continued expansion planned. Who is the Token API Designed For? Token API is not a replacement for Subgraphs. Subgraphs remain the right tool for protocol-specific custom indexing, where the data structures and events are unique to a particular smart contract system. Token API is for applications where the data model is already known: balance lookups, price feeds, transfer histories, and NFT ownership. The typical users are wallet developers, block explorer teams, and analytics platforms that need fast, reliable, consistent token data without maintaining the infrastructure to produce it. For teams in this category, Token API removes a significant operational burden. The 2026 Technical Roadmap Two milestones define Token API's trajectory in 2026 at The Graph. Production-grade latency on 10 networks, already underway in Q1, establishes the baseline performance standard the service is designed to maintain. Real-time token pricing with DEX and chain expansion in Q3 adds a new data category: live price feeds sourced from decentralized exchange activity. The addition of real-time DEX pricing is meaningful because it closes a gap in what Token API can serve. Current token price data often lags or requires integration with separate price oracles. Sourcing pricing directly from DEX activity gives applications access to market prices that reflect actual onchain liquidity, with the latency characteristics that real-time products require. Standardization as Infrastructure One of the less obvious benefits of a service like Token API is what it enables at the ecosystem level. When dozens of applications pull token data from the same standardized source, data consistency improves across the ecosystem. Portfolio trackers agree on balances, marketplaces show consistent pricing, and users see the same numbers regardless of which application they open. In a space where data fragmentation is still common, a shared, reliable source for standard token data is a meaningful coordination improvement.

  39. Published Social post

    The Graph (@graphprotocol)

    Subgraphs Defined the Standard. What Comes Next? When The Graph launched Subgraphs, the goal was to give developers a reliable, queryable layer on top of raw blockchain data. What followed was an entire ecosystem built around that standard. Thousands of protocols, dapps, and analytics platforms now rely on Subgraphs as their primary data access method. That adoption reflects how much friction Subgraphs removed from the development process. What a Subgraph Actually Does A Subgraph is a standard for how to index and query data from a blockchain. Developers specify which smart contracts to watch, which events to track, and how to transform that raw event data into a database and structured API. Once deployed, the Subgraph is served by Indexers who process queries and return results in real time. The result is a GraphQL API that applications can query directly, without needing to run their own nodes, parse raw logs, or maintain custom infrastructure. For teams building DeFi protocols, NFT marketplaces, or governance dashboards, Subgraphs compress weeks of engineering time into hours. Why the Focus is Shifting in 2026 The Graph Technical Roadmap introduces two meaningful shifts in how Subgraphs evolve. The first is around quality and economic alignment. The Rewards Eligibility Oracle (REO) establishes a proof-of-work standard, ensuring that Indexers receive rewards in proportion to the value they actually deliver, rather than as a passive function of token holding. The Direct Indexer Payments (DIPs) mechanism gives consumers, chains, and ecosystem participants a flexible way to incentivize Indexers directly. Together, these changes tighten the relationship between service quality and economic reward to improve the quality of The Graph’s Subgraph Service. The second shift is toward AI compatibility. The roadmap introduces x402-compliant gateways and support for MCP (Model Context Protocol) and A2A (Agent-to-Agent) communication protocols. This means AI agents running in tools like Claude, Cursor, or ChatGPT will be able to query Subgraphs using natural language, autonomously pay for queries per-use, and receive structured blockchain data without requiring API keys or manual setup. This is a meaningful extension of what Subgraphs can serve, moving from developer-facing infrastructure into a layer that AI systems can natively access and use. Amp-Powered Subgraphs Later in 2026, Amp is introduced as an extraction and transformation layer that accelerates Subgraphs. Rather than replacing the Subgraph model, Amp improves it at the data pipeline level, making indexing faster and more efficient. This integration is part of a longer arc toward building infrastructure that can serve institutional-grade workloads without sacrificing the open, permissionless access that defines The Graph's approach. The Bigger Picture Subgraphs have been the foundation for The Graph protocol because they solved a real problem elegantly. The work ahead is not about replacing that foundation; it is about extending it to serve a broader set of users, agents, and systems as the blockchain data landscape matures.

  41. Published Social post

    The Graph (@graphprotocol)

    The Graph Foundation's 2025 Annual Grants Report is live, revealing the strategic investments that enabled Horizon and positioned The Graph for multi-service expansion in 2026. ▶️ Horizon launch: Protocol upgrade ▶️ Token API: Production-grade infrastructure serving developers, wallets, and AI agents ▶️ AI integration: Subgraph MCP enabling natural language queries of blockchain data ▶️ Dispute resolution: Multi-stage system strengthening protocol governance ▶️ Community growth: Korean market doubled, global developer education expanded ▶️ Critical infrastructure: Chain integrations, Indexer tooling, and network support Lifetime grants: $16.8M supporting ecosystem growth since inception. Can’t wait to see what 2026 brings!

  42. Published Social post

    Wu Blockchain (@WuBlockchain)

    Coinbase Markets announced that on March 16 at around 13:00 UTC, it will suspend 25 perpetual contract trades on Coinbase Advanced and Coinbase International Exchange, including MET-PERP, REZ-PERP, SUSHI-PERP, GMX-PERP, GRT-PERP, and ARKM-PERP. All open positions will be automatically settled at the time of suspension. https://x.com/CoinbaseMarkets/status/2028802616939909185

  43. Published Social post

    Coinbase Markets 🛡️ (@CoinbaseMarkets)

    Trading for the following perpetual futures will be suspended on Coinbase Advanced and Coinbase International Exchange on March 16 on or around 13:00 UTC. • MET-PERP • REZ-PERP • BABY-PERP • SUPER-PERP • SUSHI-PERP • GMX-PERP • ERA-PERP • XAN-PERP • VINE-PERP • T-PERP • YB-PERP • WCT-PERP • HOME-PERP • NOT-PERP • MINA-PERP • CATI-PERP • DOGS-PERP • COW-PERP • GRT-PERP • DRIFT-PERP • COOKIE-PERP • ARKM-PERP • B3-PERP • SXT-PERP • BB-PERP Any remaining open positions will be settled automatically at the time of suspension. The final settlement price will be calculated as the average index price over the 60 minutes prior to the trading suspension. The funding rate will be set to zero for the final funding period before final settlement. Coinbase reserves the right to suspend trading at any point and adjust the final settlement price to a reasonable level.

  44. Published Social post

    The Graph (@graphprotocol)

    🤖 How are AI agents coming to The Graph Network this year? Subgraphs will support: ✓ x402-compliant payment gateways ✓ MCP integration for @claudeai, @cursor_ai, @ChatGPTapp ✓ A2A (Agent-to-Agent) protocols ✓ Natural language blockchain queries

  45. Published Social post

    The Graph (@graphprotocol)

    x402 has a gas problem. If an agent pays $0.0001 for a data query but network fees are $0.05, the economics break. GraphTally (the micropayment system from The Graph) solved this by introducing cryptographically signed vouchers that settle in batches onchain later. Agents can now make thousands of queries per minute without gas fees blocking every microtransaction. This same innovation has contributed to the x402 specification, making it viable for blockchain use cases. The result: agents can pay for Subgraph queries using x402, transforming The Graph into a data marketplace for the agent economy

  46. Published Social post

    The Graph (@graphprotocol)

    The Graph 2026 Technical Roadmap just dropped ⚙️ Blockchain data infrastructure is maturing into a multi-service platform that serves everyone from solo devs to global financial institutions. Here's what's coming from The Graph🧵

  48. Published Social post

    The Graph (@graphprotocol)

    At the end of 2025, The Graph shipped Horizon, the most significant protocol upgrade since the network launched. Why Horizon matters and what it enables ⬇️ ▶️ Horizon transforms The Graph from infrastructure built for one service (Subgraphs) into a modular platform that can support any type of blockchain data service. Same battle-tested foundation. Expanded capabilities. ▶️ Before Horizon: Staking, payments, and verification were built specifically for Subgraphs. ▶️ After Horizon: Those same components become reusable primitives that any data service can leverage. ▶️ For developers, Horizon means access to an expanding suite of data tools, all running on the same decentralized infrastructure. Subgraphs. Substreams. Curated APIs. Analytics. And services that haven't been built yet. ▶️ More data services = more protocol activity. More opportunities for Indexers. More utility for GRT. Horizon is the foundation for that growth. Horizon was the infrastructure upgrade. What comes next is building on it.

  49. Published Social post

    The Graph (@graphprotocol)

    The Graph's Substreams delivers Flashblocks on Base mainnet, giving developers execution-level data as soon as it's available. @base is pushing the boundaries of what's possible with fast block times and high throughput. Real-time data for real-time chains.

  50. Published Social post

    The Graph (@graphprotocol)

    Horizon opens The Graph’s standard protocol infrastructure to any data service. It launched on December 9th, but the implications will reverberate for months to come. Here’s how it’s going ⬇️ ✅ 100.00% of all active Indexers are active on Horizon, utilizing some or all their stake to serve subgraphs via Horizon. ✅ 99.39% of all queries are now served via Horizon. ✅ 90.33% of all Indexer stake is migrated to Horizon. The transition period isn’t over, but the adoption of Horizon is already a huge success: ➡️ 668 million queries have been served in the last 10 days ➡️ Total of 684 million GRT staked

Showing 50 of 380 stories · Page 1 of 8. Filters apply to the full news archive.