From ffb4f8afbbec7954ae4d6d61277d38fe3b913dfb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9my=20Roy?= Date: Thu, 8 Sep 2022 22:42:05 -0400 Subject: [PATCH] Add community checkpoint sync endpoints --- book/src/checkpoint-sync.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/book/src/checkpoint-sync.md b/book/src/checkpoint-sync.md index fc878f5f652..0ff1dae8357 100644 --- a/book/src/checkpoint-sync.md +++ b/book/src/checkpoint-sync.md @@ -41,6 +41,13 @@ Once the checkpoint is loaded Lighthouse will sync forwards to the head of the c If a validator client is connected to the node then it will be able to start completing its duties as soon as forwards sync completes. +### Use a community checkpoint sync endpoint + +The Ethereum community provides various [public endpoints](https://eth-clients.github.io/checkpoint-sync-endpoints/) for you to choose from for your initial checkpoint state. Select one for your network and use it as the url for the `--checkpoint-sync-url` flag. e.g. +``` +lighthouse bn --checkpoint-sync-url https://beaconstate.info/ ... +``` + ### Use Infura as a remote beacon node provider You can use Infura as the remote beacon node provider to load the initial checkpoint state.