Substreams builders: 0.8.0 is live, and new projects from substreams init already use the core advantages.
Modules pinned to 0.7 keep building and streaming. When you’re ready to upgrade, follow the migration guide: docs.substreams.dev/referenc…
Substreams 0.8.0 is out, and we replaced the protobuf codec, making it 2.9x faster. 🔥
prost → buffa. Blocks decode 2.9–4.9x faster.
Real backfills: → uniswap-v4 map_events, 1.5M Ethereum blocks: 342s → 118s → solana-idl-history map_idl_accounts, 1.5M Solana blocks: 846s → 384.5s
Every module decodes the block before it runs a line of its own logic: once per block per module. A chain with 10 active modules decodes every block 10 times over.
Wire format unchanged, upgrading opt-in.
Learn more in the blog post streamingfast.io/blog/substr…
This is what The Graph hoped builders would do with x402.
@vAPI_Network turned The Graph's x402 gateway into a few CLI commands. Install, fund a wallet with USDC on @base, and your agent is querying Subgraphs.
Great demo by @MarkTbuilds 🔥
From setup to your first paid API call. See vAPI Call in action.
Our protocol lead @MarkTbuilds walks through installation and demonstrates Call using @graphprotocol as a showcase provider, with USDC payments on @base powered by x402.
Replying to @iban_ginto
Really interesting to see the work you are doing here! @streamingfastio has been engaging with what you are doing on the technical side. Thanks for supporting The Graph.
Love seeing teams like @vAPI_Network build on x402 to open The Graph to AI agents.
vAPI Call lets anyone query Subgraphs and pay per query in USDC on Base, straight to through The Graph’s canonical gateway. No account, no API key.
Agents will pay per query, so data has to be meterable. Builders and agents can get started here:
The Graph is now part of our Verified Provider selection!
Buy onchain data from @graphprotocol for your agent, paid per call through vAPI Call.
22 data sources live, only 0.01 USDC per question.
Integrate our MCP to try The Graph today: mcp.vapinetwork.ai
The Graph ecosystem regained momentum in Q3 2026
With its new mandate, The Graph Foundation now runs the Gateway, Studio, and Explorer. Its first move is to send more developer demand to Indexers. All BNB Smart Chain and Polygon traffic will move from Subgraph Studio to The Graph Network starting tomorrow, October 8th.
Learn about this effort and more in The Graph's Quarter in Review post: thegraph.com/blog/q3-2026-in…
The sports calendar is stacked. MLB playoffs, the WNBA Finals, NBA tipoff, and a full NFL slate every Sunday.
Every market on it is an onchain event on Polymarket, and it's already indexed on The Graph.
Query it with Subgraphs. Stream it with Substreams. Or call the Token API.
thegraph.com/blog/prediction…
Ink + The Graph
@inkonchain is now fully streamable on The Graph with Substreams on the Extended block model: thegraph.com/docs/en/support…
Extended Blocks give you full call traces, native balance changes, storage diffs, and contract code changes, the data DeFi on Ink runs on, not just base-block logs.
Built by @PinaxNetwork: core contributors to The Graph ecosystem.
Ink now streams extended blocks on Pinax Firehose and Substreams.Every internal call, native ETH balance change, storage write and contract deployment on @inkonchain, not just logs.
Live now in the Pinax app: app.pinax.network
Developer traffic moves onto The Graph Network, Indexers who serve now earn the rewards, and the Foundation steps in as operator to grow the network.
Full breakdown, the data model, and how to check any chain: thegraph.com/blog/extended-b…
Extended blocks are live on Ethereum, Base, BNB Smart Chain, HyperEVM, Arc, Robinhood, Polygon, Arbitrum One, OP Mainnet, Unichain, Linea, Monad, and more. Check your chain on The Graph's Supported Networks page: thegraph.com/docs/en/support…
Getting this from RPC means debug_traceTransaction, the trace_ namespace, or state-diff tracers across archive state. Expensive, throttled, often gated behind premium tiers or off entirely. Extended blocks capture it at execution time, for every block.
Why Substreams Extended Blocks matter:
🔵 Internal calls: accurate accounting for routers + aggregators, MEV/trace analysis
🔵 Balance changes: exact native-balance history
🔵 Storage diffs: index state that emits no event
🔵 Code changes: track contract deployments across the call tree
An extended block comes from full node instrumentation. It carries what RPC hides: internal calls (the full call tree), balance changes, storage diffs, and contract code changes. On a base block those fields come back empty. On an extended block, they're just there.
A base block is what an RPC endpoint exposes: blocks, transactions, receipts, logs. Fast for a chain to adopt, and enough for most event-based indexing. It's a big reason so many chains get Substreams support.
Substreams take another route. Firehose extracts every block once into flat files, read in parallel. No per-call rate limits, no missed events on reconnect, same input to same output every time. On EVM chains that extraction comes in two shapes: base and extended.
Let's learn about the Substreams Extended Blocks to help get blockchain data from The Graph.
Most projects run on a thin slice of the blockchain. An RPC gives you blocks, transactions, receipts, and logs. The moment the data you need isn't in a log, you're reaching for trace endpoints that are slow, metered, and often switched off.
ICYMI: The Graph now supports @arc.
Arc uses USDC as gas, so payments, FX, and settlement are the chain's ordinary data. Two ways to index it:
→ Subgraphs: query Arc with GraphQL
→ Substreams: stream it in real-time
Build on Arc: thegraph.com/docs/en/support…
The Graph supports @Arc from day one.
What The Graph unlocks for Arc:
🟣 Publish Arc Subgraphs on The Graph and query it with GraphQL
🔵 Stream Arc data in real-time using Substreams with full call-trace and state-change data (via Extended Blocks support)
The Graph helps developers and institutions index data from Arc to advance a range of use cases – from stablecoin payments to tracking tokenized real-world assets and agentic workflows.
Build on Arc: thegraph.com/docs/en/support…
🟢 ICYMI: Anubis is now indexable on The Graph.
Subgraph support is live on The Graph Network for @AnubisChainL1 — a privacy-focused, EVM-compatible L1 doing 1M+ transactions a day.
Index DeFi, RWA & payments data, query it with GraphQL: thegraph.com/docs/en/support…
Huge thanks and congrats to @PinaxNetwork for building on the Extended Blocks support for @HyperliquidX EVM and their continued support of @graphprotocol and Substreams.
HyperEVM on Substreams just moved from base blocks to extended blocks support.
That means internal calls, balance changes, and storage changes in the stream, not just logs. Native HYPE that moves inside a call is now indexable via The Graph’s Substreams.
Get started: thegraph.com/docs/en/support…
New in the Pinax app: HyperEVM extended blocks.
Our Firehose and Substreams endpoints now carry every internal call, native HYPE balance change and storage write on HyperEVM, not just logs. We built the node instrumentation ourselves.
Get an API key: app.pinax.network












