[Merged by Bors] - Add community checkpoint sync endpoints to book #3558
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelsproul
added
docs
|
bors r+ |
bors bot
pushed a commit
that referenced
this pull request
Sep 9, 2022
## Proposed Changes Add a section on the new community checkpoint sync endpoints in the book. This should help stakers sync faster even without having to create an account.
|
Just a suggestion. The recommend |
bors
bot
changed the title
|
|
||
| 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/ ... |
There was a problem hiding this comment.
I feel like People might just end up copying this line out of laziness and all end up using this specific endpoint, which is sub-optimal from a safety perspective (no single checkpoint endpoint should be recommended). How about using a non-working domain instead, like example.com?
There was a problem hiding this comment.
that's a good point, I'm happy to merge that change if you or @remyroy would like to PR it (assuming no objections?)
There was a problem hiding this comment.
I'm good with @InvisibleSymbol suggestion. Let me do another PR.
bors bot
pushed a commit
that referenced
this pull request
Sep 10, 2022
## Proposed Changes Use a generic domain for community checkpoint sync example to meet the concern raised in #3558 (comment)
bors bot
pushed a commit
that referenced
this pull request
Sep 10, 2022
## Proposed Changes Use a generic domain for community checkpoint sync example to meet the concern raised in #3558 (comment)
Woodpile37
pushed a commit
to Woodpile37/lighthouse
that referenced
this pull request
Jan 6, 2024
## Proposed Changes Add a section on the new community checkpoint sync endpoints in the book. This should help stakers sync faster even without having to create an account.
Woodpile37
pushed a commit
to Woodpile37/lighthouse
that referenced
this pull request
Jan 6, 2024
## Proposed Changes Use a generic domain for community checkpoint sync example to meet the concern raised in sigp#3558 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Add a section on the new community checkpoint sync endpoints in the book. This should help stakers sync faster even without having to create an account.