Skip to content

Conversation

@antonis19
Copy link
Member

Cherry-pick 9907be8 from release/3.0 to main.

@antonis19 antonis19 requested a review from Copilot August 25, 2025 10:54
@antonis19 antonis19 merged commit 5e69adc into main Aug 25, 2025
16 checks passed
@antonis19 antonis19 deleted the cherry-pick-veblop branch August 25, 2025 12:08
antonis19 added a commit that referenced this pull request Sep 5, 2025
)

cherry-pick of #16803

If the tip is behind the milestone end, then this triggers an unwind to
the previous verified milestone and download of blocks from previous
verified milestone block until new milestone end block.

This is unnecessary since we can put the milestone back in the event
queue, and it will be picked up later, and hopefully by that time the
tip will be in sync with milestone. This is expected to reduce the
number of unwinds.

---------

Co-authored-by: antonis19 <[email protected]>
bloxster pushed a commit that referenced this pull request Sep 9, 2025
)

cherry-pick of #16803

If the tip is behind the milestone end, then this triggers an unwind to
the previous verified milestone and download of blocks from previous
verified milestone block until new milestone end block.

This is unnecessary since we can put the milestone back in the event
queue, and it will be picked up later, and hopefully by that time the
tip will be in sync with milestone. This is expected to reduce the
number of unwinds.

---------

Co-authored-by: antonis19 <[email protected]>
antonis19 added a commit that referenced this pull request Sep 11, 2025
Cherry-pick
9907be8
from release/3.0 to main.

---------

Co-authored-by: antonis19 <[email protected]>
yperbasis pushed a commit that referenced this pull request Sep 12, 2025
antonis19 added a commit that referenced this pull request Sep 12, 2025
)

cherry-pick of #16803

If the tip is behind the milestone end, then this triggers an unwind to
the previous verified milestone and download of blocks from previous
verified milestone block until new milestone end block.

This is unnecessary since we can put the milestone back in the event
queue, and it will be picked up later, and hopefully by that time the
tip will be in sync with milestone. This is expected to reduce the
number of unwinds.

---------

Co-authored-by: antonis19 <[email protected]>
NazariiDenha pushed a commit that referenced this pull request Oct 24, 2025
Cherry-pick
9907be8
from release/3.0 to main.

---------

Co-authored-by: antonis19 <[email protected]>
NazariiDenha pushed a commit that referenced this pull request Oct 24, 2025
)

cherry-pick of #16803

If the tip is behind the milestone end, then this triggers an unwind to
the previous verified milestone and download of blocks from previous
verified milestone block until new milestone end block.

This is unnecessary since we can put the milestone back in the event
queue, and it will be picked up later, and hopefully by that time the
tip will be in sync with milestone. This is expected to reduce the
number of unwinds.

---------

Co-authored-by: antonis19 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants