Skip to main content
netspecsEthereum networking

4.1.6.eth/vhash blob pool

Stage
Future
Validity
Future proposal; not yet reconstructed.
Sources
1 pinned source
Content
Pending reconstruction — no completeness claim is made.

Draft EIP-8094 separates a type-3 transaction from its blob sidecar. A fee replacement can reuse blobs that peers already hold under their versioned hashes.

Proposed flow

Transactions and PooledTransactions carry type-3 transactions without sidecars. A receiver gets the versioned hashes from the transaction, requests missing blobs, verifies their commitments and proofs, and only then forwards the transaction.

GetPooledBlobs requests blob data by versioned hash.

PooledBlobs returns available blobs in request order while omitting missing items.

Validation and failure handling

The receiver derives each returned versioned hash and matches it to the request. It checks KZG data before it joins the transaction and blobs. It does not relay an incomplete type-3 transaction.

Status and open points

The draft has no eth version, message codes, or final blob response encoding. The unassigned IDs above preserve that gap.

Design rationale

Content addressing lets a fee replacement reuse blob data that peers already verified under the same versioned hashes.