EIPs
EIP-4844 — Shard blob transactions
A new transaction type (0x03) that carries blob sidecar data — fixed-size 128KB blobs that get hashed via KZG commitments and made available to L2s for a short period. Rollups use blobs as their data-availability layer.
import {
to_blobs,
commitment_to_versioned_hash,
blob_gas,
} from "@ethernauta/eip/4844";
const blobs = to_blobs(calldata);
// each blob is committed to via KZG; the versioned hash goes into the tx Surface
| Export | Purpose |
|---|---|
to_blobs | Convert raw bytes into FIELD-aligned blobs. |
commitment_to_versioned_hash | KZG commitment → versioned hash for the tx. |
blob_gas | Blob-gas pricing helpers. |
| KZG proof / commitment operations | Used by to_blobs internally. |
| Blob constants | Field sizes, max blobs per tx. |
| Blob transaction schemas | Valibot validators. |
When dapps need this
Most application dapps don’t construct blob transactions directly — they’re produced by rollup sequencers / batchers. The library exposes the primitives so that those consumers (and anyone debugging or inspecting blobs) can compose them.
The wallet does not yet ship a blob-transaction signing view; the send view rejects type-3 transactions with a clear “blob transactions require sequencer infrastructure” message. This is intentional — blob construction without a connected rollup pipeline doesn’t make sense.
See also
- EIP-1559 — the fee-market model blob fees extend.
- @ethernauta/eth → eth_blobBaseFee.