From 39190467317d4642715a843cf4ec78e718a88db0 Mon Sep 17 00:00:00 2001 From: Pawan Dhananjay Date: Wed, 10 Nov 2021 23:43:12 +0000 Subject: [PATCH] Add a section on using infura as the checkpoint sync provider (#2797) ## Issue Addressed N/A ## Proposed Changes From discord, it seems like users are a bit unclear on how to run checkpoint sync if they don't have an existing synced beacon node. Adds a note on how to use infura for the checkpoint sync feature. --- book/src/checkpoint-sync.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/book/src/checkpoint-sync.md b/book/src/checkpoint-sync.md index 919c9a54e0..fc878f5f65 100644 --- a/book/src/checkpoint-sync.md +++ b/book/src/checkpoint-sync.md @@ -41,6 +41,17 @@ 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 Infura as a remote beacon node provider + +You can use Infura as the remote beacon node provider to load the initial checkpoint state. + +1. Sign up for the free Infura ETH2 API using the `Create new project tab` on the [Infura dashboard](https://infura.io/dashboard). +2. Copy the HTTPS endpoint for the required network (Mainnet/Prater). +3. Use it as the url for the `--checkpoint-sync-url` flag. e.g. +``` +lighthouse bn --checkpoint-sync-url https://:@eth2-beacon-mainnet.infura.io ... +``` + ## Backfilling Blocks Once forwards sync completes, Lighthouse will commence a "backfill sync" to download the blocks