lighthouse beacon node
Jump to navigation
Jump to search
lighthouse bn lighthouse beacon_node --help lighthouse beacon_node --execution-endpoint lighthouse beacon_node --staking lighthouse beacon_node --allow-insecure-genesis-sync --checkpoint-sync-url lighthouse checkpoint sync
lighthouse beacon_node --execution-endpoint http://127.0.0.1:8551 --execution-jwt ~/Library/Ethereum/geth/jwtsecret --allow-insecure-genesis-sync
lighthouse bn --checkpoint-sync-url=https://mainnet-checkpoint-sync.attestant.io --purge-db 2>&1 | egrep --line-buffered -v "Not ready for|Failed to "
5052 port for metrics 9000 port
Contents
Options
--execution-endpoint --http-address --staking --http --http-port --http-address --http-allow-origin --eth1-endpoints --datadir --network --disable-upnp --disable-enr-auto-update --target-peers --discovery-ports --enr-address --enr-tcp-ports --enr-udp-port --subcribe-all-subnets --import-all-attestations --validator-monitor-auto --metrics-ports --metrics-address --builder <builder/YOUR_SERVICE_URL> The URL of a service compatible with the MEV-boost API.
Examples
Example from genesis with error:
lighthouse bn May 31 09:44:11.980 INFO Logging to file path: "~/.lighthouse/mainnet/beacon/logs/beacon.log" May 31 09:44:11.984 INFO Lighthouse started version: Lighthouse/v5.1.3 May 31 09:44:11.984 INFO Configured for network name: mainnet May 31 09:44:11.984 INFO Data directory initialised datadir: ~/.lighthouse/mainnet May 31 09:44:11.988 INFO Deposit contract address: 0x00000000219ab54xxxxxxxxxx, deploy_block: 11184524 May 31 09:44:12.042 INFO Blob DB initialized oldest_blob_slot: Some(Slot(8626176)), path: "~/.lighthouse/mainnet/beacon/blobs_db", service: freezer_db May 31 09:44:12.042 INFO Starting from known genesis state service: beacon May 31 09:44:12.048 CRIT Failed to start beacon node reason: Syncing from genesis is insecure and incompatible with data availability checks. You should instead perform a checkpoint sync from a trusted node using the --checkpoint-sync-url option. For a list of public endpoints, see: https://eth-clients.github.io/checkpoint-sync-endpoints/ Alternatively, use --allow-insecure-genesis-sync if the risks are understood. May 31 09:44:12.048 INFO Internal shutdown received reason: Failed to start beacon node May 31 09:44:12.048 INFO Shutting down.. reason: Failure("Failed to start beacon node") Failed to start beacon node
Errors
Related
See also
lighthouse beacon_node, --execution-endpoint, --execution-jwt, --allow-insecure-genesis-sync, logs,--checkpoint-sync-url, --help, checkpoint sync,beacon.loglighthouse: [ account | beacon_node | boot node | account manager | database manager | validator client ], --help, --version, Releases, Ligthouse WARN, Paul Hauner, Lighthouse checkpoint sync, Lighthouse logs, Changelog- Ethereum Beacon Chain,
lighthouse beacon_node - Beacon Chain, Ropsten Beacon Chain, Bellatrix beacon chain, The Merge, BeaconChainRpcEndpoints,
lighthouse beacon_node, 5052
Advertising:
