Skip to content

Commit

Permalink
Update EIP-7691: Updating eip with blob count
Browse files Browse the repository at this point in the history
Merged by EIP-Bot.
  • Loading branch information
parithosh authored Nov 22, 2024
1 parent cf5db57 commit a6389a7
Showing 1 changed file with 9 additions and 8 deletions.
17 changes: 9 additions & 8 deletions EIPS/eip-7691.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
eip: 7691
title: Blob throughput increase
description: Increase the number of blobs to reach a new target of x blobs per block, to be defined by performing tests.
description: Increase the number of blobs to reach a new target and max of 6 and 9 blobs per block respectively
author: Parithosh Jayanthi (@parithosh), Toni Wahrstätter (@nerolation), Sam Calder-Mason (@samcm), Andrew Davis (@savid)
discussions-to: https://ethereum-magicians.org/t/eip-7691-blob-throughput-increase/19694
status: Draft
Expand All @@ -10,8 +10,6 @@ category: Core
created: 2024-04-17
---

<!-- TODO: Update "x" in the description above -->

## Abstract

This EIP proposes to increase to the number of blobs in a block to provide more scale to Ethereum via L2 solution that rely on L1 data capacity.
Expand All @@ -31,10 +29,13 @@ The current long term plan of Ethereum is to implement peerDAS as specified by [

### Parameters

| Constant | Value |
| - | - |
| `PECTRA_FORK_EPOCH` | `tbd` <!-- TODO --> |
| `MAX_BLOBS_PER_BLOCK` | `tbd` <!-- TODO --> |
| Constant | Value |
|----------------------------------|---------------------|
| `PECTRA_FORK_EPOCH` | `tbd` <!-- TODO --> |
| `MAX_BLOBS_PER_BLOCK_ELECTRA` | `9` |
| `TARGET_BLOBS_PER_BLOCK_ELECTRA` | `6` |

The values defined are consumed by the consensus layer clients and are passed via the engineAPI to the execution layer clients. The mechanism describing this uncoupling is specified in [EIP-7742](./eip-7742.md).

## Rationale

Expand All @@ -52,7 +53,7 @@ Through the use of big block/blob tests on Ethereum mainnet as well as testnets,

## Backwards Compatibility

todo <!-- TODO -->
The consensus clients would continue to use `MAX_BLOBS_PER_BLOCK` for the deneb fork and once the `ELECTRA` fork is active, they would use `MAX_BLOBS_PER_BLOCK_ELECTRA`.

## Security Considerations

Expand Down

0 comments on commit a6389a7

Please sign in to comment.