web3wagmi
← All standards

EIP-8256 Blob Streaming

DraftCorecreated 2026-05-06requires EIP-2935, EIP-4788, EIP-4844, EIP-7002, EIP-7594, EIP-7732, EIP-7918

Introduces ahead-of-time blob propagation via ticket-based capacity reservation.

Authors: Marios (@mariosioannou-create), Bharath (@bharath-123), Francesco D'Amato (@fradamt), Julian Ma (@ma-julian), Raúl Kripalani (@raulk), Bosul Mun (@healthykim), Csaba Kiraly (@cskiraly), Anders Elowsson (@anderselowsson)

Depends on (7)

Proposals this one names in its requires field.

EIP-2935Serve historical block hashes from stateEIP-4788Beacon block root in the EVMEIP-4844Shard Blob TransactionsEIP-7002Execution layer triggerable withdrawalsEIP-7594PeerDAS - Peer Data Availability SamplingEIP-7732Enshrined Proposer-Builder SeparationEIP-7918Blob base fee bounded by execution cost

What the specification covers

AbstractMotivationSpecificationParametersHelpersBlob Transaction ClassificationBlock Header ChangesBlock ValidationEL Mempool ChangesReplacementsOpcode ChangesSystem Call OrderingTicket ContractStorage LayoutTarget slotCode Paths1. Buy Tickets (User Call with Value)2. Fee Getter (Zero-Value Call with Empty Calldata)3. System Call (End of Block)Ticket expiry semanticsFee MechanismConsensus Layer ChangesExecution Payload ModificationsP2P GossipData AvailabilityEngine API Changesengine_forkchoiceUpdatedV5PayloadAttributesV5engine_newPayloadV6engine_getPayloadV7engine_getBlobsV3RationaleUnified fee mechanismFee state in a system contractNon-refundable ticketsSeparate JIT and AOT capacity limitsBLS key commitment in ticketsRing buffer storageNo target slot in contract storageCapacity parameter communicationCensorship resistanceBackwards CompatibilitySecurity ConsiderationsCapacity griefing via ticket purchaseFee manipulationBuilder centralizationAOT gossip validationTicket front-runningReorg handlingCopyright

This proposal declares no Solidity interface, so there is nothing to compute. It may be a core protocol change, a meta proposal, or written in prose only.

Compare with

Parsed from the canonical specification · discussion