Arbitrum
Firehose configuration for Arbitrum One
This page provides Arbitrum One specific configuration. First read the Ethereum general notes for common information.
Docker Image
ghcr.io/streamingfast/nitro:<version>-fh3.0View available versions on GitHub Packages
The image contains both the Firehose-patched Nitro binary and fireeth.
Client Binary
Nitro (Firehose-patched)
Networks
Arbitrum One
arb-one
Arbitrum Nova
arb-nova
Arbitrum Sepolia
arb-sepolia
L1 Dependency
Arbitrum requires access to an Ethereum L1 node (both execution and beacon client) for operation. The L1 connection is used for state validation and blob data retrieval.
Reader Node Configuration
Arbitrum One
Arbitrum Nova
Key Nitro Flags
--execution.vmtrace.tracer-name=firehose
Required. Enables Firehose Protocol output
--chain.id
Chain ID (42161 for Arbitrum One, 42170 for Nova)
--parent-chain.connection.url
Ethereum L1 RPC endpoint
--parent-chain.blob-client.beacon-url
Ethereum L1 beacon client endpoint
Resources
Last updated
Was this helpful?
