Skip to content

internal/era: random access to header and receipts #31544

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.

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

Merged
merged 6 commits into from
Apr 4, 2025

Conversation

s1na
Copy link
Contributor

@s1na s1na commented Apr 2, 2025

This will be required to serve API requests for header and receipts.

@s1na s1na requested a review from lightclient as a code owner April 2, 2025 10:26
Copy link
Member

@lightclient lightclient left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation looks good, couple nits.

@lightclient lightclient self-assigned this Apr 2, 2025
@lightclient lightclient force-pushed the era/get-header-receipt branch from 94b39ec to 48248e6 Compare April 3, 2025 15:05
@lightclient
Copy link
Member

Made a few changes, PTAL!

@s1na
Copy link
Contributor Author

s1na commented Apr 4, 2025

I can't approve my own PR but your changes look good to me! I plan to hook the era db up at the freezer level next.

@lightclient lightclient merged commit 77dc1ac into ethereum:master Apr 4, 2025
4 checks passed
@lightclient lightclient added this to the 1.15.8 milestone Apr 4, 2025
sivaratrisrinivas pushed a commit to sivaratrisrinivas/go-ethereum that referenced this pull request Apr 21, 2025
Co-authored-by: lightclient <lightclient@protonmail.com>

Add GetHeaderByNumber and GetReceiptsByNumber to allow more efficient API request filling from Era files.
Rampex1 pushed a commit to streamingfast/go-ethereum that referenced this pull request May 15, 2025
Co-authored-by: lightclient <lightclient@protonmail.com>

Add GetHeaderByNumber and GetReceiptsByNumber to allow more efficient API request filling from Era files.
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.

2 participants