Setup for the Glamsterdam hardfork: schedule, block header, and fixture harness - #2870
Open
anvacaru wants to merge 10 commits into
Open
Setup for the Glamsterdam hardfork: schedule, block header, and fixture harness#2870anvacaru wants to merge 10 commits into
anvacaru wants to merge 10 commits into
Conversation
…sterdam (Glamsterdam EL) schedule
….py: parse Amsterdam block header (blockAccessListHash, slotNumber); discard receipts/blockAccessList fixture keys in the harness
…v7.2.0 from ethereum/execution-specs
… max 21 / fraction 11684671) AMSTERDAM inherited the Osaka/Prague blob parameters (target 6 / max 9 / fraction 5007716). EELS amsterdam vm/gas.py has BLOB_SCHEDULE_TARGET = 14 and BLOB_SCHEDULE_MAX = 21 (at PER_BLOB = 2^17: Gtargetblobgas = 1835008, Gmaxblobgas = 2752512) and BLOB_BASE_FEE_UPDATE_FRACTION = 11684671, matching the mainnet BPO2 blob schedule (EIP-8135 / EIP-7892) that Amsterdam starts from. Raising Gmaxblobgas from 9 to 21 blobs exposes the pre-existing missing EIP-7594 per-tx blob limit (EELS BLOB_COUNT_LIMIT = 6, fork.py:150): the blob_count_21 sub-case of invalid_max_blobs_per_tx was previously rejected by the too-small inherited block max instead of the per-tx check. Mask it in failing.llvm next to its already-masked blob_count_7/8 siblings until the per-tx limit is implemented. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
read_csv_file crashed test collection with IndexError on any blank line in failing.llvm/slow.llvm — which the fixtures-failing-list Makefile target itself can produce via its sort/sed post-processing. Skip empty rows.
# Conflicts: # kevm-pyk/src/kevm_pyk/kproj/evm-semantics/driver.md
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.
Defining the base for the Amsterdam (Glamsterdam EL) fork: the schedule, the new block-header shape, and the conformance fixture pin. Individual Amsterdam EIP PRs will build on this.
Changes:
AMSTERDAMschedule (inherits Osaka) wired throughgst_to_kore/cli.blockAccessListHash(EIP-7928), andslotNumber(EIP-7843)). The<balHash>/<slotNumber>cells are populated and hash-validated as header fields here; their semantics land with the EIP-7928/EIP-7843 PRs.receipts/blockAccessListfixture bodies in the harness (_GST_DISCARD_KEYS): both are committed to by header fields (receiptTrie,blockAccessListHash), so the bodies carry no extra validation signal.tests-glamsterdam-devnet@v7.2.0(from ethereum/execution-specs).