diff --git a/EIPS/eip-6780.md b/EIPS/eip-6780.md
index 3749184795030..1b6a0e94cc47e 100644
--- a/EIPS/eip-6780.md
+++ b/EIPS/eip-6780.md
@@ -4,8 +4,7 @@ title: SELFDESTRUCT only in same transaction
 description: SELFDESTRUCT will recover all funds to the target but not delete the account, except when called in the same transaction as creation
 author: Guillaume Ballet (@gballet), Vitalik Buterin (@vbuterin), Dankrad Feist (@dankrad)
 discussions-to: https://ethereum-magicians.org/t/deactivate-selfdestruct-except-where-it-occurs-in-the-same-transaction-in-which-a-contract-was-created/13539
-status: Last Call
-last-call-deadline: 2024-02-15
+status: Final
 type: Standards Track
 category: Core
 created: 2023-03-25
@@ -64,6 +63,10 @@ Contracts that depended on re-deploying contracts at the same address using `CRE
 
 Previously it was possible to burn ether by calling `SELFDESTRUCT` targeting the executing contract as the beneficiary.  If the contract existed prior to the transaction the ether will not be burned.  If the contract was newly created in the transaction the ether will be burned, as before.
 
+## Test Cases 
+
+Test cases for this EIP can be found in the Execution Spec Tests suite [`eip6780_selfdestruct`](https://github.com/ethereum/execution-spec-tests/tree/1983444bbe1a471886ef7c0e82253ffe2a4053e1/tests/cancun/eip6780_selfdestruct).
+
 ## Security Considerations
 
 The following applications of `SELFDESTRUCT` will be broken and applications that use it in this way are not safe anymore: