Lighthouse bn --checkpoint-sync-url

• https://lighthouse-book.sigmaprime.io/checkpoint-sync.html

lighthouse bn --checkpoint-sync-url
lighthouse bn --purge-db --checkpoint-sync-url

lighthouse bn --checkpoint-sync-url=https://mainnet-checkpoint-sync.attestant.io --purge-db  2>&1 | egrep --line-buffered -v "Not ready for|Failed to "

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.

Jun 13 10:17:57.101 INFO Starting checkpoint sync                remote_url: https://mainnet-checkpoint-sync.attestant.io/, service: beacon

Jun 13 10:14:29.078 INFO Refusing to checkpoint sync             msg: database already exists, use --purge-db to force checkpoint sync, service: beacon

INFO Starting checkpoint sync
CRIT Failed to start beacon node
WARN Running HTTP server on port
INFO Starting beacon chain
INFO Issuing forkchoiceUpdated

• https://eth-clients.github.io/checkpoint-sync-endpoints/

• Lighthouse checkpoint sync
• Attestant.io

lighthouse beacon_node, --execution-endpoint, --execution-jwt, --allow-insecure-genesis-sync, logs, --checkpoint-sync-url, --help, checkpoint sync, beacon.log