lambdaclass / lambdaclass/lambda_ethereum_consensus
Make checkpoint sync recursive and smarter
Open
@avilagaston9 is already working on this.
Since Aug 14, 2024.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Currently we use checkpoint sync to start subscriptions when blocks are finished downloading. However, there's two things we can improve:
- If the new slot drifted from the last block downloaded, repeat checkpoint sync, this time with less slots.
- If at any point later in the life of a node we get a big chunk of missing blocks (e.g. due to downtime) we can do the sync again until we're up to date. This one needs to be better evaluated but may improve our response to outages.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.