Add pre-fork EIP-8282 contract deployment playbook (gloas-dev)#217
Merged
Conversation
pk910
approved these changes
Jul 13, 2026
qu0b
added a commit
to ethpandaops/ansible-collection-general
that referenced
this pull request
Jul 13, 2026
…le (#559) ## What The assertoor values template hardcodes `assertoorTests: []`, so there is no way to register assertoor tests from a devnet's inventory — test registration currently happens ad-hoc via the assertoor API and is lost on redeploys. This adds a `gen_kubernetes_config_assertoor_tests` role var (default `[]`, keeping current output byte-identical) that is rendered into `assertoorTests` when set. Entries use assertoor's external-test registration schema, e.g.: ```yaml gen_kubernetes_config_assertoor_tests: - id: deploy-eip8282-contracts file: https://raw.githubusercontent.com/ethpandaops/assertoor/master/playbooks/gloas-dev/deploy-eip8282-contracts.yaml schedule: startup: true ``` ## Why glamsterdam-devnet-7 omits the EIP-8282 builder request contracts from genesis and deploys them pre-gloas via an assertoor startup test (ethpandaops/assertoor#217). That test must be registered declaratively so it survives redeploys and runs as soon as assertoor comes up. ## Verification Rendered the new block with ansible (`to_nice_yaml | indent`) against a populated list — output parses back to the exact registration entries; with the var unset the template still renders `assertoorTests: []`.
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.
What
New playbook
playbooks/gloas-dev/deploy-eip8282-contracts.yamlthat deploys the EIP-8282 builder deposit (0x03) and builder exit (0x04) system contracts onto a running devnet before the GLOAS fork activates.glamsterdam-devnet-7 deliberately omits these predeploys from genesis (
DEPLOY_EIP8282_CONTRACTS=false) to exercise the mainnet-like deployment workflow — from GLOAS activation onward every block is invalid unless both contracts exist. This playbook is meant to be registered as a startup test on the devnet so the contracts land right after launch.How
0x4e59...956C, predeployed in devnet genesis as a well-known contract) using the vanity-mined salt + initcode pairs from ethereum/execution-specs#3091 (builder_{deposit,exit}_factory_deploy.json). The factory reverts when CREATE2 fails (including the already-deployed collision case), so a successful receipt is proof of deployment (failOnReject: true).eth_callprecheck against the deposit contract's fee getter detects existing code (0x= missing, 32-byte fee = deployed; never reverts) and skips deployment on re-runs, so a startup-scheduled test stays green across assertoor restarts. The exit contract cannot be prechecked the same way — its constructor arms the slot-0 excess inhibitor, making its fee getter revert by design until the first post-GLOAS system call — so its deployment is asserted via the deploy receipt (the pair only ever deploys together).Verification
CREATE2(factory, salt, initcode)recomputed withcastfrom the embedded calldata → matches the canonical addresses0x0000bFF4...8282/0x000064D6...8282; the initcode runtime is byte-identical to the egg v6.1.3 genesis predeploy (source: ethereum/sys-asm).assertoor validatepasses with the playbook registered as an external test.