dev CLI Command
Quickly bootstrap a beacon node and multiple validators. Use for development and testing
Examplesโ
Start a single beacon node with 8 interop validators
./lodestar dev --genesisValidators 8 --reset
dev Optionsโ
--dataDirโ
Lodestar root data directory
type: string
--networkโ
Name of the Ethereum Consensus chain network to join
type: string
choices: "mainnet", "gnosis", "sepolia", "hoodi", "chiado", "ephemery", "dev"
default: "mainnet"
--paramsFileโ
Network configuration file
type: string
--rcConfigโ
RC file to supplement command line args, accepted formats: .yml, .yaml, .json
type: string
--supernodeโ
Subscribe to and custody all data column sidecar subnets
type: boolean
--semiSupernodeโ
Subscribe to and custody half of the data column sidecar subnets to support blob reconstruction, enabling more efficient data availability with lower bandwidth and storage requirements compared to a supernode.
type: boolean
--genesisStateFileโ
Path or URL to download a genesis state file in ssz-encoded format
type: string
--checkpointSyncUrlโ
Server url hosting Beacon Node APIs to fetch weak subjectivity state. Fetch latest finalized by default, else set --wssCheckpoint
type: string
--checkpointStateโ
File path or url to finalized checkpoint state to start syncing from
type: string
--wssCheckpointโ
Start beacon node off a state at the provided weak subjectivity checkpoint, to be supplied in <blockRoot>:<epoch> format. For example, 0x1234:100 will sync and start off from the weak subjectivity state at checkpoint of epoch 100 with block root 0x1234.
type: string
--forceCheckpointSyncโ
Force syncing from checkpoint state even if db state is within weak subjectivity period. This helps to avoid long sync times after node has been offline for a while.
type: boolean
--ignoreWeakSubjectivityCheckโ
Ignore the checkpoint sync state failing the weak subjectivity check. This is relevant in testnets where the weak subjectivity period is too small for even few epochs of non finalization causing last finalized to be out of range. This flag is not recommended for mainnet use.
type: boolean
--persistNetworkIdentityโ
Whether to reuse the same peer-id across restarts. Validator custody requires custody group count to persist relative to a given ENR. Setting to false will reset ENR and validator custody requirements on restarts.
type: boolean
default: true
--privateโ
Do not send implementation details over p2p identify protocol, and in builder and execution engine requests
type: boolean