copy and paste this google map to your website or blog!
Press copy button and paste into your blog or website.
(Please switch to 'HTML' mode when posting into your blog. Examples: WordPress Example, Blogger Example)
Edge Nodes September October 2025 Update Monitoring for The Graph’s CCIP integration is now set up Studio Explorer Engineering Added internal diagnostic tools to aid ongoing Studio billing operations support Implemented bug fix for Studio to address minor issue switching key status for a payment edge case Continued Explorer testing and fixes for Horizon update Graph Node: v0 40 1
Edge Nodes March April 2025 Update - Core Team Updates - The Graph 👩🚀 Executive Summary March and April brought record consistency in Network usage by combining for ~4 5 billion queries This consistency comes alongside April bringing all-time highs for both query volume and active paying wallets on Studio The successful launch of Token API, swiftly integrated into Claude, Cline, and Cursor for AI-assisted crypto wallet and price data solutions
GraphOps Update June 2025 - Core Team Updates - The Graph 👩🚀 Executive Summary For Subgraph MCP, our team was focused on refining the core system, adding Prometheus metrics and iterating on top of the GraphWow agent We proudly supported the beta launch of Graph Assistant at EthCC and engaged with the broader community at the ETHGlobal hackathon, helping hackers to use The Graph’s AI suite On the Kubernetes Launchpad front, a new version
Pinax September 2025 Update - Core Team Updates - The Graph 👩🚀 Summary Pinax has made lots of progress on the Token API since our last update, bringing new features like NFT spam scoring, and a whole bunch of new Solana endpoints to market We’ve also seen significant improvements to data quality and syncing performance, allowing us to ship new features faster Looking ahead, we’re working hard towards the launch of paid plans and
Edge Node May 2025 Update - Core Team Updates - The Graph 👩🚀 Executive Summary In May 2025, Edge Node made a number of notable contributions to The Graph ecosystem -ranging from new features on Subgraph-related products to marketing efforts campaigns several products, chain integrations, and new partnerships The E N Engineering team completed several critical initiatives, including the rollout of a new Studio billing platform, security
Edge Node July 2025 Update - Core Team Updates - The Graph 👩🚀 Executive Summary The last month saw strong ecosystem engagement for Edge Node Hypergraph in particular received a lot of DevRel, marketing, and business development support from the E N team in addition to our technical contributions We also saw major progress toward Horizon deployment, both on the technical front and in preparing the Council to approve its deployment
Introducing New Council Member: Jonathan Alexander The Graph Foundation is pleased to welcome Jonathan Alexander as the newest member of The Graph Council Jonathan brings over two decades of experience in software engineering, infrastructure leadership, and web3 innovation He has already begun actively participating in protocol discussions and GIPs, and his perspective will be instrumental as The Graph scales and shapes the future of
Graph Council Meeting #111 - Ecosystem Updates - The Graph Council members value transparency and have agreed to follow Chatham House Rules for sharing meeting notes On November 13th 2025, The Graph Council held its 111th meeting Roster Adam Fuller Sebastian Lorenz Santiago Palladino Derek Meyer Chris Wessels Observers and Note Taker Andrew Clews, The Foundation Nick Hansen, The Foundation Pedro Diogo, The Foundation Jacob Flowers, The Foundation
Proposal: Explore x402 for Future Data Services on The Graph As The Graph expands beyond subgraphs, a key challenge will be frictionless monetization of new data services Today, most access is gated by API keys, credits, or centralized gateways The x402 protocol (HTTP 402 Payment Required) offers a simple, standardized way to handle per-query payments directly at the HTTP layer Instead of issuing API keys, a server can respond with a 402, the client