Ethereum
Configuration options
Below are all the parameters that can be configured for Ethereum networks. Please get in touch if you would like to change any other parameters.
| Parameter | Example Value | Description |
|---|---|---|
| Chain ID | 3151908 | Unique identifier for the network. Used by wallets and applications to ensure they're connecting to the correct chain. |
| Block time | 12 | The time in seconds between consecutive blocks. |
| Gas limit | 30000000 | The maximum total gas allowed in a single block, which governs the total computational effort that can be included per block. |
| Churn limit quotient | 65536 | In Proof-of-Stake, this factor limits how many validators can join or exit per epoch. The “churn limit” is calculated as the number of active validators divided by this quotient. |
| Ejection balance (gwei) | 16000000000 | The minimum balance (in Gwei) below which a validator is forcibly removed from the active validator set. |
| Minimum withdrawability delay | 256 | The minimum number of epochs a validator must wait before being able to fully withdraw its stake after initiating a withdrawal. |
| ETH1 Follow Distance | 2048 | How many blocks behind the head of the chain the beacon node should follow for deposit contract finality. |
| CPU | 2 | Number of CPU cores allocated to nodes. |
| Memory | 4 | Amount of memory (in GB) allocated to nodes. |
| Node count | 1 | The number of nodes (validator or execution) to run. |
| Execution client | Reth | The client that handles transaction execution and state transitions (e.g., Geth, Erigon, Nethermind, Reth, etc.). |
| Consensus client | Lighthouse | The client that handles the Proof-of-Stake consensus logic (e.g., Lighthouse, Prysm, Teku, Nimbus, Lodestar). |
info
Forking is only available with the Reth client currently
info
Currently, the platform does not allow changing the node count, CPU and memory but please let us know if you need larger networks.