web3wagmi
← All standards

EIP-8101 Payload Chunking with Chunk Access Lists

DraftCorecreated 2025-12-01requires EIP-4844, EIP-4895, EIP-7732, EIP-7825, EIP-7928

Semantic payload chunking with separated state diffs for streaming validation and reduced latency

Authors: Toni Wahrstätter (@nerolation), Milos Stankovic (@morph-dev), Jihoon Song (@jihoonsong), Bharath Vedartham (@bharath-123), Raúl Kripalani (@raulk)

Depends on (5)

Proposals this one names in its requires field.

EIP-4844Shard Blob TransactionsEIP-4895Beacon chain push withdrawals as operationsEIP-7732Enshrined Proposer-Builder SeparationEIP-7825Transaction Gas Limit CapEIP-7928Block-Level Access Lists

What the specification covers

AbstractMotivationSpecificationConstantsType AliasesData StructuresExecution ChunkChunk Access Lists (CALs)ExecutionPayload and ExecutionPayloadHeaderBeacon Block CommitmentsNetwork TopisChunk Construction RulesNetwork ProtocolGossip TopicsMessage ValidationConsensus Layer ChangesTypesStore ExtensionsThree-Phase ValidationPhase 1: CAL ReceptionPhase 2: Chunk ValidationPhase 3: Block FinalizationAttestation RulesExecution Layer ChangesChunk ExecutionEngine APIengine_newBlockHeaderV1engine_newChunkAccessListV1engine_executeChunkV1engine_finalizeBlockV1Response TypesRationaleIncremental CALsCL-Driven ArchitectureSeparate CAL PropagationSemantic ChunkingParameter SelectionBackwards CompatibilitySecurity ConsiderationsData Availability AttacksCopyright

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