Explore the code No node to operate
Not for history, not for the head.
Access by chain
Query the chain.
Skip the node.
History and live data for the chain you work on, in one stream, with no node to run and no indexer to maintain.
- One stream
- History and head
- No node to run
- Open source
Ethereum → Firehose → Substreams → PostgreSQL
Interactive illustration
StreamingFast
ecosystem
01 Access by chain
Looks familiar?
The plan starts with standing up an archive node, and the node is not the product.
On top of it, an indexer, which is the part nobody budgeted.
Then the second chain arrives and you find out whether you built a pipeline or a one-off.
Want to see the chain you are building on?
Explore the chains
RUST → WEBASSEMBLYThe chain changes. The path does not.
Every chain has its own quirks, and none of them should cost you a new stack. The same extraction, decoding and delivery path serves each supported network, so adding a chain is a configuration decision rather than a project.
Read the guideFilterMapAggregateDeliver
▧ substreams.yamlPACKAGE STRUCTURE
01 specVersion: v0.1.0
02 package:
03 name: token_transfers
04 version: v0.1.0
05
06 modules:
07 - name: map_transfers
08 kind: map
09 inputs:
10 - source: sf.ethereum.type.v2.Block
11 output:
12 type: proto:transfers.Transfers Illustrative excerpt Build a complete package ↗
What you get
Existing packages
Start from what someone already wrote for that chain.
One path per chain
The second chain costs a fraction of the first.
Flat files included
Take the raw output if that is what your stack wants.
Open source
The decoding you depend on is readable.
02 Access by chain
How it works
FROM HISTORY TO THE CHAIN HEAD
Historical blocksNew blocks
TRANSACTIONS
TRACES & LOGS
STATE CHANGES
Rich block data. One continuous stream.
Pick the chain
Check which networks are served before planning around one.
Start from a package
Rather than decoding the chain yourself.
Sink it where you work
Files, a database, or your own consumer.
Want to see the chain you are building on?
Explore the chains03 Access by chain
What you stop owning
[01]
An archive node per chain
[02]
An indexer per chain
[03]
The refactor the second chain forces
Access by chain
Start on your chain, today.
Read the guide ↗Retrieve complete blockchain history
Define coverage, plan the backfill and verify the dataset before you rely on it.