This EIP adds a flag to the block builder in order to allow them to include a client configured maximum amount of blobs. This is an execution layer only change.
Currently a builder will include all blobs in their local mempool, up to the maximum amount that the protocol requires. If a builder has low bandwidth, they may include too many blobs and subsequently end up not being able to convince the network that the blobs are available.
USER_CONFIGURED_MAX_BLOBS_PER_BLOCKMAX_BLOB_GAS_PER_BLOCK and the USER_CONFIGURED_MAX_BLOBS_PER_BLOCKNote: By default USER_CONFIGURED_MAX_BLOBS_PER_BLOCK may be set to the maximum in the current fork.
By adding a flag for the local block builder, they are able to specify how many blobs they can include in a block.
No backward compatibility issues found.
N/A
Copyright and related rights waived via CC0.