Skip to content

Bind Beacon state dumps to their fork identity - #86

Draft
0x00101010 wants to merge 4 commits into
feat/beacon-atomic-resetfrom
feat/beacon-state-identity
Draft

0x00101010 wants to merge 4 commits into
feat/beacon-atomic-resetfrom
feat/beacon-state-identity

Conversation

@0x00101010

Copy link
Copy Markdown

Why

State dumps without fork and Beacon identity can be interpreted against an incompatible chain. Persist that identity and reject incompatible loads before changing live state.

What

  • Record chain, boundary, Beacon genesis, slot duration, and simulated-finality settings.
  • Reject missing or mismatched identity without importing accounts or history.
  • Fail closed on Beacon loads while preserving legacy non-Beacon loading.
  • Share blob submission helpers across API and state regressions.

Notes

  • Connectivity credentials are not persisted.
  • 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