web3wagmi
← All standards

EIP-8146 Block Access List Sidecars

DraftCorecreated 2026-02-03requires EIP-7732, EIP-7928

Propagate block access lists as independent sidecars, off the critical path and ahead of the execution payload

Authors: Toni Wahrstätter (@nerolation), Raúl Kripalani (@raulk)

Depends on (2)

Proposals this one names in its requires field.

EIP-7732Enshrined Proposer-Builder SeparationEIP-7928Block-Level Access Lists

What the specification covers

AbstractMotivationSpecificationExecution LayerConsensus LayerConstantsTypesContainersExecutionPayloadExecutionPayloadBidPayloadAttestationDataBlockAccessListSidecarFork ChoiceStoreon_blockon_payload_attestation_messageon_block_access_list_sidecaron_execution_payload_envelopeNetworkingGossip: block_access_list_sidecarReq/RespValidator DutiesBuildersPTC MembersEngine APIengine_getPayloadV6engine_notifyBlockAccessListV1engine_newPayloadV5RationaleHeader Commitment ReuseNo Sidecar SignatureSeparate PTC FieldPublication TimingDedicated Engine API MethodSidecar RetentionBackwards CompatibilitySecurity ConsiderationsWithholdingEarly BAL ExposureNetwork OverheadVerification CostUnmatched BALsCopyright

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