Skip to content

Validate Beacon time adjustments - #81

Closed
0x00101010 wants to merge 3 commits into
feat/beacon-slot-clockfrom
feat/beacon-time-validation
Closed

0x00101010 wants to merge 3 commits into
feat/beacon-slot-clockfrom
feat/beacon-time-validation

Conversation

@0x00101010

Copy link
Copy Markdown

Why

Explicit time changes must not reuse slots, move behind the canonical tip, or overflow the supported date range. Validate settings while retaining legacy behavior outside slot mode.

What

  • Reject off-grid timestamps and invalid slot intervals.
  • Preserve the canonical tip when moving the clock.
  • Bound extreme adjustments while allowing mining to continue.

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
@0x00101010 0x00101010 closed this Oct 26, 2026
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