_dao-chains-parameters
1. Parent chain (Ethereum) parameters
The --parent-chain.connection.url parameter needs to provide a standard RPC endpoint for an Ethereum node, whether self-hosted or obtained from a node service provider:
--parent-chain.connection.url=<Ethereum RPC URL>
Additionally, use the parameter --parent-chain.blob-client.beacon-url to provide a beacon chain RPC endpoint:
--parent-chain.blob-client.beacon-url=<Ethereum beacon chain RPC URL>
If you choose to self-host an EVM node, the Prysm client software is a great choice. It's straightforward, efficient, and effective—ensuring your setup runs smoothly!
You can also consult our list of Ethereum beacon chain RPC providers. Note that historical blob data is required for these chains to properly sync up if they are new or have been offline for more than 18 days. The beacon chain RPC endpoint you use may also need to provide historical blob data. Please see Special notes on ArbOS 20: Atlas support for EIP-4844 for more details.
2. Arbitrum chain parameters
Use the parameter --chain.id to specify the chain you're running this node for. See RPC endpoints and providers to find the IDs of these chains.
--chain.id=<Arbitrum chain ID>
Alternatively, you can use the parameter --chain.name to specify the chain you're running this node for. Use arb1 for Arbitrum One, nova for Arbitrum Nova, or sepolia-rollup for Arbitrum Sepolia.
--chain.name=<Child chain name>