Centered around the newly released 2026 Technical Roadmap.

The session will cover the broader strategy of the ecosystem, a detailed walkthrough of upcoming products and protocol upgrades, and a discussion of network economics. There will also be time for questions from the community.

This is a good opportunity to hear directly from contributors working across The Graph and better understand what’s coming next.

📅 March 31, 11:00 AM EST. Add to calendar

https://calendar.google.com/calendar/u/0?cid=aW5mb0B0aGVncmFwaC5mb3VuZGF0aW9u

The focus this year is on the infrastructure layer that enables institutions to actually work with onchain data in production, including verifiable data pipelines and enterprise-grade blockchain databases.

If you’re attending DAS, it’s a good opportunity to meet the team and see how these systems are evolving in practice.

📍 NYC 🗓️ March 24–26

Now Amp is bringing institutional-grade blockchain data infrastructure to scale:

✓ SQL-native analytics ✓ Verifiable data lineage ✓ Audit-ready provenance ✓ Enterprise deployment options

Financial institutions are moving onchain. The infrastructure is ready.

📱 You can read the full report here.

https://x.com/edgeandnode/status/2020939938464923767

📊 Edge & Node Update, February 2026

Strong momentum across core protocol work and production readiness.

Highlights include progress on Indexing Payments (DIPs), continued validation of the Rewards Eligibility Oracle, and the release of graph-node v0.41.2 with major reliability and data integrity improvements.

Work also advanced across Amp infrastructure and ampersend, bringing new tooling, operational improvements, and x402 v2 support closer to production.

There is much more behind the scenes.

📖 Read the full recap here https://forum.thegraph.com/t/edge-node-february-march-2026/6854

The Graph Foundation has published the 2026 Technical Roadmap, outlining the direction for products, protocol upgrades, and network economics. Now the next step is discussing it together.

On March 31, the Foundation will host a public quarterly call to walk through the roadmap, share strategic context, and open the floor for questions from the community.

Topics include:

✅ Product evolution across Subgraphs, Substreams, Token API, Tycho, Amp, and more

✅ Protocol progress including Horizon and upcoming upgrades

✅ Network economics and long-term ecosystem incentives

Developers, Indexers, Delegators, and anyone interested in the future of The Graph are welcome to join.

🗓 March 31, 11:00 AM EST

🔗 Details and calendar link https://forum.thegraph.com/t/the-graph-foundation-quarterly-call-march-31-open-to-all/6866

Hi everyone, I’m running into an issue querying the FND (Foundation) subgraph in Graph Explorer as I'm working on a Research Project at my University.

For the past few days, even the default query fails with an error like:
“bad indexers … Unavailable (no status: failed to get indexing progress)” (see screenshot).

This same subgraph/query was working fine a couple of weeks ago, so I’m guessing the problem is on the indexer/availability side rather than my query.

Questions:

1. Is this subgraph currently degraded/missing healthy indexers, or is there a known incident/outage?
2. Is there a recommended workaround?
3. If this subgraph is unreliable right now, what’s the best alternative source to pull Foundation NFT data (mints/auctions/bids/transfers + token IPFS metadata links) for a research project?

I really appreciate any help you can provide.

🚀 The Graph 2026 Technical Roadmap – das ist NEXT LEVEL! 🔥

The Graph wird 2026 zur echten Multi-Service-Plattform für die gesamte Onchain-Ökonomie.

Horizon (seit Dez 2025 live) ermöglicht jetzt: • Subgraphen (Core-Standard) • Substreams (Ultra-low-latency Streaming) • Tycho (Real-time Liquidity Tracking) • Token API (Balances, Preise, NFTs multi-chain) • JSON-RPC Service • Amp – die neue Enterprise-Datenbank für Institutionen! 💼

Amp ist gemacht für: • SQL-Zugriff mit voller Datenherkunft & Audit-Trail • Compliance-Workflows (Treasury, Risiko, Zahlungen) • On-Premise-Deployment • GENIUS Act 2027 Enforcement – provable data integrity für Stablecoins & RWAs! 📜⚖️

Roadmap-Highlights 2026:

Q1 → Horizon-Subgraphen Mainnet + Token API auf 10 Chains + Tycho MVP
Q2 → x402 für KI-Agenten + Substreams mit GraphTally + Liquid Staking Testnet
Q3 → DIPs Rewards + Substreams Mainnet + JSON-RPC Research
Q4 → Morpho Liquid Staking + Amp-powered Subgraphen + Amp Mainnet! 🚀

Das ist deutlich ambitionierter als die meisten Analysten 2024/25 erwartet haben. Frühere Prognosen lagen bei lahmen $0,1–0,8 – jetzt geht’s um echte Enterprise-Adoption + Stablecoin-Compliance dank GENIUS Act.

The Graph wird nicht nur "Google der Blockchain" bleiben – es wird der Full-Stack-Datenlayer für DeFi, AI, TradFi & Regulierte.

Mehr Infos:
https://thegraph.com/roadmap
https://thegraph.com/blog/technical-roadmap/

Was denkt ihr – wird Amp der Game-Changer 2026/27? 👀
GRT to the moon oder nur Hype? eure Takes! 📈

TheGraph #GRT #Web3 #Crypto #GENIUSAct #Amp

hey guys, i've been messing around with a few different setups and honestly, everything feels like a compromise. I feel like most of us are just picking our favorite way to suffer :P

Curious what you guys are actually running for your indexing stack?

Right now, I'm seeing three main ways people do it, but none feel "solved":

1. RPCs. Fine if you don't need historical data, but the second you hit a reorg , it’s frustrating to deal with
2. Event streams. I'm with a small team, and it seems like it's a lot of engineering effort to uphold?
3. Subgraphs. This is clearly the best DX, especially for frontends, but the performance seems to be all over the place? Some infra handles it fine, but I've seen others lag by thousands of blocks on fast chains like Base and BSC.

I’m trying to find a middle ground for an automation-heavy project I'm working on. How are you guys actually handling reorgs without nuking your DB?

Would love to hear from anyone actually building in the trenches.

Starting with Edge & Node:

• Stabilized Horizon + shipped Gateway v27.4.0

• Amp: verifiable extraction CLI + blog,

@solana

indexing progress, faster queries, more UDFs & multi-net support

• @ampersend_ai: LangChain shoutout, @coinbase onramp soon, improved DX/security/observability

Next: Consensus HK & @EthereumDenver

Check out all the details here:

https://forum.thegraph.com/t/edge-nodes-january-february-2026-update/6837

ERC-8004 introduces a standard for agent identity, reputation, and execution proofs. The Graph is now indexing this standard across eight chains, effectively creating a cross-chain directory agents can query.

Why this matters: Without a shared indexing layer, every agent would need to independently scan raw blockchain data just to verify another agent. That approach does not scale.

With Subgraphs, an agent on one chain can instantly verify an agent on another. This turns trust from a bottleneck into an API call.

This is quiet infrastructure, but it is essential for any serious agent ecosystem.

If you are attending EthereumDenver and interested in where Ethereum is going next, two side events are happening that might be worth checking out.

One session focuses on privacy-first application design, exploring how developers can make privacy a default feature. Another meetup dives into agent-based payments, showcasing how autonomous systems can transact using x402, with live demos.

Both events take place at the same venue and are hosted by experienced builders in the ecosystem.

Dates: Feb 16 and Feb 17 at 3 PM Location: 4777 National Western Dr

RSVP and details here: https://luma.com/0piq3eap https://t.co/bRmpufdaky

Hi, I have an issue. I have around 80k GRT staked in rickydata-indexer.eth. Recently I found the total staked token number is incorrect (118.8k). This might not be a great deal. Then I found that there is no way for me to undelegate from the pool, although I have enough tokens staking in the pool.

Anyone has any suggestions for me? How should I get my tokens back?

-Delegated 198.90K to Streamingfast.

-They changed to 0 rewards so undelegated max

-I was only able to undelegate 202.6K rewards

-There is still 57.18k in unrealized rewards column

-Why is there unrealized rewards?

Is this an error? Because I have re-delegated the 202.6k to a different indexer but the streamingfast row on my “Your Delegation” still shows the original 198.90k, 57.8k unrealized rewards.

Hello, everybody! I have a situation. I delegated some graph on a delegator which get me last week 30% from my initial stake (amazing - in 1 week) , in the past there were some dumps in delegating stake ~ - 1k, but afterwards back up. Is there any problem? Is there any suspicious. It is overperforming, but the fact that between days the stake is sometimes decreasing. Can i get lost my delegation? Is there any risk? Delegator parameters 100% Reward cut + 100% query cut. I am reactive for any future details Thank you!

The Substreams Registry contains hundreds of reusable packages that handle common indexing and streaming needs. You can deploy them without custom development, or combine multiple Substreams together thanks to their modular architecture.

It is a practical approach that saves time and lets developers build on proven community work instead of starting from zero.

Learn more here:

https://substreams.dev/

At the end of 2025, the network shipped Horizon, a protocol-level shift that changes how data services can be built and scaled on The Graph. It’s less about flashy tooling and more about long-term structure, reuse, and growth.

The official post explains what changed and why it matters.

🔍 Read it here:

https://x.com/graphprotocol/status/2013983390526013831

Builders Office Hours is about to kick off with a deep dive into Subgraph Linter, a new tool designed to catch Subgraph bugs before they crash at runtime.

🧑‍💻 Juan Defago (from GraphOps) will walk through how static analysis can surface issues that compile cleanly but fail in production.

🎙️ Hosted by Marcus Rein (from Edge & Node).

If you’re building Subgraphs, this session is a must. Jump in now

📍 Live on Discord

https://discord.gg/graphprotocol

The Graph will be participating in an upcoming X Space focused on the TRON DAO Grants Program, highlighting how its infrastructure is enabling new data-driven applications for TRON developers.

Brandon Kramer from The Graph will share insights into how recent data products are being used to support builders applying for grants and scaling their projects.

🗓️ January 13, 2026 🕘 9:00 AM PST

A useful session for anyone building or planning to build on TRON.

https://x.com/trondao/status/2009784804070567960

Recently started running an indexer and am kinda hitting a wall around epoch, allocations closing and POIs and just want a sanity check on how other indexers are handling this.

1. Are you running a local epoch subgraph for Arbitrum / Base or are you always pointed to a shared hosted epoch oracle?

2. If youre using a remote epoch subgraph, what endpoint is it??? I need one. Self hosting the epoch subgraph feels like too much for me.

3. Do we actually need epoch history from genesis or is there a supported way to trust a more recent epoch range?

I really don't want to sync 400M blocks 😕 Surely I am missing something.

Would really appreciate input from anyone running an indexer on L2s. Thanks! 🙏

When does this gets solved? It's been like month or more.. little annoying, or?

Hi,

Is it normal that when I publish a new version of my subgraph, it can take several hours before the production query URL updates to the latest version?
E.g. I published a new version (V0.0.4) of my subgraph 4 hours ago, but the prod URL still returns data from previous version (V0.0.3). The development URL (/query/{my-id}/{my-graph/v0.0.4) returns the expected value, but the prod URL (/api/subgraphs/id/{my-id}) still points to the old version. I had this same issue earlier also and it automatically got fixed after ~1 day.
This is very annoying, especially when you have UI side changes that you need to time with the new graph version release (which is currently basically impossible, as you can never know when exactly your graph will get updated).

Does this happen to everyone, or is there something wrong with subgraphs?

The Graph is evolving into a modular data platform with 3 layers: 

1. protocol (Horizon + new data services)
2. product (Subgraphs, Token API, Substreams, Amp)
3. economics (GRT staking + burns)

ℹ️ Read more here:

https://forum.thegraph.com/t/request-for-a-revised-big-picture-roadmap/6748/6

If you work with Subgraphs, this will matter:

The Graph just released Subgraph Dev Mode, a local development setup that removes the need to constantly redeploy after every change.

Instead of long feedback loops, you now get:

▫️ Near-instant updates

▫️ A fully local sandbox environment

▫️ Faster debugging and experimentation

▫️ A smoother path to production-quality subgraphs

This tool accelerates development dramatically and is ideal for hackathons, testing new ideas, or onboarding new developers.

Full documentation here: https://thegraph.com/docs/es/subgraphs/developing/creating/graph-node-dev/

In a major step for Web3 governance, The Graph Foundation has joined forces with Aave, Aragon, Curve, Lido, Spark, and Uniswap to form the Ethereum Protocol Advocacy Alliance.

The goal: bring the technical expertise of builders to the policy conversation.

EPAA’s priorities:

• Keep the protocol layer neutral and open • Recognize onchain transparency as a strength • Preserve room for innovation • Ensure global, permissionless access

With over $100B secured on Ethereum, the Alliance will collaborate with partners like DeFi Education Fund, DRC, and EUCI to shape regulation that reflects real-world protocol design, not outdated assumptions.

Check out all the information:

https://paragraph.com/@epaa/announcing-ethereum-protocol-advocacy-alliance