Skip to content

Contract the legacy B20 genesis allocation #69

Closed

Description

@mowind

Parent

#64

What to build

Complete the contract phase of the expand-contract migration. Move every remaining test and consumer away from the raw B20 genesis allocation, delete the legacy allocation and duplicate HashKey state-plan surface, and enforce static and behavioral gates that leave the shared profile-owned seam as the only canonical interface.

Integration tests observe addresses through existing network projections, feature admission through ABI behavior, or independent fixed fixtures where raw storage is itself under test. They do not use the production initializer as both input and oracle.

Acceptance criteria

  • Remaining network, backend, node, and CLI tests no longer index marker or feature-seed arrays or depend on tuple layout.
  • Canonical B20 recipe coverage exists only at the shared module seam; production adapter tests focus on translation and lifecycle behavior.
  • The public raw B20 genesis allocation type, constructor, and profile getter are deleted.
  • The HashKey state-plan variant is deleted while the specialized Tempo initialization path remains unchanged.
  • All duplicate Forge and Anvil allocation loops and migration bridges are deleted.
  • Production backend code contains no copied B20 marker application recipe.
  • Static source checks prove the legacy allocation symbols, array-field indexing, and backend-local marker loops have zero matches.
  • Default and no-HashKey builds compile without leaking a HashKey-only dependency into production callers.
  • HashKey standalone, fork, reset, snapshot, later-EVM, and custom-genesis focused suites pass.
  • Existing Ethereum, Optimism, Celo, and Tempo behavior remains unchanged.
  • Legal CLI stdout, stderr, JSON, quiet, verbosity, exit status, RPC result, trace, and state-transition behavior remains unchanged.
  • Formatting, linting, focused integration suites, and workspace validation introduce no new failures; any known unrelated pre-existing failures are reported separately.

Blocked by

Activity

  1. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Implemented and pushed in 97952f9.

  2. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Follow-up hardening pushed in e35ab9b: explicit backing-state targets, adapter contract coverage, snapshot/custom-genesis lifecycle coverage, and review fixes.

  3. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Additional follow-up pushed in 6b903a0: release the adapter lock before the preserved Tempo initializer.

  4. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Test-only fixture gating pushed in 7bfc1e1.

  5. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Final coverage follow-up pushed in 346b4de: nonce/feature precedence assertions and Cast trace-identity projection.

  6. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Final standards-review fix pushed in d286fda.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified and ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions