Skip to content

gloas blocks rpc limits resizing#22

Closed
shane-moore wants to merge 3 commits intogloas-envelopes-by-root-req-respfrom
gloas-blocks-rpc-limits-resizing
Closed

gloas blocks rpc limits resizing#22
shane-moore wants to merge 3 commits intogloas-envelopes-by-root-req-respfrom
gloas-blocks-rpc-limits-resizing

Conversation

@shane-moore
Copy link
Copy Markdown
Owner

Changes

  • gloas cl blocks are significantly smaller now, so the rpc limits for gloas blocks from inbound responses can be reduced

@shane-moore shane-moore mentioned this pull request Oct 3, 2025
@shane-moore shane-moore force-pushed the gloas-envelopes-by-root-req-resp branch from b2de0c5 to 9eb273a Compare October 17, 2025 01:30
@shane-moore
Copy link
Copy Markdown
Owner Author

Closing — envelope RPC upstream + block-size resize explicitly rejected upstream.

The envelope RPC scaffolding (most of this PR's diff, inherited from base branch) is upstreamed via sigp#8896 ("Gloas serve envelope rpc", c7055b604).

The headline change — resizing block RPC limits down for GLOAS — was explicitly rejected upstream. rpc_block_limits_by_fork in beacon_node/lighthouse_network/src/rpc/protocol.rs:138-162 keeps Bellatrix-sized max for GLOAS, with a comment added precisely to explain why:

"Gloas blocks no longer contain the execution payload, but we must still accept pre-Gloas blocks during historical sync, so we keep the Bellatrix max as the upper bound."

Upstream considered the same idea and chose the opposite for backfill-sync correctness. Nothing salvageable to upstream from this fork PR.

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