From a6389a75e75ef7335afcedf9531c847404d67d47 Mon Sep 17 00:00:00 2001 From: Parithosh Jayanthi Date: Fri, 22 Nov 2024 18:28:24 +0700 Subject: [PATCH] Update EIP-7691: Updating eip with blob count Merged by EIP-Bot. --- EIPS/eip-7691.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/EIPS/eip-7691.md b/EIPS/eip-7691.md index a2426fc09ad992..62edb91169b05f 100644 --- a/EIPS/eip-7691.md +++ b/EIPS/eip-7691.md @@ -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 @@ -10,8 +10,6 @@ category: Core created: 2024-04-17 --- - - ## 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. @@ -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` | -| `MAX_BLOBS_PER_BLOCK` | `tbd` | +| Constant | Value | +|----------------------------------|---------------------| +| `PECTRA_FORK_EPOCH` | `tbd` | +| `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 @@ -52,7 +53,7 @@ Through the use of big block/blob tests on Ethereum mainnet as well as testnets, ## Backwards Compatibility -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