Skip to content

feat: add RPC API - #53

Merged
MegaRedHand merged 7 commits into
mainfrom
add-rpc-api
Jan 26, 2026
Merged

MegaRedHand merged 7 commits into
mainfrom
add-rpc-api

Conversation

@MegaRedHand

Copy link
Copy Markdown
Collaborator

No description provided.

@MegaRedHand
MegaRedHand merged commit ec48acc into main Jan 26, 2026
2 checks passed
@MegaRedHand
MegaRedHand deleted the add-rpc-api branch January 26, 2026 19:21
tcoratger pushed a commit to tcoratger/ethlambda that referenced this pull request Oct 30, 2026
…peers (lambdaclass#53)

A range batch sends its blocks and a DataColumnsByRange for the same span
together, and the column request is aimed by custody, which is only known
once a peer's metadata/3 answer or ENR cgc has been read. Right after
startup that is almost nobody. On a mainnet follower after a fresh
checkpoint sync, the first batch went out 5 s after startup with two peers
and at most one known custodian per column, and 121 of the 122 holds it
caused were missing every custody column; a short or empty range answer is
never retried, so each block was left to the by-root path.

A batch whose span reaches fulu is now held, blocks included, until every
custody column has a known custodian among the connected peers, the way
lighthouse's range sync holds its batches. It is re-checked after every
metadata answer, on every Status answer, and at a deadline, past which it
goes anyway with the old fallback: nothing here searches for a custodian of
a specific column, so an open-ended wait could stall sync.
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