Difference between revisions of "Lighthouse bn --checkpoint-sync-url"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
* https://lighthouse-book.sigmaprime.io/checkpoint-sync.html | * https://lighthouse-book.sigmaprime.io/checkpoint-sync.html | ||
| + | [[lighthouse bn]] --checkpoint-sync-url=https://mainnet-checkpoint-sync.[[attestant.io]] | ||
[[lighthouse bn]] --checkpoint-sync-url "http://remote-bn:[[5052]]" ... | [[lighthouse bn]] --checkpoint-sync-url "http://remote-bn:[[5052]]" ... | ||
Revision as of 10:03, 13 June 2024
lighthouse bn --checkpoint-sync-url=https://mainnet-checkpoint-sync.attestant.io
lighthouse bn --checkpoint-sync-url "http://remote-bn:5052" ...
--checkpoint-sync-url <BEACON_NODE>
Set the remote beacon node HTTP endpoint to use for checkpoint sync.
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.
INFO Starting checkpoint sync CRIT Failed to start beacon node WARN Running HTTP server on port INFO Starting beacon chain INFO Issuing forkchoiceUpdated
lighthouse beacon_node, --execution-endpoint, --execution-jwt, --allow-insecure-genesis-sync, logs, --checkpoint-sync-url, --help, checkpoint sync, beacon.log
Advertising:
