Skip to content

Reset execution and Beacon identity together - #85

Draft
0x00101010 wants to merge 8 commits into
feat/beacon-slot-endpointsfrom
feat/beacon-atomic-reset
Draft

0x00101010 wants to merge 8 commits into
feat/beacon-slot-endpointsfrom
feat/beacon-atomic-reset

Conversation

@0x00101010

Copy link
Copy Markdown

Why

Changing an execution fork before Beacon metadata or account reads finish can destroy the current chain on failure. Prepare the replacement database and genesis accounts before changing live state.

What

  • Serialize reset and state operations with mining.
  • Prepare both upstreams and fund staged genesis accounts before replacement.
  • Preserve history, accounts, blobs, snapshots, metadata, and clock on failed reads.
  • Clear slot restrictions when resetting to in-memory mode.

Notes

  • Implementation, tests, and review assisted by Amp.

Amp-Thread-ID: T-01a10d69-00b6-7378-855f-af2b1a148692
Amp-Thread-ID: T-01a10d69-00b6-7378-855f-af2b1a148692
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant