Add example curl command to test Beacon API endpoint in blsync.md #31980
Conversation
This file contains hidden or 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
❌ Deploy Preview for geth-website failed.Built without sensitive environment variables
|
tr1sm0s1n
reviewed
Jun 8, 2025
lightclient
reviewed
Jun 13, 2025
There was a problem hiding this comment.
Thanks Shanti! What I'm hoping for here in the example is more of a one line command that gets the checkpoint and starts geth using blsync with that root.
It should look something like this
export BEACON=<server URL>
geth --beacon.api=$BEACON --beacon.checkpoint=$(curl <rest of command to get the check point root>)
You'll want to use jq to access the exact values from the JSON response from the beacon api.
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.
This adds a short example section showing how to use curl to verify that a Beacon API endpoint is reachable and returns valid light client headers. Helps developers quickly test endpoint connectivity before integration.