Go to Home
Web3 security pattern.
Pectra Competition
Web3 security pattern.
EIP-7691
EIP-7691 raises Ethereum’s blob limits to 9 max and 6 target per block, boosting rollup data throughput until long-term scaling arrives.EIP-7691 increases blob limits to enhance rollup data availability, providing a temporary scaling boost before peerDAS is implemented.

EIP-7691

Table of Contents

Heading 2
Heading 3
Heading 4

What is this EIP about?

EIP-7691 proposes increasing the maximum and target number of blobs per block in Ethereum to 9 and 6, respectively. This change aims to temporarily improve data throughput for rollups, pending the implementation of long-term scaling solutions like peerDAS.

The proposal addresses current data availability limitations, providing a short-term scaling boost to Layer 2 (L2) rollup solutions that rely on Ethereum's data capacity.

Why is this EIP needed?

Ethereum’s roadmap heavily emphasizes rollup-centric scaling, where rollups use blobs to store transaction data on-chain. The current blob limits (set during the Dencun upgrade) constrain data throughput, potentially slowing L2 performance and adoption.

  • Limitations:
    1. Blob capacity: The current limit of 3 blobs per block restricts the amount of data rollups can commit to Layer 1 (L1).
    2. Future uncertainty: Long-term solutions like peerDAS are not yet implemented, leaving a gap in Ethereum’s scalability.

This proposal focuses on data availability and scalability, which are critical for supporting Ethereum’s growing rollup ecosystem and ensuring that L2 solutions remain performant.

‍What does this EIP propose, and how does it function?

  • Key Proposal:
    1. Blob Limits:
      • Increase the maximum blobs per block to 9.
      • Increase the target blobs per block to 6.
    2. Base Fee Adjustments:
      • Adjust the blob base fee update fraction to account for the new blob limits. This ensures that base fee changes remain responsive to network usage.
  • Technical Details:
    1. Updated Constants:

‍

  1. Base Fee Sensitivity:
    • Full blobs increase base fees by ~8.2%.
    • No blobs decrease base fees by ~14.5%.
  2. Transition Mechanism:
    • Consensus clients use updated constants starting at the ELECTRA fork epoch.
    • Execution clients adopt new parameters during the PRAGUE fork.

What are the security implications of this EIP?

  • Potential Risks:
    1. Network Bandwidth: Increasing blob limits might strain network bandwidth, particularly for validators with limited resources.
    2. Fork Stability: Adjusting blob limits at the fork transition could cause temporary instability.
    3. Base Fee Sensitivity: Misaligned base fee adjustments could lead to unpredictable fee markets or congestion.
  • Mitigations:
    1. Big Block/Blob Testing: Comprehensive mainnet and testnet simulations ensure that higher blob limits do not compromise network stability.
    2. Monitoring: Enhanced monitoring during and after the fork transition ensures any issues are quickly identified and addressed.
    3. Gradual Adjustment: Changes are designed to be incremental and minimally disruptive, allowing for smooth adoption.

EIP-7691 is a practical, short-term solution to enhance Ethereum’s scalability by increasing data availability, supporting the ecosystem’s reliance on rollups until more robust scaling technologies are deployed.