Skip to content

Conversation

@evan-forbes
Copy link
Member

@evan-forbes evan-forbes commented Dec 15, 2025

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.

@github-project-automation github-project-automation bot moved this to Needs Triage in core/app Dec 15, 2025
Copy link
Member Author

@evan-forbes evan-forbes left a 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

Comment on lines +1 to +7
# 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)
Copy link
Member Author

@evan-forbes evan-forbes Dec 15, 2025

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

@evan-forbes evan-forbes changed the title feat: unified catchup and blocksync don't merge will be split up: feat: unified catchup and blocksync Dec 15, 2025
@evan-forbes evan-forbes changed the title don't merge will be split up: feat: unified catchup and blocksync don't review will be split up: feat: unified catchup and blocksync Dec 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

2 participants