feat(playbooks): add glamsterdam-devnet-6 network-level EIP test suite#197
Closed
qu0b wants to merge 3 commits into
Closed
feat(playbooks): add glamsterdam-devnet-6 network-level EIP test suite#197qu0b wants to merge 3 commits into
qu0b wants to merge 3 commits into
Conversation
5 playbooks covering Amsterdam EIP behaviors that require a live running network and cannot be covered by EELS state tests: - EIP-7778: verifies block.gasUsed diverges from sum(receipt.gasUsed) when refund txs are mined (multi-slot block gas accounting) - EIP-7843: cross-validates SLOTNUM opcode value against CL beacon API - EIP-7928: reads blockAccessListHash from all EL clients simultaneously to verify cross-client consistency - EIP-7975/8159: checks p2p protocol version negotiation via admin_peers - EIP-8282: builder deposit/exit lifecycle requiring CL slot progression EVM semantics EIPs (7708, 8246, 8038, 7954, etc.) are covered by the EELS spec test suite (see glamsterdam-devnet-6-eels-tests.yaml).
qu0b
force-pushed
the
qu0b/feat/glamsterdam-devnet-6-playbooks
branch
from
5e6fc07 to
0a16427
Compare
qu0b
changed the title
The pseudo-version v0.1.4-0.20260618225213-e8d135e8cdc1 had ExecutionRequests with 3 fields (Deposits, Withdrawals, Consolidations). v0.1.4 adds BuilderDeposits and BuilderExits (EIP-8282), making it 5 fields. The SSZ decoder expected offset 12 (3×4) but blocks have offset 20 (5×4), causing 'incorrect offset: first offset 20 does not match expected 12' on every Gloas block. BUG-032. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Amsterdam state gas (EIP-8037) charges ~1530 gas/byte for code storage. A 30KB contract costs ~47M gas; a 60KB contract costs ~94M gas. At typical devnet gas prices (75-200 gwei), 1 ETH is insufficient to cover gas estimation (recap_with_account_balances caps too aggressively). Fund with 1000 ETH to allow deployment at up to ~500 gwei gas price.
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
2 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.
Summary
5 playbooks covering Amsterdam EIP behaviors that require a live running network — things EELS state tests cannot cover: cross-client consistency, CL/beacon API cross-validation, P2P protocol negotiation, multi-slot block accounting, and builder lifecycle flows.
EVM semantics EIPs (7708, 8246, 8038, 7954, etc.) are covered by the EELS spec test suite (see #198).
glamsterdam-devnet-6-eip7778-block-gasblock.gasUseddiverges fromsum(receipt.gasUsed)when refund txs are mined — requires real blocks across multiple slotsglamsterdam-devnet-6-eip7843-slotnumglamsterdam-devnet-6-eip7928-bal-hashblockAccessListHashfrom all EL clients simultaneously to verify cross-client consistencyglamsterdam-devnet-6-eip7975-8159-protocoladmin_peers— not testable in state testsglamsterdam-devnet-6-builder-lifecycleexecution_requestsin beacon blocksTest plan
passstatus