Accelerating The @Graphprotocol. Firehose and Substreams core devs.

Canada
Hosted Sinks can now serve your Substreams data over a read-only GraphQL API and console. Powered by Hasura Auto-tracks your tables Just one checkbox to enable. Outgrowing a Subgraph? Taking the next step to Substreams no longer means giving up your GraphQL query layer. streamingfast.io/blog/serve-…
Made with AI
6
10,512
Hosted Stores are live on The Graph Market. Substreams turns raw chain data into structured output. But when a module needs to look something up mid-stream (an off-chain price, token metadata, an address→owner map), you were stuck recomputing it in every pipeline or running your own key/value service that stays correct through reorgs. Hosted Stores removes that. It's a managed, block-aware key/value store StreamingFast runs for you: • Keys = raw bytes. Values = your protobuf messages. • Every read targets a block and stays in sync with the stream, backfills included. • Reachable over gRPC, or as a foundational-store input in any Substreams module. Two ways to fill it: → Remote feed: your service pushes data in over gRPC. Good for off-chain price feeds, allowlists, identity data. → Substreams feed: a package populates it from chain data. Compute token metadata or a pool registry once, reuse it across every pipeline. It joins Hosted Sinks under Hosted Services, the managed side of Substreams. Sinks push data OUT to your database. Stores hold data you look UP inside your pipelines. You operate neither. Beta. Works end to end today. Blog: streamingfast.io/blog/hosted… Docs + feedback: docs.substreams.dev/how-to-g…
Made with AI
1
3
5
8,700
StreamingFast ⏫ retweeted
Earlier this year, The Graph Foundation published the Technical Roadmap, Part 1 of a two-part series on the future of The Graph. Here’s Part 2: the official announcement of the Foundation’s new mandate, and how the Foundation will bring that roadmap to life. thegraph.com/blog/new-founda…
14
34
182
35,560
Agents are now building on Substreams end-to-end. So why are you still coding by hand? → Machine-readable OpenAPI spec for the substreams.dev registry. No more scraping HTML to find packages → 9 open-source Substreams Skills for Claude Code, Cursor or your favorite coding agent → Agentic access to @graphprotocol’s The Graph Market — check usage, manage keys, monitor sinks from your terminal Details in blog: streamingfast.io/blog/leveli…
2
2
12
18,661
Getting on-chain data into a database has always been the annoying part — provisioning servers, babysitting a sink, handling reorgs. Hosted Sinks kills that work. Point it at a Substreams package + your Postgres or ClickHouse DB, click Deploy, and we run it for you. Zero ops. Try it out on @graphprotocol's thegraph.market Live in minutes 👇 streamingfast.io/blog/hosted…
8
6,813
Great work from many teams at @ETHGlobal Lisbon. Check out this project that monitors across multiple protocols to detect malicious activity in real-time, leveraging Substreams as a data source
Best AI Tooling for The Graph at @ETHGlobal Lisbon. $5,000 for reusable infrastructure that makes The Graph easier to build with from AI environments. Not apps. Tools the next builder gets to keep. Three winners ⬇️
4
370
Find it, and many others, on the public Substreams Registry here substreams.dev/packages/robi… Community supporting community!
The first substreams for @RobinhoodApp Chain tokenized stocks now streams the full data layer: scaled transfers (correct ERC-8056 ui_value), @chainlink fair prices, and @Uniswap V4 swaps.Everything you need to build on onchain stocks, in one substreams.dev/packages/robi…
3
247
StreamingFast ⏫ retweeted
> Turbine answers the question of how can we have large trades settle onchain at a price that is as good or better than a centralized exchange. @apriori0x cooked on this episode of Deeply Intents with @haikane. A lot of defi trading micro-structure alpha in here. ✨
Markus and team may have solved trading for institutions onchain. Everyone in the Ethereum community should be paying attention. In particular, one of the reasons so many large traders are not trading on chain is price impact. Turbine answers the question of how can we have large trades settle onchain at a price that is as good or better than a centralized exchange. 🤯 This is a significant unlock for large CEX traders, liquid funds, whales, and institutions who want to come onchain to trade SIZE. Large Funds don't care about executing every second. They care about executing at a good price. Turbine cares about price and not speed. Tommy Lee, Joe Lubin, Etherealize, Ethlabs and anyone working towards institutional adoption of Ethereum would be wise to take note here. Markus doesn't always do podcasts or yell from the rooftops about what he is building. When he does, you should listen.
3
11
979
Good prices come to those who wait Privacy, security, better spreads. What more could a trader want? Congrats on the launch of Turbine to the whole @PropellerSwap team!
The best place for large trades is now Ethereum. Introducing Turbine.
1
8
741
The chain data you need, in your database, backed by a world-class backend. Getting on-chain data into your database is now the easy part via @graphprotocol's The Graph Market. Hosted Sinks is a fully managed Substreams-sink-as-a-service. You point it at a Substreams package and a database, click Deploy, and we run it for you, at scale, securely, with zero ops on your side. Chain data to your tables, live, in minutes, then query it with the SQL tools you already know. --- What it does Bring your Substreams package, pick PostgreSQL or ClickHouse, and hit Deploy. That's it. Fresh chain data starts streaming into your tables, and we keep it running, backed by our highly-available and highly-reliable distributed infrastructure. Running a different kind of sink? Let us know so we can prioritize it! Transactional data for your app, columnar analytics for your dashboards, your choice. Works on all chains available on The Graph Market: Ethereum, Base, Solana, and beyond. No new runtime on your infrastructure, no blockchain plumbing: your Substreams package maps protobuf straight into relational tables, and you read it back with plain SQL. You already have a database, let us connect and fill it for you. --- How your team benefits Spin up in minutes, not sprints. Deploy, start, stop, and delete on demand — all self-service from the portal. No infrastructure to provision. Always correct, fork-aware. Substreams tracks the canonical chain and signals reorgs automatically, so chain reorgs never leave sheared or stale data behind. Inserts, updates, and upserts keep mutable data current. No manual cleanup. Update without downtime. Edit your package or config in place and we roll it out gracefully. Need a clean slate? Reset and re-sync from your start block. Secrets stay secret. Your database credentials live in HashiCorp Vault, never in code or config. Injected at runtime, with built-in disaster-recovery export/import. Multi-tenant by design. Every deployment is isolated to your organization: strict, enterprise-grade separation out of the box. Full visibility. Live status, per-instance health, and a complete deployment history — created, scaled, updated, restarted — all in the dashboard. --- What does it cost Billing is the same as it currently is, pay only for the data coming out of your Substreams. For the next 6 months, we’ll manage the sink for free. After this initial period, each sink will incur a negligible cost per month, confirmed before billing begins. The bottom line Stop staffing a platform team to move blockchain data into a database. Hosted Sinks abstracts away the credential management, the scaling, and the re-sync headaches and gives you back a simple form and a Deploy button. Check the docs to get started today docs.substreams.dev/how-to-g… Your data. Your database. Our infrastructure. Live in minutes.
4
17
2,660
If you build on Substreams, you've been getting faster data. We moved our reader nodes to @OVHcloud Bare Metal — 2-3x lower blockchain head latency, uptime measured in months, and faster catch-up on demanding chains like Solana and Base. Less waiting, more building. ovhcloud.com/en-ca/case-stud…
4
4
18
2,638
Congrats to the @PropellerSwap team! Quality work being done by a quality team 💪
.@UniswapFND gives a grant for Tycho and Fynd to: Make Uniswap pool simulations really fast (down to 900 ns per pool quote). Index >100k Uni pools with 0 inconsistent state, even on Flashblocks and reorgs. Make v4 hooks tradable minutes after deployment. More soon.
4
259
StreamingFast ⏫ retweeted
Replying to @streamingfastio
the only way to get flawless chain state
1
2
252
Congrats to the @PropellerSwap team on your launch of Fynd! Powered by Substreams under the hood ⚡️ That’s how you get this level of speed—parallelized, streaming-first data pipelines delivering real-time performance at scale.
2
1
12
479
StreamingFast ⏫ retweeted
Traditional financial institutions are building on blockchains. They need data infrastructure that meets compliance requirements, handles high throughput, and runs reliably at scale. Substreams was built for this.
7
16
110
3,416
StreamingFast ⏫ retweeted
Kudos to the @streamingfastio team for continuing to make Substreams faster and faster. The team is doing great work to support the @graphprotocol
Substreams on @graphprotocol is getting even faster! The SQL sink (substreams-sink-sql) and core substreams-sink have been refactored to use the new V4 Blocks Streams protocol + S2 compression (replacing GZIP). What’s new? V4 protocol: Switches to repeated BlockScopedDatas → enables batching of blocks from server to client (only during catch-up/backfill). S2 compression: Up to 30% better ratios than GZIP + 7–10× faster CPU-wise. Real gains Batching + S2 → up to 30% extra compression (vs. old 2–4% without batching). Result: Much faster sink times — especially historical reprocessing & initial syncs! Update now to take advantage: Substreams CLI & libs → latest substreams-sink-sql → latest These are live on StreamingFast endpoints — clients auto-negotiate. Faster indexing awaits! Check the changelog: github.com/streamingfast/sub…
3
6
308
Substreams on @graphprotocol is getting even faster! The SQL sink (substreams-sink-sql) and core substreams-sink have been refactored to use the new V4 Blocks Streams protocol + S2 compression (replacing GZIP). What’s new? V4 protocol: Switches to repeated BlockScopedDatas → enables batching of blocks from server to client (only during catch-up/backfill). S2 compression: Up to 30% better ratios than GZIP + 7–10× faster CPU-wise. Real gains Batching + S2 → up to 30% extra compression (vs. old 2–4% without batching). Result: Much faster sink times — especially historical reprocessing & initial syncs! Update now to take advantage: Substreams CLI & libs → latest substreams-sink-sql → latest These are live on StreamingFast endpoints — clients auto-negotiate. Faster indexing awaits! Check the changelog: github.com/streamingfast/sub…
2
8
34
2,428