Blob Archive
The Blocknative Blob Archive stores all blobs that enter the mempool (confirmed on-chain or not) in the Ethereum network using our global network of nodes. Given any versionedHash
of an on-chain blob, the archive returns the versioned hash, commitment, proof, count of zero-bytes, count of non-zero bytes and blob data. If you only want a summary view of the blob data, the archive can return the response without the full blob data.
Full blob data
Given the versionedHash
of an on-chain blob, this will return the commitment, proof, count of zero bytes, count of non-zero bytes and blob data.
GET https://api.ethernow.xyz/v1/blob/{versionedHash}
Example Request
Example Response
Query Parameters
data
Bool
When data=false, the api will NOT include the blob data
Summary of blob data
Given the versionedHash
of an on-chain blob, this will return the commitment, proof, count of zero bytes, and count of non-zero bytes. Blob data will be empty.
GET https://api.ethernow.xyz/v1/blob/{versionedHash}?data=false
Example Request
Example Response
Description of Terms
Term descriptions come from the official EIP and EIP-4844 website. Please refer to both of these resources for more details on the terms below.
versionedHash
A single 0x01 byte (representing the version) followed by the last 31 bytes of the SHA256 hash of the commitment.
commitment
proof
The KZG commitment of the blob and a KZG proof-of-evaluation
data
The blob data itself where blob data is a vector of 4096 field elements, numbers within the range:
0 <= x < 52435875175126190479447740508185965837690552500527637822603658699938581184513
zeroBytes
The count of used zero bytes in the blob data not including zero padding
nonZeroBytes
The count of used non-zero bytes in the blob data
Questions
If you have any questions please join the Blocknative Mempool Research Telegram channel where our team can provide guidance.
Last updated