Skip to content

Gloas dont enforce peer column custody on block import#9341

Open
eserilev wants to merge 1 commit into
sigp:unstablefrom
eserilev:gloas-dont-enforce-peer-column-custody-on-block-import
Open

Gloas dont enforce peer column custody on block import#9341
eserilev wants to merge 1 commit into
sigp:unstablefrom
eserilev:gloas-dont-enforce-peer-column-custody-on-block-import

Conversation

@eserilev
Copy link
Copy Markdown
Member

Issue Addressed

Peers that advertise that they have imported a block may not have the columns for that slot available post-Gloas. Ensure that we dont penalize them.

@eserilev eserilev requested a review from jxs as a code owner May 22, 2026 13:17
@eserilev eserilev added gloas syncing ready-for-review The code is ready for review low-hanging-fruit Easy to resolve, get it before someone else does! labels May 22, 2026
Copy link
Copy Markdown
Member

@pawanjay176 pawanjay176 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, other than a small suggestion.

// have the block but not yet imported the envelope and data columns.
// Don't enforce max_responses in this case.
lookup_peers.contains(&peer_id)
&& !cx
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can do
!cx.fork_context.current_fork_name().gloas_enabled()

This is not strictly correct because we should be checking the block's slot and not current slot clock. But given that #9155 is overhauling the entire thing, i'm fine with this to help with the devnet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gloas low-hanging-fruit Easy to resolve, get it before someone else does! ready-for-review The code is ready for review syncing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants