Skip to content

Use MAX_REQUEST_PAYLOADS in EnvelopesByRange - #5383

Merged
jtraglia merged 2 commits into
ethereum:masterfrom
jtraglia:max-request-payloads
Jun 23, 2026
Merged

Use MAX_REQUEST_PAYLOADS in EnvelopesByRange#5383
jtraglia merged 2 commits into
ethereum:masterfrom
jtraglia:max-request-payloads

Conversation

@jtraglia

Copy link
Copy Markdown
Member

For some reason, we're still using MAX_REQUEST_BLOCKS_DENEB in ExecutionPayloadEnvelopesByRange. I believe we forgot to update this when adding the new config a while back. This would mirror ExecutionPayloadEnvelopesByRoot:

##### ExecutionPayloadEnvelopesByRoot v1
**Protocol ID:** `/eth2/beacon_chain/req/execution_payload_envelopes_by_root/1/`
For each successful `response_chunk`, the `ForkDigest` context epoch is
determined by `compute_epoch_at_slot(beacon_block.slot)` based on the
`beacon_block` referred to by
`signed_execution_payload_envelope.message.beacon_block_root`.
Per `fork_version = compute_fork_version(epoch)`:
<!-- eth_consensus_specs: skip -->
| `fork_version` | Chunk SSZ type |
| -------------------- | -------------------------------------- |
| `GLOAS_FORK_VERSION` | `gloas.SignedExecutionPayloadEnvelope` |
Request Content:
```
(
List[Root, MAX_REQUEST_PAYLOADS]
)
```
Response Content:
```
(
List[SignedExecutionPayloadEnvelope, MAX_REQUEST_PAYLOADS]
)
```

@github-actions github-actions Bot added the gloas label Jun 22, 2026
@jtraglia jtraglia changed the title Use MAX_REQUEST_PAYLOADS in EnvelopesByRange Use MAX_REQUEST_PAYLOADS in EnvelopesByRange Jun 22, 2026
@jtraglia
jtraglia requested a review from jihoonsong June 23, 2026 11:55
@jtraglia
jtraglia merged commit 77933b9 into ethereum:master Jun 23, 2026
16 checks passed
@jtraglia

Copy link
Copy Markdown
Member Author

To be clear, these are the same value right now (128).

tbenr added a commit to rolfyone/teku that referenced this pull request Jul 9, 2026
tbenr added a commit to rolfyone/teku that referenced this pull request Jul 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants