Skip to content

Implement engine_getBlobsV1 #12284

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

Closed
somnathb1 opened this issue Oct 11, 2024 · 3 comments · Fixed by #13975
Closed

Implement engine_getBlobsV1 #12284

somnathb1 opened this issue Oct 11, 2024 · 3 comments · Fixed by #13975
Assignees
Labels
Milestone

Comments

@somnathb1
Copy link
Contributor

Rationale

Why should this feature exist?
Helps CL fetch blobs directly from the EL's mempool, not having to wait on p2p to get blobs

What are the use-cases?
To be used by CLs and Caplin

Refer to https://github.com/ethereum/execution-apis/blob/main/src/engine/cancun.md#engine_getblobsv1

Implementation

Do you have ideas regarding the implementation of this feature?

  • Create a memory map for Blob hashes in the TxPool
  • Implement method eth_getBlobs in the Engine-API

Are you willing to implement this feature?
Yeah

@jasonyic
Copy link

I am still getting the following error on erigon v3.0.0, thought was merged already 3 weeks earlier

2025-03-26 09:45:19.837 WARN  - Local EL blobs lookup failed: Invalid remote response from the execution client: JSON-RPC error: Method not found (-32601): the method engine_getBlobsV1 does not exist/is not available

@somnathb1
Copy link
Contributor Author

I am still getting the following error on erigon v3.0.0, thought was merged already 3 weeks earlier

2025-03-26 09:45:19.837 WARN  - Local EL blobs lookup failed: Invalid remote response from the execution client: JSON-RPC error: Method not found (-32601): the method engine_getBlobsV1 does not exist/is not available

We had a code-freeze, didn't make it to the release in time. cc @yperbasis

@jasonyic
Copy link

thank you, just to confirm.

@yperbasis yperbasis added this to the 3.1.0 milestone Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants