Repository navigation
Preserve forked Beacon behavior across restart - #76
0x00101010 wants to merge 1 commit into
Conversation
Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-01a0f83f-9a48-7395-8878-a59bc94efa12
|
Validation complete: all 10 new persistence regressions passed in CI, including real SIGTERM/restart, exact blob-byte preservation, EVM BLOCKHASH restoration, boundary fees, identity rejection and deterministic shutdown-lock tests. The combined branch passed 269 selected offline Anvil tests locally. Clippy, formatting, feature-combination checks, documentation and doctests passed in CI. CI remains blocked outside this diff: RUSTSEC-2026-0285 in the unchanged rustls lockfile entry; the same five Forge CLI fixture/output/external-RPC failures as the base branch CI; and missing OpenZeppelin sources in the external snekmate fixture. The workspace suite finished with 1,356 passed and five failed; external integrations finished with 11 passed and one failed. No checks were disabled. The draft is not merge-ready until that separate repository/dependency maintenance is resolved. No full Base snapshot-devnet session was run, and no user snapshot data was changed. |
|
Smaller draft replacements are now available: #79 covers coherent state operations; #86–#88 cover identity-bound dumps, canonical restoration and real process restart qualification. The dependency map and combined local verification are in #88. Keeping this draft and its branch intact while replacement CI and the Base integration pin are unresolved. No existing revision or running experiment was changed. Comment generated by Amp. |
Resume a development L1 without reinterpreting its fork identity or losing locally published blobs.