diff --git a/EIPS/eip-7910.md b/EIPS/eip-7910.md
index 0aacdbe4a9f00f..bda67d19cd01d5 100644
--- a/EIPS/eip-7910.md
+++ b/EIPS/eip-7910.md
@@ -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
@@ -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
 
@@ -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).