Recording: https://youtu.be/vswfnKQ9UZs
Host: BK from The Graph Foundation
Here is a summary of this week’s Graph Office Hours. This summary is written from the deck. Check it against the recording before posting.
Rewards Eligibility Oracle: Step 4 is live
Indexers above 40M GRT total stake: Check your Step 4 number on the dashboard. Count the Subgraphs you serve qualifying queries on each day, and keep headroom.
Step 4 will go live with tomorrow’s 10:00 UTC oracle run. It is the first step of Phase 2, which scales work with stake. The 10 largest Indexers hold about 70% of total stake and received about 71% of indexing rewards (stake as of November 2; rewards paid August 2 to October 29).
The rule: Required qualifying Subgraphs is now the greater of 10 or 1 Subgraph per 4M GRT in stake. Only Indexers above 40M GRT total stake see a change.
| Total stake | Step 3 | Step 4 | End goal |
|---|---|---|---|
| 30M GRT | 10 | 10 | 30 |
| 50M GRT | 10 | 13 | 50 |
| 100M GRT | 10 | 25 | 100 |
| 200M GRT | 10 | 50 | 200 |
- Total stake is GRT provisioned to the Subgraph Service plus delegation to it, counted up to the 16x delegation ratio. Thawing GRT does not count.
- Serve, not sync: the count is Subgraphs that you serve qualifying queries on.
- Full effect by December 1: eligibility renewed before today stays valid for the rest of its 14-day period.
- Unchanged: 5 or more online days in a rolling 28-day window. A qualifying query returns HTTP 200, responds in under 5,000 ms, and comes from an Indexer within 50,000 blocks of chainhead.
The end goal stays 1 qualifying Subgraph per 1M GRT of total stake. The roadmap in the video shows Steps 5 to 7 as projected. Each later step will be announced with at least 14 days’ notice and the data from the step before. No criteria changes are planned over the holiday period.
- Status for every Indexer: https://reo.thegraph.com/
- Criteria and changelog: rewards-eligibility-oracle/ELIGIBILITY_CRITERIA.md at main · graphprotocol/rewards-eligibility-oracle · GitHub
- Discussion: REO Step 4: Requirements Begin to Scale with Stake
Studio to Network: Base
Developers: Publish Studio-only Base Subgraphs to The Graph Network by December 1. Indexers: Sync those Base Subgraphs as they hit the network.
Base was officially announced on November 16 as Phase 2 of moving Subgraph Studio traffic to The Graph Network. Phase 1 moved more than 860 BSC and Polygon Subgraphs with no major issues reported.
| Date | What happens |
|---|---|
| November 16-17 | Announcement; batch curation and the curation bot begin |
| December 1 | Studio-only Base Subgraphs must be published |
| December 1-15 | The Foundation adds signal where needed |
- Already on The Graph Network? No action is needed. If your app still queries a Studio URL, switch it to the Gateway endpoint.
- Studio-only? Publish each Subgraph (a one-time transaction on Arbitrum One), set up billing and an API key in Subgraph Studio, and switch your app to the Gateway endpoint. You do not need GRT to curate. A curation bot signals on newly published Base Subgraphs.
- Subgraph Studio: Developers can still deploy Base Subgraphs to Studio and manage versions there. The main change is that the staging environment no longer supports syncing.
- Indexers: Base is a large chain with 200ms blocks, so plan capacity. The coverage list comes in
#indexer-announcements. Flag sync issues in#indexers.
Publishing guide: Publishing a Subgraph to the Decentralized Network | Docs | The Graph
Curation burns rise from 1% to 3%
The governance vote passed. The transaction executes late November 17 or early November 18 (EST). The burn applies on deposit: new signal, added signal, and signal that migrates on an upgrade. Withdrawals have no burn.
For Indexers: The Arbitration team wants to discourage self-signaling and signal cycling. In dispute 0x9347e202, the PoIs were valid and real indexing work was done, so slashing was not possible. The higher curation tax signals the team’s disapproval of rapid signal rotation. Self-curation stays allowed. Re-signaling 129k GRT now burns about 3,870 GRT, up from about 1,290 GRT.
For Developers: Publishing with signal costs slightly more:
| Signal | Burned at 1% | Burned at 3% | Added cost |
|---|---|---|---|
| 1,000 GRT | 10 GRT | 30 GRT | about USD 0.34 |
| 2,000 GRT | 20 GRT | 60 GRT | about USD 0.67 |
| 10,000 GRT | 100 GRT | 300 GRT | about USD 3.36 |
USD figures use about USD 0.0168 per GRT (Coinbase, November 16). The recommendation is at least 1,000 GRT of signal on every Subgraph, so that multiple Indexers pick it up. DIPs is not affected by the curation burn.
GRT burns: Every signal deposit now burns three times as much GRT.
Multi-Gateway Subgraph Strategy
Status of each workstream:
- Provider Collaboration Framework: While still in progress, a working draft is guiding ongoing GTM launches. The tiered model for external gateways covers Enablement, Endorsement, and Expansion. It is projected to finish by the end of December.
- Multi-Gateway Alignment: Complete as of early November.
- Gateway QoS Endorsement: Phase 1 is complete. Endorsed gateways publish a change log, a blocklist, and per-Indexer QoS data. Phase 2 is projected for February 2027. This framework will likely be outlined in more detail in next week’s Graph Office Hours.
- Powered by The Graph brand guidelines: A draft is available, but still being finalized.
What’s next: A public launch of Subgraph Gateways is expected in the next two weeks with two design partners’ gateways to follow. Any team can run a Subgraph Gateway on The Graph Network under its own brand, pricing, and support, while independent Indexers do the indexing. Each new gateway’s sender must be whitelisted by Indexers before it can send queries.
Graph Node updates
There was no Graph Node release this week.
- gnd and runtime fixes: gnd keeps nullable fields set to 0 or false (#6760), and each WASM module is now hashed once instead of once per data source (#6732).
- Gateway fixes: query durations are reported in seconds, counters start at zero, and Indexer feedback uses observed progress.
- dipper v0.2.9 to v0.3.1: five releases. v0.3.0 changes the admin API (paged indexing-request list). Signed admin requests are hardened, and price ceilings are capped at the agreement limit.
- DIPs Indexer selection v2.11.0 to v2.15.0: five releases. Selection now combines freshness checks through the gateway, per-chain uptime and success, and latency into one score.
- graph-network-subgraph: effective cuts are now computed on active stake and delegation.
Substreams updates
- Substreams v1.27.0:
substreams runandguioffer to log in, andsubstreams authsaves a long-lived API key (SUBSTREAMS_API_KEY) instead of an expiring JWT. The release includes a migration guide, SQL sink fixes, and security fixes. Releases · streamingfast/substreams · GitHub - firehose-ethereum v2.25.0: new transaction types for Base account abstraction (EIP-8130) and the OP Stack post-exec type (Lagoon), plus a configurable tier1 status page.
- firehose-solana v1.6.0 and substreams-solana v0.17.0: SIMD-0123 block revenue sharing, sub-second block time from the Alpenglow block footer, and account transaction indexes.
- firehose-core v1.21.2: the final release after two release candidates, with reader upload-backlog metrics, merged-blocks tooling fixes, and a compression library CVE fix.
Chain updates
Changes from networks registry v0.8.9 to v0.8.14:
- New: Elysium (v0.8.13). Kinetiq’s Layer 2 for Hyperliquid is supported on Substreams and Firehose by StreamingFast. Elysium has no Subgraphs support and is not eligible for indexing rewards.
- zkSync Era adds Substreams (v0.8.14). Pinax added Firehose and Substreams endpoints. Subgraphs with indexing rewards continue on The Graph Network.
- BSC and Polygon: Network only (v0.8.11). Subgraph Studio no longer indexes these networks. The Foundation curates published Subgraphs, and indexing rewards continue.
- Removed: Blast, Starknet, Starknet Sepolia, and Robinhood Chain Testnet have no providers left and are dropped from Supported Networks. Robinhood Chain mainnet is unaffected.
- Base: v0.8.14 still lists a Studio entry. The registry update is pending.
Registry: GitHub - graphprotocol/networks-registry · GitHub
Docs updates
PR #1129 (still in review) merges the Subgraph How-to Guides into one Guides & Best Practices section:
- A new overview page with a performance checklist and a map of the section
- Pages reordered and rewritten: contract design, schema, storage and queries, debugging and grafting, composition, then migration
- One Grafting page for hotfixes and contract replacement, and Tooling renamed to Testing & Tooling
- Supported Networks synced to registry v0.8.14, and old guide, cookbook, and grafting-hotfix URLs redirected
Review the PR: Base to network by brandonleekramer · Pull Request #1129 · graphprotocol/docs · GitHub
Adjacent ecosystems
Scheduled (dates come from project docs and news coverage and can change):
- November 23, Stellar Protocol 30 “Bell” mainnet vote (17:00 UTC): live on testnet since November 3. Adds muxed contract addresses and millisecond ledger close times. Update XDR definitions and SDKs.
- December 2, Telcoin Network genesis: a new EVM layer 1 for stablecoin payments.
- December 3, OP Stack Lagoon on OP Sepolia and Unichain Sepolia: Superchain interop and post-exec transactions. The mainnet date is pending governance.
- December 8, BNB Chain Jenner (02:30 UTC): BSC v1.8.2 is mandatory. Adds CAS20 precompiles, a payment lane, and millisecond time through precompile 0x70.
- Base, next upgrade: native account abstraction (EIP-8130). No date yet; firehose-ethereum v2.25.0 already supports the new transaction type.
Watch list:
- Polygon recovery fork (proposed): would zero about 70.5M POL in five blocked addresses at a fixed block, with no transfer event. Balance indexers that rebuild state from transfers would need an adjustment. No fork block is set.
- Ethereum Glamsterdam: no new Hoodi date after the EIP-8037 review. Mainnet is unconfirmed.
- Polymarket Protocol V2: new markets move to V2 contracts, and V1 positions do not convert. The cutover is not yet confirmed.
Open floor
Questions or feedback? Reply below, or join the next call on Tuesday at 17:00 UTC on the Discord stage.