githubEdit

Ethereum

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.

circle-exclamation

Binary & Releases

Component
Repository
Binary

The fireeth binary includes all firecore functionality plus Ethereum-specific features and commands. Download releases from the GitHub releases pagearrow-up-right or use published Docker images from GitHub Container Registryarrow-up-right.

circle-info

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.

Supported Networks

Firehose for Ethereum supports Geth and Geth forks. Each network requires a Firehose-patched version of its client:

Network
Guide

Ethereum Mainnet, Sepolia, Hoodi

Arbitrum One, Nova

Base Mainnet, Sepolia

BNB Smart Chain

Katana

Optimism Mainnet, Sepolia

Polygon PoS

Unichain

Worldchain

Common Configuration

All Ethereum-based networks share these characteristics:

Chain Name (The Graph Network Registry)

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 Registryarrow-up-right.

VM Trace Flag

The Firehose-patched Geth (and forks) require the --vmtrace=firehose flag to emit Firehose Protocol logs to stdout.

Basic Reader Node Pattern

Resources

Last updated

Was this helpful?