The post proposes a simple rule to preserve unconditional data censorship resistance in EIP-7999 once EIP-8279 combines calldata and EIP-7928 BAL data into a single data resource, which makes the existing 8 KiB per-IL (128 KiB total) inclusion-list bound insufficient. It divides the block's transaction data byte limit equally among the sixteen inclusion lists (e.g., ~228.9 KiB per IL under a 60M data-gas limit at 16 data gas per byte) and validates ILs on declared data_byte_limit sums rather than actual consumption, so validators never need to execute omitted transactions. The author argues this preserves unconditional data CR for essentially all ordinary transactions, covering single-contract deployments under EIP-7954's 64 KiB runtime-code limit, while unusually data-heavy transactions could be split or included without an IL guarantee.
This item was indexed from its published source and tied to the entity records it names. The Counterparty reports what the market says and who it says it about; it does not rewrite the original report. Read the source for the full account.