Thanks Emmanuel Nalepa for the review and contribution. TL;DR This doc aims to analyze PeerDAS sampling spec and propose a change to the spec to mitigate the underlying issue. Background EIP-7594: PeerDAS - Peer Data Availability Sampling proposes an intermediate step towards full Danksharding, its design separates network interaction between nodes into two phaes: distribution and sampling. During distribution phase, blobs were extended horizontally (1D PeerDAS), and then divided into NUMBER_OF_COLUMS (currently 128) sections and distributed across DATA_COLUMN_SIDECAR_SUBNET_COUNT (currently 32) subnets. Each node is required to custody at least CUSTODY_REQUIREMENT (currently 1) subnets (4 columns).

References: https://community.optimism.io/docs/developers/build/transaction-fees/ Overview Unlike L1 (Ethereum) transactions fees which will burn the base fee, pass priority fee to miners, distribute a block reward, Base (or the op stack) L2s have a different fee calculation mechanism. Sender On a high level, for a given transaction, it will be charged L2 execution fee => which is the same mechanism as L1if it is a EIP-1559 tx, then will be charged for BaseFee + PriorityFee if it is a legacy tx, then it will be charged for Gas Fee