diff --git a/EIPS/eip-7691.md b/EIPS/eip-7691.md
index e843cca625ef38..51ebf0e9dc99ff 100644
--- a/EIPS/eip-7691.md
+++ b/EIPS/eip-7691.md
@@ -4,7 +4,8 @@ title: Blob throughput increase
 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), Ansgar Dietrichs (@adietrichs)
 discussions-to: https://ethereum-magicians.org/t/eip-7691-blob-throughput-increase/19694
-status: Review
+status: Last Call
+last-call-deadline: 2025-04-01
 type: Standards Track
 category: Core
 created: 2024-04-17
@@ -20,8 +21,6 @@ Ethereum, with its rollup centric roadmap, scales by relying on L2. Since the De
 
 As we now have the Dencun upgrade live, we are able to use monitoring tools to check the network health. Initial monitoring indicates that we have a stable network with the current gas target and the re-org rate is trending downwards. Additionally, analysis on messages in gossipsub indicate that the inclusion of `IDONTWANT` messages could bring us a significant bandwidth savings. This allows us to consider starting a series of big block and blob tests to determine the theoretical headroom we currently have. The EIP specifies a proposed new blob gas target and limit based on the series of tests.
 
-Additional EIPs such as [EIP-7623](./eip-7623.md) proposes a calldata cost increase which would significantly lower the worst case base block size, thus creating more headroom for a potential blob throughput increase.
-
 This EIP aims to increase the throughput short term to provide some scaling until future solutions are deployed. In order to alleviate valid concerns about solo-stakers, approaches such as the inclusion of a flag indicating the max blobs per block for locally built blocks could be considered.
 
 ## Specification