Skip to content

beacon/blsync: add checkpoint import/export file feature #31469

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 3, 2025

Conversation

zsfelfoldi
Copy link
Contributor

This PR adds a new --beacon.checkpoint.file config flag to geth and blsync which specifies a checkpoint import/export file. If a file with an existing checkpoint is specified, it is used for initialization instead of the hardcoded one (except when --beacon.checkpoint is also specified simultaneously). Whenever the client encounters a new valid finality update with a suitable finalized beacon block root at an epoch boundary, it saves the block root in hex format to the checkpoint file.

fjl pushed a commit that referenced this pull request Mar 24, 2025
This PR updates beacon checkpoints. The checkpoints are now stored as
embedded hex files, in the same format that
#31469 uses.
sidhujag pushed a commit to syscoin/go-ethereum that referenced this pull request Mar 26, 2025
This PR updates beacon checkpoints. The checkpoints are now stored as
embedded hex files, in the same format that
ethereum#31469 uses.
@fjl fjl merged commit 9f83e9e into ethereum:master Apr 3, 2025
3 of 4 checks passed
@fjl fjl added this to the 1.15.8 milestone Apr 3, 2025
sivaratrisrinivas pushed a commit to sivaratrisrinivas/go-ethereum that referenced this pull request Apr 21, 2025
This PR updates beacon checkpoints. The checkpoints are now stored as
embedded hex files, in the same format that
ethereum#31469 uses.
sivaratrisrinivas pushed a commit to sivaratrisrinivas/go-ethereum that referenced this pull request Apr 21, 2025
)

This PR adds a new `--beacon.checkpoint.file` config flag to geth and
blsync which specifies a checkpoint import/export file. If a file with
an existing checkpoint is specified, it is used for initialization
instead of the hardcoded one (except when `--beacon.checkpoint` is also
specified simultaneously). Whenever the client encounters a new valid
finality update with a suitable finalized beacon block root at an epoch
boundary, it saves the block root in hex format to the checkpoint file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants