Skip to content

Portal: Implementation of finalized history network WIP #3427

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 5 commits into
base: master
Choose a base branch
from
Draft

Portal: Implementation of finalized history network WIP #3427

wants to merge 5 commits into from

Conversation

kdeme
Copy link
Contributor

@kdeme kdeme commented Jun 25, 2025 •
edited
Loading

WIP, but starting to implement https://ethresear.ch/t/using-portal-network-protocol-for-history-expiry/22658

TODO (not necessarily all in this PR):

  • get receipts/body API
  • json-rpc API on top
  • Header Oracle or similar, allow for using (currently not existing) get header json RPC API from EL or just passing headers along when natively integrated
  • add network tests
  • probably some test vectors generation
  • adapt EL integration + bridging in data from EL
  • Might require ContentDb change due to same content id for BlockBody and Receipts. Unless specs change

@kdeme kdeme force-pushed the finalized-history-network branch 2 times, most recently from a6bab77 to 71dca54 Compare June 30, 2025 20:01
@kdeme kdeme force-pushed the finalized-history-network branch from 500d195 to 1a3cc5a Compare July 6, 2025 20:32
@kdeme
Copy link
Contributor Author

kdeme commented Jul 6, 2025

Specs PR now: ethereum/portal-network-specs#407

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@kdeme