Skip to content

Update EIP-7910: Move to Final #11135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eth-bot merged 2 commits into from
Jan 21, 2026
Merged

Update EIP-7910: Move to Final #11135

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c0f0562
Move to Final EIP-7910
poojaranjan Jan 21, 2026
59f95ca
Update eip-7910.md
SamWilsn Jan 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 3 additions & 8 deletions EIPS/eip-7910.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,7 @@ title: eth_config JSON-RPC Method
description: A JSON-RPC method that describes the configuration of the current and next fork
author: Danno Ferrin (@shemnon)
discussions-to: https://ethereum-magicians.org/t/eth-config-json-rpc-method/23183
status: Last Call
last-call-deadline: 2025-10-28
status: Final
type: Standards Track
category: Interface
created: 2025-03-18
Expand Down Expand Up @@ -102,9 +101,9 @@ For Prague, the system contracts are (in order) `BEACON_ROOTS_ADDRESS`, `CONSOLI

Future forks MUST define the list of system contracts in their meta-EIPs.

### Blob Parameter Only Forks
### Blob Parameter Only (BPO) Forks

BPO forks specified in [EIP-7892](./eip-7892.md) should be interpreted as new forks, taking the parent fork as base (recursively, if the parent fork is also a BPO) and updating only the appropriate values in the `blobSchedule` object to produce the new fork configuration.
BPO forks should be interpreted as new forks, taking the parent fork as base (recursively, if the parent fork is also a BPO) and updating only the appropriate values in the `blobSchedule` object to produce the new fork configuration.

## Rationale

Expand Down Expand Up @@ -377,10 +376,6 @@ When no future forks are configured, the same RPC command would return:
}
```

## Reference Implementation

See Besu Pull \#8417

## Security Considerations

- **Exposure Risks**: Incorrect configurations could leak operational details. Operators SHOULD restrict `eth_config` to trusted interfaces (e.g., local access or authenticated endpoints).
Expand Down