📺 Graph Office Hours #284 is up
🟣 REO Step 4 is live
🟣 Base moves from Studio to the Network
🟣 Curation burns rise from 1% to 3%
🟣 Subgraph Gateways will launch soon
➕ Many more updates from The Graph ecosystem
Replying to @base
@base Subgraphs are moving to The Graph Network.
Phase 1 moved 860+ @BNBCHAIN and @0xPolygon from Subgraph Studio with no major issues.
Now, Base is next and here's what you need to know. 🧵
More query volume is coming to The Graph Network.
Here is what is happening, starting with @BNBCHAIN and @0xPolygon. 🧵
No GRT needed to curate. An automated curation bot detects newly published Base Subgraphs and adds signal, so Indexers pick them up.
This ensures high quality of service for those developers moving onto The Graph Network
Subgraph Studio will still be the path to deploy, manage versions, and publish to the Network as usual.
Details: forum.thegraph.com/t/base-su…
The Graph retweeted
Elysium brings 100ms blocks and trading at Hyperliquid's pace.
If your router is slower than 100ms, you sign a stale route for every trade.
On @Enter_Elysium Fynd solves 98% of routes in <5ms, long before the next block, making Fynd by far the fastest router on Elysium.
📺 Graph Office Hours #283 is up
✅ REO Step 4 from Nov 17: work scales with stake
✅ Base is next for Studio to Network
✅ Elysium on Substreams
✅ Multi-Gateway Subgraph Service next steps
➕ Many more updates from The Graph ecosystem
Forum Recap: forum.thegraph.com/t/graph-o…
YouTube: youtu.be/G27HIxbsW30
Elysium is live. The Graph and Substreams, built by @streamingfastio, support it from day one.
@Enter_Elysium streams as extended blocks from genesis: internal calls, native HYPE balance changes, and storage writes, with no RPC polling at 100 ms blocks.
Get started at substreams.dev.
Building on @Enter_Elysium at launch?
Don’t write your own indexer.
Substreams streams decoded Elysium data directly into your database, at whatever granularity you need, from entire blocks down to a single event.
Live from genesis.
StreamingFast is proud to be a launch partner.
Step 4 from November 17th: Indexers would be required to index either the greater of 10 Subgraphs or 1 Subgraph for every 4M GRT. Only Indexers above 40M GRT see a change in this next step.
The end goal would be 1 qualifying Subgraph per 1M GRT. At 100M GRT, that is 100 Subgraphs. The ratio rises in steps each with at least 14 days’ notice.
📺 Graph Office Hours #282 is up
✅ REO: Two-month retrospective
✅ REO Step 4: Requirements start to scale based on stake starting on Nov 17th
✅ Multi-Gateway Strategy: A deep dive
➕ Many more updates from The Graph ecosystem
The Graph protocol’s Rewards Eligibility Oracle is two months in. REO is designed to direct rewards towards the Indexers providing value to end consumers:
1. Moving fast: 3 steps in 9 weeks
2. Removing under-performing Indexers: Eligible Indexers dropped from 70 → 55 in Step 1, then 55 → 48 at 5 Subgraphs
3. Making the protocol more efficient: ~667K GRT from failing Indexers went to the reclaim contract instead
All of it makes the on-chain data service high quality and more cost effective.
23 hours → 7 minutes 36 seconds.
The same Uniswap v4 data on Ethereum, indexed with Substreams on 75 parallel workers.
Amazing work as always by the @streamingfastio team.
From 23 hours to under 8 minutes.
That’s how long it took to index Uniswap V4 on Ethereum, subgraph vs Substreams, in a benchmark run by BuildersDAO (@GraphBuilders). 182x faster, on 75 parallel workers.
On Base: 94 hours down to 2h 06m. Push to 300 workers and it’s 56 minutes — 100x.
We just built the SQL sink straight into the Substreams CLI: one binary, pass a package and the mode is auto-detected.
Migrating is painless: cursors and schemas are unchanged, so no re-sync.
The Substreams skill for AI coding agents knows the new commands too.
Full breakdown + benchmark tables, and thanks to The Graph’s BuildersDAO for running this experiment: streamingfast.io/blog/substr…











