Repository navigation
Conversation
This was referenced Sep 29, 2026
Marchhill
changed the title
Marchhill
changed the title
| - `slotNumber`: `QUANTITY`, 64 Bits - value for the `slotNumber` field of the new payload | ||
| - `targetGasLimit`: `QUANTITY`, 64 Bits - target value for the `gasLimit` field of the new payload | ||
| - `inclusionListTransactions`: `Array of DATA` - Array of transaction objects, each object is a byte list (`DATA`) representing `TransactionType || TransactionPayload` or `LegacyTransaction` as defined in [EIP-2718](https://eips.ethereum.org/EIPS/eip-2718). | ||
| - `inclusionListMembership`: `Array of DATA`, 2 Bytes - Array of inclusion list memberships, one per element of `inclusionListTransactions` at the same position. Each element is a bitvector of length `INCLUSION_LIST_COMMITTEE_SIZE`, encoded as SSZ `Bitvector[INCLUSION_LIST_COMMITTEE_SIZE]`, in which bit `i` is set if and only if the inclusion list of the inclusion list committee member at committee position `i` carries the transaction. |
There was a problem hiding this comment.
could this add an example? as 2 byte hex it's easy to read as a big-endian uint16, but in ssz order positions {0, 9} are 0x0102.
|
|
||
| 3. The total byte length of the transaction list **MUST NOT** exceed `MAX_TRANSACTIONS_BYTES_PER_INCLUSION_LIST`. | ||
|
|
||
| 4. When [EIP-8141](https://eips.ethereum.org/EIPS/eip-8141) is active, the total VERIFY budget cost of the Profile 2 candidates in the transaction list **MUST NOT** exceed `MAX_VERIFY_GAS_PER_IL`, with the cost, the candidates and the constant as defined in [EIP-8369](https://eips.ethereum.org/EIPS/eip-8369). |
There was a problem hiding this comment.
ethereum/EIPs#12394 says SHOULD NOT for the same bound, is the difference intended? also MAX_VERIFY_GAS_PER_IL isn't in the constants table here, and eip-8369 only has a candidate value.
Draft
1 of 2 tasks
Marchhill
changed the title
Marchhill
changed the title
Marchhill
added a commit
to NethermindEth/nethermind
that referenced
this pull request
Oct 15, 2026
…nclusion checks Brings Profile 2 and the Bogota engine API to ethereum/EIPs#12394 and #12396, ethereum/execution-apis#911, ethereum/consensus-specs#5698 and ethereum/execution-specs#3777. - engine_newPayloadV6 and engine_newPayloadWithWitnessV6 take one inclusion list per committee position and omissionClaims {transactionHash, evaluationIndex}, replacing the flat list and its membership bitvectors. Each list is checked against its byte cap before deduplication; malformed lists or claims answer -32602. - Inclusion is checked apart from execution. A VALID payload is answered at once with inclusionCheckId and the check's verdict, null while it is pending; engine_getInclusionListVerdictV1 polls it and answers -38007 for an unknown check. A check that cannot be decided is forgotten, not completed. - engine_forkchoiceUpdatedV5 takes PayloadAttributesV5.inclusionLists and returns PayloadStatusV1. The retained-list answers and the queued-copy tracking kept for per-call lists are removed. - engine_getPayloadV7 returns omissionClaims; the builder fills each list's VERIFY budget separately. - The VERIFY fill runs per committee position over the separate lists. - The pipeline records the gas used before each transaction whenever Profile 2 is active, for claims judged after execution. - MAX_INCLUSION_LIST_CLAIMS is renamed MAX_OMISSION_CLAIMS.
7 of 16 tasks
… encoding Add MAX_VERIFY_GAS_PER_TX and note that the Bogota IL shapes replace the FOCIL devnet shapes.
5 tasks done
This was referenced Oct 27, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds separate inclusion lists and bounded omission claims to Bogota's Engine API. Each committee position retains its own list and budget.
``newPayloadV6
returns a completed inclusion verdict withVALID`; there is no inclusion-check ID or polling endpoint. Forkchoice reports execution validity only. Inclusion failure does not invalidate execution.Validation: specification build/tests and OpenRPC lint pass.
Related: ethereum/EIPs#12394, ethereum/consensus-specs#5698, ethereum/execution-specs#3777.