You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Rebuild Anvil standalone state on local backing #65
Make Anvil's fork-to-standalone reset establish a genuinely local backing-state epoch before genesis is reapplied. Clearing the fork role must not leave a remote-capable database, stale fork cache, remote-only account or storage, or dynamically loaded B20 token state reachable from the new standalone node.
This is the prefactor that makes the later profile-owned genesis migration safe: FreshStandalone must describe the concrete database, not merely a boolean role flag.
Acceptance criteria
Resetting a forked node to standalone replaces or equivalently detaches the remote-capable database before generic and profile-owned genesis are reapplied.
The resulting standalone database has no remote fallback and cannot fetch previously unseen state from the former fork source.
Remote-only unrelated accounts and storage disappear after fork-to-standalone reset.
Remote or cached dynamic B20 token account and storage state disappear after fork-to-standalone reset.
The standalone node still restores its configured generic genesis accounts and current canonical B20 local baseline.
Standalone-to-standalone reset and fork-to-fork reset retain their existing behavior.
Focused tests use local deterministic nodes and do not depend on a public RPC endpoint.
Reset failures retain the existing non-atomic RPC error model; this ticket does not introduce rollback or staging-and-swap publication.
Implemented in commit ad80f34. Fork-to-standalone reset now replaces the remote-capable backing database with a fresh MemDb before genesis reapplication, and deterministic HashKey integration coverage verifies cached and previously unseen remote account/storage state, dynamic B20 state, generic genesis balance, and the B20 baseline. Focused Anvil tests and the HashKey-enabled Anvil suite pass. The workspace-wide suite still has the pre-existing cast stack-overflow failures and external Vyper fixture setup failure.
Activity
mowind commentedon Aug 4, 2026
Implemented in commit ad80f34. Fork-to-standalone reset now replaces the remote-capable backing database with a fresh MemDb before genesis reapplication, and deterministic HashKey integration coverage verifies cached and previously unseen remote account/storage state, dynamic B20 state, generic genesis balance, and the B20 baseline. Focused Anvil tests and the HashKey-enabled Anvil suite pass. The workspace-wide suite still has the pre-existing cast stack-overflow failures and external Vyper fixture setup failure.