Skip to content

Migrate Forge local genesis state #67

Closed

Description

@mowind

Parent

#64

What to build

Migrate Forge's complete local-genesis lifecycle to the shared profile-owned seam. Fresh non-fork backend construction receives the canonical B20 baseline, fork-backed construction performs no local profile writes, and all later, nested, cloned, inspected, and derived execution contexts inherit current state without replaying genesis.

The Forge adapter translates the two generic capabilities into backend mutations while preserving unrelated account state and deriving code hash from code bytes.

Acceptance criteria

  • Fresh standalone Forge backend construction applies profile-owned local genesis through the shared seam exactly once.
  • Fork-backed Forge construction uses the remote-fork target and performs no profile-owned local writes.
  • Forge production code no longer reads or iterates the legacy B20 allocation and contains no backend-local marker literal or independently transported marker hash.
  • Account patching preserves pre-existing balance, unrelated storage, and non-owned account fields.
  • Marker code hash is correctly derived from the supplied code bytes.
  • Single-slot writes preserve account information and unrelated storage slots.
  • A changed feature admission value remains changed across normal, inspected, nested, and later EVM creation.
  • Cloned backends preserve current B20 state, while empty or derived reusable backends do not implicitly receive profile genesis.
  • Snapshot and revert continue to use ordinary backend and journal state without invoking the profile-owned seam.
  • Adapter failures retain their source error and prevent backend construction from publishing an executable backend.
  • Focused Forge lifecycle and adapter tests pass through the shared profile-owned entry point.

Blocked by

Activity

  1. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Implemented and pushed in 6d629b7.

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