Ethereum
Firehose chain-specific configuration for Ethereum and EVM chains
Last updated
Was this helpful?
Firehose chain-specific configuration for Ethereum and EVM chains
This page covers Reader Node configuration for Ethereum and EVM-compatible chains. For general Firehose architecture and deployment, see the Single Machine Deployment or Distributed Deployment guides.
This guide does not cover how to sync an Ethereum node. For node synchronization, storage requirements, and network configuration, refer to the official documentation of your chosen client.
The fireeth binary includes all firecore functionality plus Ethereum-specific features and commands. Download releases from the GitHub releases page or use published Docker images from GitHub Container Registry.
For Reader Nodes, each network provides bundle Docker images containing both fireeth and the network's Firehose-patched node binary. See the network-specific guides below for Docker image references.
Firehose for Ethereum supports Geth and Geth forks. Each network requires a Firehose-patched version of its client:
Ethereum Mainnet, Sepolia, Hoodi
Arbitrum One, Nova
Base Mainnet, Sepolia
BNB Smart Chain
Katana
Optimism Mainnet, Sepolia
Polygon PoS
Unichain
Monad Mainnet
Worldchain
All Ethereum-based networks share these characteristics:
Only --advertise-chain-name needs to be specified. All other advertise fields (block ID encoding, chain aliases, etc.) are automatically derived from The Graph Network Registry.
The Firehose-patched Geth (and forks) require the --vmtrace=firehose flag to emit Firehose Protocol logs to stdout.
Last updated
Was this helpful?
Was this helpful?
--advertise-chain-name="<chain-name>"fireeth start reader-node <apps> \
--reader-node-path="<path-to-geth-binary>" \
--reader-node-arguments="--vmtrace=firehose --datadir={node-data-dir} <network-flags>" \
--advertise-chain-name="<chain-name>" \
<other_flags...>