-
Notifications
You must be signed in to change notification settings - Fork 725
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
Snap sync moving root/healing implementation #3332
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
…orepo into snap-sync-moving-root
…orepo into snap-sync-moving-root
…/ethereumjs-monorepo into snap-sync-moving-root
…ly on protocol binding, small local refactor
…sendStatus for devp2p protocols
…to move from Sync -> Peer
…atest() call on peers in peer pool
…m-to-redo-peer-handshake-for-status-update
…e-for-status-update
…update' of https://github.com/ethereumjs/ethereumjs-monorepo into snap-sync-moving-root
…/ethereumjs-monorepo into snap-sync-moving-root
…orepo into snap-sync-moving-root
…orepo into snap-sync-moving-root
Update: Currently, with #3354 merged, I am working on implementing functionality for the snap sync fetchers to change the state root that they are using for fetching state data. In order to run the client manually for syncing Holesky using snap sync, use commands similar to the following:
In order to run the client manually for syncing the smaller, more manageable
In both cases, the |
This change will add the ability to the snap sync fetchers to have their target roots updated and will explore adding continual healing to the snap sync process.