-
-
Notifications
You must be signed in to change notification settings - Fork 411
feat: update blobs endpoint to use versioned_hashes instead of indices as filter #8264
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @nflaig, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request updates the getBlobs Beacon API endpoint to align with recent changes in the Ethereum beacon-APIs specification. Specifically, it modifies the filtering mechanism for blobs from using numerical indices to cryptographic versioned_hashes, reflecting the ongoing evolution of the Ethereum protocol, particularly in the context of EIP-4844 (Dencun upgrade).
Highlights
- API Signature Update: The "getBlobs" endpoint's query parameter for filtering blobs has been changed from "indices" (an array of numbers) to "versioned_hashes" (an array of strings), impacting both type definitions and request/response handling.
- Internal Blob Filtering Logic: The backend implementation of "getBlobs" has been refactored to process "versioned_hashes". This involves deriving versioned hashes from KZG commitments within the block and then selecting the corresponding blobs.
- Test Data Alignment: Unit tests for the "getBlobs" endpoint have been updated to reflect the new "versioned_hashes" parameter, ensuring consistency with the API's revised signature.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request updates the getBlobs beacon API to filter by versioned_hashes instead of indices, aligning with recent specification changes. The changes correctly update the API route definitions, test data, and implementation logic. I have two suggestions for the implementation in packages/beacon-node/src/api/impl/beacon/blocks/index.ts. First, the uniqueness check for versionedHashes should be case-insensitive to match the lookup logic. Second, the logic for finding blob indices can be optimized for better performance and readability by using a Map.
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## unstable #8264 +/- ##
============================================
- Coverage 54.15% 54.14% -0.01%
============================================
Files 849 849
Lines 63991 64012 +21
Branches 4852 4852
============================================
+ Hits 34652 34658 +6
- Misses 29262 29277 +15
Partials 77 77 🚀 New features to boost your workflow:
|
Performance Report🚀🚀 Significant benchmark improvement detected
Full benchmark results
|
|
upstream spec PR has been merged |
|
🎉 This PR is included in v1.34.0 🎉 |
Motivation
Latest updates from ethereum/beacon-APIs#546
Description
Update
getBlobsbeacon api to useversioned_hashesinstead ofindicesas filter