Graph Office Hours #280 (October 20, 2026)

General
1

Recording: https://youtu.be/3s7zL3BPM6U Host: BK, with Orjan and Samuel from The Graph Foundation

Here is a summary of this week’s Graph Office Hours. Timestamps point to the recording.

Chain integrations (01:01)

Deprecations

  • October 16: near-mainnet and near-testnet are deprecated.
  • October 19: fuse, fuse-testnet, and fantom. Fantom usage had dropped to almost nothing except historical queries. A few teams still use historical data from Fantom Subgraphs, and Ellipfra has helped support those.
  • October 21: soneium, soneium-testnet, kaia, kaia-testnet, zksync-era-sepolia, arbitrum-nova, monad-testnet, and viction (newly added this week).
  • November 2: botanix and botanix-testnet, to honor the end of the agreement with that team.

New and upcoming

  • The Foundation chain integration blog post is still coming. It will clarify the Foundation’s position on chain integrations.
  • BK is coordinating with several Indexers on Network about Robinhood Chain Subgraph support. More next week.

Studio to Network migration (03:22)

BSC and Polygon Subgraph traffic moved from Subgraph Studio to The Graph Network, and Studio support ended on October 8. The migration went well. Starting October 20:

  • The upgrade Indexer unallocates from about 214 Subgraphs that are already supported on the Network.
  • 551 inactive Matic/BSC Subgraphs are deleted.

No user issues have been reported so far. This gives the traffic back to Network Indexers.

Indexer software (04:42)

indexer-agent and indexer-cli v0.25.12 are out. Indexers should upgrade. The release brings more complete fee collection, clearer provision errors, and an updated feature support matrix with better docs. Thanks to Tomas and Carlos. Questions go to Tomas in #indexer-software on Discord. Release notes: Release v0.25.12 · graphprotocol/indexer · GitHub

Graph Node (05:46) is in a stabilization phase as it moves from Edge & Node to InfraDAO. Two experienced Graph Node engineers are active. For the next one to two months, the focus is open community PRs, critical fixes, security patches, and dependency updates. New features come later if they become a priority.

Substreams 0.8.0 (06:57)

Substreams 0.8.0 moves Rust protobuf bindings from prost to buffa. Blocks decode 2.9x to 4.9x faster depending on the chain, and backfills finish up to 2.9x faster. Nothing changes downstream. The upgrade is opt-in.

vAPI on The Graph (09:16)

vAPI is a marketplace where AI agents find and pay for data sources. It now lists The Graph, with roughly 15 to 20 Subgraphs. Queries run through The Graph’s x402 gateway and settle in USDC on Base, with no API key needed. See vAPI’s walkthrough on X.

In Q&A (18:48), BK explained the pricing. vAPI charges $0.01 per query, compared with the Network’s baseline of about $20 per million queries. vAPI keeps the difference, which fits the Foundation’s support for multiple gateways. One clarification: vAPI runs a gateway business on top of The Graph’s canonical gateway and x402. It does not run its own Subgraph gateway infrastructure for routing and Indexer payments. More AI marketplaces like this are expected, and growing AI usage is a priority for the coming months.

Rewards Eligibility Oracle (11:11)

On Tuesday, October 27, the Daily Query Requirement rises from 5 to 10 qualifying Subgraphs. Quality of service thresholds stay the same. Samuel’s modeling shows eligible Indexers dropping from 48 to 42. Further changes depend on how the Network responds after the 27th.

Direction under discussion (14:15): Oriana described making eligibility dynamic, scaled to total stake (including delegation). For example, a requirement of N Subgraphs per million GRT staked, with a floor. At 0.1 per million, an Indexer with 100M GRT stake needs 10 Subgraphs, which matches today. At 1 per million, it would need 100. The goal is to be efficient, not punitive: indexing rewards should go to Indexers who provide real value. Nothing is decided. The team wants to see how the October 27 change settles and wants community feedback first.

Community input from the chat (31:21):

  • Matthew suggested letting Indexers shed stake to downsize, for example by removing self-stake or not counting over-allocated or over-delegated stake. This only changes the calculation, not the protocol.
  • Some discussion on how to reward Indexers who specialize instead of serving everything.

Dashboard: https://reo.thegraph.com/

Ongoing Foundation initiatives (22:22)

Most of the Foundation team’s time goes to these three:

  • Multi-Gateway Plan: how the Foundation will run its canonical gateway and work with external gateways (BD, marketing, docs, product). The proposal is in a strong first draft and goes to The Graph Council for review this Thursday. The hope is to finalize it within a few weeks, depending on Council feedback.
  • Subgraph Studio pricing: Pedro is leading a simpler pricing model. Optimistically about a month away, but it could take three to five months to roll out.
  • Liquid Staking: still in Phase 1 and moving toward Phase 2. Avantgarde, which operated the vault day to day while the Foundation managed it, announced last week that it is winding down. The Foundation is lining up a new operator and expects to finalize a plan internally next week. In Q&A (34:10), Oriana confirmed that some funds were spent with Avantgarde. Their fees were time-based, not a large upfront cost, so the loss is limited. External partners have shown interest, and the team thanked Avantgarde for its work.

Upstream protocol upgrades (25:37)

Changes in other ecosystems that affect Indexers, Subgraphs, and Substreams:

  • Solana Alpenglow: StreamingFast is already up to date. Little to no impact on Substreams or Token API is expected.
  • Aero (October 22): Aerodrome and Velodrome merge into Aero across seven chains. Existing Aerodrome and Velodrome Subgraphs and Substreams keep working, but liquidity will move to Aero over the following weeks, and Aero needs new Subgraphs and Substreams. About 63 Subgraphs are likely affected. BK is contacting the teams behind the most-used ones. If you want to help build Aero Subgraphs, reach out to BK. Upgrade hub: Upgrade and Launch Hub — Aero
  • Unichain to OP Enterprise: the chain ID and addresses stay the same, so no impact is expected.
  • Polymarket V2: a new Subgraph was introduced (Graphtronauts), and the V1 API will be deprecated over the coming month or so.
  • Also on the radar: Ethereum Glamsterdam, Base, and Avalanche upgrades.
  • ENSv2 activation on Ethereum L1: see below.

ENSv2 (28:52)

ENSv2 brings a new registry design, and cutover follows the “Activate ENSv2” DAO vote (closes October 25). If you run an app on ENS data, plan your upgrades. To BK’s knowledge, apps on the current ENS Subgraph should keep working without major code changes. BK will confirm whether any move to the new Subgraph is needed.

In Q&A (32:44): no Graph Node changes are expected for ENSv2. BuildersDAO and the Foundation worked with ENS on an ENSv2 Subgraph schema that also covers ENSv1, for continuity. An estimated 90 to 95% of that work is done, so the Subgraph should be ready when ENS launches. BK will double-check with the Graph Node team.

ENSv2 readiness checklist: Preparing for ENSv2 | ENS Docs

Open floor

Abel, the long-time host of these calls, dropped by to say hello. Recordings are on The Graph’s YouTube channel under Indexer Office Hours.

Questions or feedback? Reply below, or join the next call on Tuesday at 17:00 UTC on the Discord stage.