Difference between revisions of "Lighthouse beacon node"

From wikieduonline
Jump to navigation Jump to search
Line 8: Line 8:
  
 
  [[5052]] port
 
  [[5052]] port
 
  
 
== Options ==
 
== Options ==
Line 34: Line 33:
 
  [[--metrics-address]]
 
  [[--metrics-address]]
 
  [[--builder]] <builder/YOUR_SERVICE_URL> The [[URL]] of a service compatible with the [[MEV-boost]] API.
 
  [[--builder]] <builder/YOUR_SERVICE_URL> The [[URL]] of a service compatible with the [[MEV-boost]] API.
 +
 +
== Example ==
 +
 +
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
  
 
== Related ==
 
== Related ==

Revision as of 10:05, 31 May 2024

lighthouse bn 
lighthouse beacon_node --help
lighthouse beacon_node --execution-endpoint
lighthouse beacon_node --staking
lighthouse checkpoint sync
5052 port

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.

Example

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

Related

See also

Advertising: