Starknet
Firehose chain-specific configuration for Starknet
This page covers Reader Node configuration specific to Starknet. For general Firehose architecture and deployment, see the Single Machine Deployment or Distributed Deployment guides.
Firehose for Starknet uses an RPC poller approach. You can either run your own Starknet node or use an RPC provider. For node setup, refer to the official Starknet documentation.
Docker Image
ghcr.io/streamingfast/firehose-starknet:<version>View available versions on GitHub Packages
The image contains the firecore and firestarknet binaries.
Binary & Releases
Download releases from the GitHub releases page.
Networks
Starknet Mainnet
starknet-mainnet
Starknet Sepolia
starknet-sepolia
Architecture
Firehose for Starknet uses an RPC poller approach. The poller fetches blocks from Starknet RPC endpoints and converts them to Firehose format. It also requires an Ethereum L1 endpoint for finality information.
Reader Node Configuration
Starknet Mainnet
Starknet Sepolia
Key Poller Flags
fetch
Subcommand to run the RPC poller
{first-streamable-block}
Variable substituted from --common-first-streamable-block
--state-dir
Directory to store poller state
--starknet-endpoints
Starknet RPC endpoint URL
--eth-endpoints
Ethereum L1 RPC endpoint for finality
--block-fetch-batch-size
Number of blocks to fetch in parallel
--interval-between-fetch
Delay between fetch cycles
Resources
Last updated
Was this helpful?
