coincashew / EthPillar

EthPillar: one-liner ethereum staking node setup tool and management TUI
https://www.coincashew.com/coins/overview-eth/ethpillar
GNU General Public License v3.0
8 stars 5 forks source link

Checkpoint sync.... #8

Closed chrismarino closed 2 months ago

chrismarino commented 2 months ago

Noticed that Nimbus CC was taking a long time to sync, then I realized that there was no checkpoint sync configured. Setting it up is included in the CoinCashew docs. Maybe best practice is to sync from scratch, but maybe the checkpoint sync could be included in the Tools section.

coincashew commented 2 months ago

With a default ethpillar one-liner install, nimbus's install should checkpoint sync automatically. Here's the code https://github.com/coincashew/EthPillar/blob/f91bd52897d22015a1067c1fe530dc94e2672c0b/deploy-nimbus-nethermind.py#L440C6-L440C9

You can force a checkpoint sync again in ethpillar > consensus client > resync consensus client.

Let me know if that works.

coincashew commented 2 months ago

I think what happened was nimbus checkpoint sync occurs, but it takes a while to backfill sync.

chrismarino commented 2 months ago

Hmmm.....Didn't work. Might be an artifact of zsh v. bash prob. Trying again w/v1.5.0.

╰─►  bash ethpillar                                                                                                                                                                     127 ↵
/home/chris/git/ethpillar/resync_consensus.sh: line 10: /functions.sh: No such file or directory
curl: no URL specified!
curl: try 'curl --help' or 'curl --manual' for more information
coincashew commented 2 months ago

Simply

ethpillar

should work now with zsh.

Still doesn't work on the latest version?

chrismarino commented 2 months ago

Sorry for the confusion. I tried to resync before I updated, and got the same bash error (even when I executed `bash ethpillar'). The new version works without any errrors. But still not sync'ing quickly. Still seems too slow. Will look in to it later.

coincashew commented 2 months ago

Ok, thanks.

Checkpoint sync should enable your CL nimbus to sync to the head within seconds. e.g. your CL sees the correct current slot number. However all CL clients will take about half a day to fully sync during what's known as the backfill step.

From nimbus discord re: checkpoint sync "it should be fast, trusted node sync/checkpoint sync (as most clients call it) takes little time. backfilling is not that fast, but can be done in background with --backfill=off and it can/will validate fine in meantime"

Reference https://discord.com/channels/613988663034118151/812268053718237196/1215696256962134096

chrismarino commented 2 months ago

My re-install showed checkpoint sync working, etc. closing....

chrismarino commented 2 months ago

Closed