Skip to content

Read upstream Beacon identity safely - #82

Draft
0x00101010 wants to merge 3 commits into
feat/beacon-time-validationfrom
feat/beacon-upstream-identity
Draft

0x00101010 wants to merge 3 commits into
feat/beacon-time-validationfrom
feat/beacon-upstream-identity

Conversation

@0x00101010

Copy link
Copy Markdown

Why

A fork needs a captured Beacon genesis and slot duration before serving historical data. Validate their alignment with the execution timestamp using bounded metadata reads.

What

  • Capture genesis and slot duration and convert slots without overflow.
  • Preserve endpoint paths and credential queries without leaking URLs in errors.
  • Bound response sizes and timeouts and refuse redirects.

Notes

  • This backend capability does not expose a CLI mode.
  • 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