Skip to content

fix: rename max IL transactions bytes constants #871

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mkalinin merged 1 commit into from
Aug 28, 2026
Merged

fix: rename max IL transactions bytes constants #871

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/engine/bogota.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ This specification is based on and extends [Engine API - Amsterdam](./amsterdam.

| Name | Value |
| - | - |
| `MAX_BYTES_PER_INCLUSION_LIST` | `uint64(8192) = 2**13` |
| `MAX_TRANSACTIONS_BYTES_PER_INCLUSION_LIST` | `uint64(8192) = 2**13` |

## Structures

Expand Down Expand Up @@ -124,7 +124,7 @@ This method follows the same specification as [`engine_newPayloadV5`](./amsterda

1. Client software **MUST** provide a list of transactions for the inclusion list based on the local view of the mempool. The strategy for selecting which transactions to include is implementation dependent.

2. Client software **MUST** ensure the byte length of the RLP encoding of the returned transaction list does not exceed `MAX_BYTES_PER_INCLUSION_LIST`.
2. Client software **MUST** ensure the byte length of the RLP encoding of the returned transaction list does not exceed `MAX_TRANSACTIONS_BYTES_PER_INCLUSION_LIST`.

3. Client software **MUST NOT** include any [blob transaction](https://eips.ethereum.org/EIPS/eip-4844#blob-transaction) in the returned transaction list.

Expand Down
Loading