Skip to content
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

Support checkpoint sync #624

Closed
4 tasks done
stefa2k opened this issue Aug 6, 2022 · 1 comment · Fixed by #987
Closed
4 tasks done

Support checkpoint sync #624

stefa2k opened this issue Aug 6, 2022 · 1 comment · Fixed by #987
Assignees
Labels
enhancement Request or proposal for a new feature or enhancement

Comments

@stefa2k
Copy link
Member

stefa2k commented Aug 6, 2022

Right now syncing takes a long time, especially on mainnet. Until we are able to integrate SyncLink please provide the possibility of checkpoint sync.

Users need to enter their infura.io (or any similar service) url in order to perform a checkpoint sync of the consensus clients. This input occures at:

Clients:

  • Lighthouse --checkpoint-sync-url "http://remote-bn:5052"
  • Nimbus --trusted-node-url=http://localhost:5052
  • Prysm --checkpoint-sync-url http://other-node:5051
  • Teku --initial-state=http://other-node:5051/eth/v2/debug/beacon/states/finalized

@daGscheid please provide the UI for this!

@stefa2k stefa2k added the enhancement Request or proposal for a new feature or enhancement label Aug 6, 2022
@stefa2k stefa2k added this to the beta2.0-stack milestone Aug 6, 2022
@stefa2k stefa2k pinned this issue Aug 10, 2022
@daGscheid
Copy link
Member

daGscheid commented Aug 11, 2022

Here is the current plan for all 4 cases. Most of it is with the thought in mind that it can later be reused for Execution Clients & include SyncLink as an option.

CASE 1# One Click Installation

We drop FastSync & use the space to include an additional element to specify an URL. The user can select between Genesis Sync or Checkpoint Sync.
ONE CLICK INSTALLATION
ONE CLICK INSTALLATION – 1

This solution will be also part of 2# for every Consensus Clients as soon as we reach the custom installations full implementation:
f.e. Prysm
CUSTOM INSTALLATION

CASE 3#: NETWORK SWITCH
Pressing the button to switch the network adds an additional step to define the sync source...
image

....looking like this. We add an additional step to both execution & consensus client to define their sync source (the execution client just doesn't have a second option)

NETWORK SWITCH

After confirming your selection is taken.

CASE 4# will be addressed similarish in 504# to case 3#. An specific UI will follow for this.

CASE 5#: An additional case, I propose: You just want to re-sync for some reason (f.e. smth is not working right)

in the settings there will the option for you to click (for Consensus & Execution client) to delete your chain data & inniate a re-sync. With this element you are also able to chose the source.

PLUGIN SETTINGS – 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Request or proposal for a new feature or enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants