Chain Specific

Chain-specific Firehose configuration guides

This section contains chain-specific configuration guides for Firehose. Each guide covers the Reader Node configuration required to extract blockchain data for that particular chain.

Before reading these guides, ensure you understand the general deployment concepts from:

• Single Machine Deployment - For development or small-scale deployments

• Distributed Deployment - For production deployments

Supported Chains

EVM Chains

Ethereum and EVM-compatible chains use fireeth and share similar configuration patterns:

Chain	Type	Notes
Ethereum	Native Firehose	Mainnet, Sepolia, Hoodi
Arbitrum	Native Firehose	Requires L1 connection
Base	Native Firehose	OP Stack, requires OP Node
BNB Smart Chain	Native Firehose	BSC Geth fork
Katana	Native Firehose	OP Stack
Optimism	Native Firehose	OP Stack, requires OP Node
Polygon	Native Firehose	Bor client
Unichain	Native Firehose	OP Stack
Worldchain	Native Firehose	OP Stack
Avalanche	RPC Poller	C-Chain via RPC
Sei	Native Firehose	Cosmos SDK + EVM

Non-EVM Chains

These chains use firecore with chain-specific binaries:

Chain	Type	Notes
Injective	RPC Poller	Cosmos SDK chain
NEAR	Native Firehose	NEAR Protocol
Solana	Geyser Plugin	Solana validator plugin
Starknet	RPC Poller	Requires Ethereum L1 RPC
Stellar	RPC Poller	Soroban RPC
Tron	RPC Poller	Native and EVM formats

Integration Types

Native Firehose

Chains with native Firehose instrumentation have a patched blockchain client that outputs block data in Firehose format. This provides the most complete data extraction.

RPC Poller

For chains without native instrumentation, an RPC poller fetches blocks from standard RPC endpoints. You can use your own node or an RPC provider.

Geyser Plugin

Solana uses a Geyser plugin that hooks into the validator to extract block data.