cerc-io/lighthouse
16
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Add a section on using infura as the checkpoint sync provider (#2797)

Browse Source 
## 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.
This commit is contained in:
Pawan Dhananjay 2021-11-10 23:43:12 +00:00
parent 931daa40d7
commit 3919046731
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
book/src/checkpoint-sync.md
View File

@ -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 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. 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://<PROJECT-ID>:<PROJECT-SECRET>@eth2-beacon-mainnet.infura.io ...
```
## Backfilling Blocks ## Backfilling Blocks
Once forwards sync completes, Lighthouse will commence a "backfill sync" to download the blocks Once forwards sync completes, Lighthouse will commence a "backfill sync" to download the blocks