Repository navigation
Conversation
github-actions
Bot
added
c-update
Collaborator
File
|
Marchhill
changed the title
|
|
||
| To enforce this per list, the activating fork must define Engine API versions for payload validation and building that carry each counted inclusion list's `[transactions, recursive_stark]`, preserving its authenticated committee-position association and EIP-7805's membership and committed claims. Existing method versions retain their encodings. The execution layer checks each list's dependency proof and derives obligations per list. The consensus layer cannot instead drop lists with failed proofs: checking `deps_hash` requires parsing transactions, and dropping a whole list would remove obligations for its dependency-free transactions. | ||
|
|
||
| For a transaction imposing an inclusion obligation, omission is permitted only when EIP-7805 excuses it or `dependencies_fit_block(dependencies(block) + dependencies(tx))` is false. Capacity is evaluated against the complete final block dependency union, including when EIP-7805 evaluates transaction validity at an earlier index. Dependencies already present in the block consume no additional capacity. Local mempool limits, proving time, proof retention or aggregation scheduling are not additional omission grounds. |
Contributor
There was a problem hiding this comment.
Can 16 list proofs plus one wrapper proof be merged in time, given leanVM takes at most 16 children per step?
Marchhill
force-pushed
the
eip8288-focil-conditions
branch
from
October 14, 2026 20:12
2050668 to
5a4206f
Compare
This was referenced Oct 14, 2026
|
|
||
| The weights and unit budget are provisional, pending worst-case circuit benchmarks for the activated verification profiles, memory use and slot deadlines, including recursive merges and discards needed for IL obligations. The activating fork must fix them together with gas pricing; clients must not choose weights or capacity from local measurements. They are consensus capacity units, not an additional gas charge. | ||
|
|
||
| The circuit identified by `AGGREGATED_VK` must support every valid block dependency set within both bounds. Its separate private-input and verification-work limits still apply. Local proving budgets and mempool policy do not reduce block capacity and are not grounds for omitting an inclusion-list transaction. |
Contributor
There was a problem hiding this comment.
Should the private-input bounds be required to cover the discards from pruning one IL's proof? Otherwise a builder could be obliged to include a tx it can't prove.
Marchhill
changed the title
…eip8288-focil-conditions
…p8288-scheme-bound-deps
…eip8288-focil-conditions
3 tasks done
…rsive input count check, and fix the gas share wording
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
3 participants
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.
Depends on #12473, inheriting #12479's proof-in-body baseline. Review changes above the wrapper baseline. Also includes the independent zero-hash clarifications from #12518.
Defines EIP-8288's changes to EIP-7805 in one section: inclusion obligations, signed proof commitments, availability and retention, Engine methods, and activation requirements.
Validation: Markdown lint, structural EIP checks and shared-baseline consistency checks pass. Performance benchmarks remain outstanding activation requirements.