Do not sync from genesis by default

prysmaticlabs / prysm

Go implementation of Ethereum proof of stake

https://www.offchainlabs.com

GNU General Public License v3.0

3.45k stars 986 forks source link

Do not sync from genesis by default #13020

Open potuz opened 11 months ago

potuz commented 11 months ago

Many users inadvertently try to sync from genesis cause they do not know about checkpoint sync (for example our documentation does not mention it in the quickstart guide). Besides fixing the docs, I think a good UX would be to

Add a feature flag --sync-from-genesis.
When starting a node on an empty db, refuse to sync unless one of --sync-from-genesis or one of the --checkpoint-sync flags is set.

potuz commented 11 months ago

As Preston noted, this cannot be included until a major version change, presumably for Deneb v5

prestonvanloon commented 11 months ago

This impacts the new user workflow only. Given that we are moving away from genesis sync in favor of checkpoint sync + backfill, this change makes sense to do so in the next major upgrade.

jooddang commented 10 months ago

I'm getting trouble to start prysm.sh . How can I sync from a checkpoint? Or, is there a correct genesis file that I can use?

$ ./prysm.sh beacon-chain --execution-endpoint=http://localhost:8551 --holesky --suggested-fee-recipient=0x0000 --jwt-secret=../jwt.hex --genesis-state=genesis.ssz

unable to start beacon node: could not load genesis from file: version=0x22637573 not found in any known fork choice schedule: unable to find requested BeaconChainConfig

junghyun0783 commented 1 month ago

@jooddang hey~ I'm having this same error right now. Have you fixed it?

jooddang commented 1 month ago

@jooddang hey~ I'm having this same error right now. Have you fixed it?

No... I moved to a different service

junghyun0783 commented 1 month ago

@jooddang I have a question. In my case, I stopped the container in the middle of initialization. Will this cause a problem? The beacon initialization was going well, but I stopped the container for a while due to a network problem, and when I ran it again, it didn't work. Will there be a problem if I stop it during initialization?

Did you also encounter this situation when you stopped it during initialization?