Skip to content

Serve fork-aware Beacon endpoints - #84

Draft
0x00101010 wants to merge 9 commits into
feat/beacon-historical-blobsfrom
feat/beacon-slot-endpoints
Draft

0x00101010 wants to merge 9 commits into
feat/beacon-historical-blobsfrom
feat/beacon-slot-endpoints

Conversation

@0x00101010

Copy link
Copy Markdown

Why

A private execution fork must serve historical Beacon data without mixing its local continuation with upstream blocks. Capture the slot identity and route each request across the pinned boundary.

What

  • Add the opt-in Beacon endpoint configuration and startup validation.
  • Serve stable genesis and slot metadata plus filtered JSON and SSZ blobs.
  • Resolve later slots only to exact canonical local blocks.
  • Hide upstream successor and competing-boundary blocks, transactions, logs, receipts, and traces.
  • Exercise routing with independent local execution and Beacon providers.

Notes

  • The larger diff retains shared fixtures and boundary regressions together.
  • 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