stereum-dev
Support checkpoint sync
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:
- OneClickInstallation
- Adding a new consensus client #500
- Switching network #503
- Switching consensus client #504
Clients:
- [x] Lighthouse
--checkpoint-sync-url "http://remote-bn:5052" - [ ] Nimbus
--trusted-node-url=http://localhost:5052 - [x] Prysm
--checkpoint-sync-url http://other-node:5051 - [x] Teku
--initial-state=http://other-node:5051/eth/v2/debug/beacon/states/finalized
@daGscheid please provide the UI for this!
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.
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
CASE 3#: NETWORK SWITCH
Pressing the button to switch the network adds an additional step to define the sync source...
....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)
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.
