Skip to content
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

find_potential_parents: Enforce max_depth from the pending_block #7335

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bkchr
Copy link
Member

@bkchr bkchr commented Jan 24, 2025

Currently max_depth is checked from the included_block. However, we should always be interested to build on the pending_block that will be the next included block. Thus, enforcing the max_depth from pending_block is the more correct option here. Especially for chains that are running with a higher block frequency than the relay chain and thus, having more than one block between included_block and pending_block.

Currently `max_depth` is checked from the `included_block`. However, we should always be interested to build
on the `pending_block` that will be the next included block. Thus, enforcing the `max_depth` from `pending_block` is the
more correct option here. Especially for chains that are running with a higher block frequency than the relay chain and thus,
having more than one block between `included_block` and `pending_block`.
@bkchr bkchr added the T0-node This PR/Issue is related to the topic “node”. label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T0-node This PR/Issue is related to the topic “node”.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant