Networks and nodes
Starknet networks and nodes
Last updated
Was this helpful?
Starknet networks and nodes
Last updated
Was this helpful?
A few public Starknet networks are live, and are uniquely identified as follows:
starknet-mainnet
Ethereum mainnet
The main canonical Starknet where valuable assets are stored
starknet-sepolia
Ethereum Sepolia testnet
The latest testnet which developers are encouraged to use
starknet-goerli
Ethereum Goerli testnet
The original testnet which will be deprecated soon
starknet-sepolia-integration
Ethereum Sepolia testnet
A canary network for SDK and node developers
starknet-goerli-integration
Ethereum Goerli testnet
A canary network for SDK and node developers
Tip: Firehose does not know or care about the assigned identifiers. These identifiers are useful only in and .
It's also possible to run a vastly simplified Starknet network for local development. The is a popular option.
Note that since these networks aren't real Starknet, it's not possible to synchronize a full node with such a network. However, this does not mean it's impossible to run a Firehose stack on such a network, as you can use the .
All instrumented nodes are available in 3 different distributions:
as a standalone Docker image (supports both AMD64 and ARM64) where the node binary is available as the entrypoint;
as a firehose-starknet Docker image (supports both AMD64 and ARM64) where firestark is the entrypoint, but the node binary is available on PATH;
and of course, as source code that you can directly compile from.
pathfinderA Starknet node implemented in Rust.
Standalone Docker image (multi-arch)
firehose-starknet bundled Docker image (multi-arch)
Source code
junoA Starknet node implemented in Go.
Standalone Docker image (multi-arch)
firehose-starknet bundled Docker image (multi-arch)
Source code
jsonrpc-to-firestarkA pseudo node that does not actually synchronize with the network. Instead, it relies on a trusted JSON-RPC endpoint on an existing synchronized full node to collect and emit the same data format expected by Firehose to the standard output.
This pseudo node exists because currently Starknet full nodes cannot synchronize through P2P, but instead only from a centralized sequencer API, which is heavily rate-limited. Having to synchronize from scratch via the sequencer could take an extended period of time. jsonrpc-to-firestark significantly speeds up the process if there's an already-synchronized node under the same network.
An additional use case for jsonrpc-to-firestark is to "synchronize" with local development networks where full nodes cannot be used.
Standalone Docker image (multi-arch)
firehose-starknet bundled Docker image (multi-arch)
Source code
Note: Precompiled binaries are not available at the moment. However, you can always for the entire stack.