-
Notifications
You must be signed in to change notification settings - Fork 359
don't review will be split up: feat: unified catchup and blocksync #2716
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
base: evan/exp/header-sync
Are you sure you want to change the base?
Conversation
extended commit from the vote extensions
evan-forbes
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vast majority of the new LoC are tests and documentation, so don't let the 10k scare anyone
| # Implementation Plan: Unified Pending Block Manager | ||
|
|
||
| ## Overview | ||
|
|
||
| This plan describes how to implement a unified `PendingBlocksManager` that consolidates: | ||
| 1. **Catchup** (part-level recovery for current consensus height) | ||
| 2. **Blocksync** (downloading historical blocks to catch up to the network) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
trying something new by including the implementation planning document I was using to prompt the llms
this is actually the best place to start for reviewers
we should delete this before merging presumably
implemented unified catchup
closes #2711
blocked by headersync
this still needs to be more thoroughly tested on talis
its a lot of code as there is a ton of boiler plate and tests. probably 2k loc of actual logic.