Skip to content

fix: send status request on connection and use real status - #54

Merged
MegaRedHand merged 5 commits into
mainfrom
send-status-on-connection
Jan 26, 2026
Merged

MegaRedHand merged 5 commits into
mainfrom
send-status-on-connection

Conversation

@MegaRedHand

Copy link
Copy Markdown
Collaborator

This PR replaces the minimal behavior of our Status req-resp flow with the correct implementation.

@MegaRedHand
MegaRedHand merged commit 75e536d into main Jan 26, 2026
2 checks passed
@MegaRedHand
MegaRedHand deleted the send-status-on-connection branch January 26, 2026 19:31
tcoratger pushed a commit to tcoratger/ethlambda that referenced this pull request Oct 30, 2026
…t it (lambdaclass#54)

A block whose parent has no post-state walks up to its first ancestor that
does have a parent state and re-queues that ancestor for import. When the
ancestor is held for its custody columns, that import can only hold it
again, and a range batch hands the actor its whole chain at once, so every
block behind a held one paid for another hold of it. On a mainnet follower's
first batch after a checkpoint sync, the 68 blocks behind the first one
re-held it 68 times over 54 s, while the columns that would release it had
already been delivered.

The walk now stops at a block in blocks_awaiting_columns. The child is
already registered under its parent in pending_blocks, and the held block's
release imports it and cascades down the chain from there.
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.

1 participant