From cfa518ab41232b7af45a42057372b73eaf5e322f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9my=20Roy?= Date: Sat, 10 Sep 2022 01:35:11 +0000 Subject: [PATCH] Use generic domain for community checkpoint sync example (#3560) ## Proposed Changes Use a generic domain for community checkpoint sync example to meet the concern raised in https://github.com/sigp/lighthouse/pull/3558#discussion_r966720171 --- book/src/checkpoint-sync.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/src/checkpoint-sync.md b/book/src/checkpoint-sync.md index 0ff1dae83..736aa08f1 100644 --- a/book/src/checkpoint-sync.md +++ b/book/src/checkpoint-sync.md @@ -45,7 +45,7 @@ as soon as forwards sync completes. 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/ ... +lighthouse bn --checkpoint-sync-url https://example.com/ ... ``` ### Use Infura as a remote beacon node provider