Skip to content

Commit 355e7db

Browse files
authored
Merge e3a893d into 40ad571
2 parents 40ad571 + e3a893d commit 355e7db

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

EIPS/eip-7840.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
eip: 7840
33
title: Add blob schedule to EL config files
4-
description: Include a per-fork schedule of max and target blob counts in client configuration files
4+
description: Include a per-fork blob parameters in client configuration files
55
author: lightclient (@lightclient)
66
discussions-to: https://ethereum-magicians.org/t/add-blob-schedule-to-execution-client-configuration-files/22182
77
status: Review
@@ -19,6 +19,7 @@ target blob count per block and max blob count per block for each fork.
1919

2020
- ensure there is a way to dynamically adjust the target and max blob counts per
2121
block
22+
- ensure there is a way to dynamically adjust the blob base fee update fraction
2223
- avoid complex handshake over engine API
2324

2425
## Specification
@@ -30,17 +31,19 @@ following shape:
3031
"blobSchedule": {
3132
"cancun": {
3233
"target": 3,
33-
"max": 6
34+
"max": 6,
35+
"baseFeeUpdateFraction": 3338477
3436
},
3537
"prague": {
3638
"target": 6,
37-
"max": 9
39+
"max": 9,
40+
"baseFeeUpdateFraction": 5007716
3841
}
3942
}
4043
```
41-
42-
When there is no explicit configuration for the current fork, use the last
43-
specified fork value. If no last value is specified, set both to zero.
44+
Clients **MUST** explicitly configure blob parameters in the configuration for Ethereum mainnet.
45+
If there is no explicit configuration for the current fork, the client should use the last specified fork value.
46+
This EIP does not define the behavior when the configuration is missing; clients are free to choose how to handle this situation.
4447

4548
## Rationale
4649

@@ -50,7 +53,7 @@ for various activities. For example, the `eth_feeHistory` RPC method returns a
5053
field `blobGasUsedRatio` that does require the max, even though the core
5154
protocol doesn't specifically need such value. Passing this value over the
5255
engine API every block seem overkill so we believe a configuration value is a
53-
good middle ground.
56+
good middle ground. Additionally, the `baseFeeUpdateFraction` parameter was added to adjust the responsiveness of blob gas pricing per fork.
5457

5558
## Backwards Compatibility
5659

0 commit comments

Comments
 (0)