Move EIP-8246 notice to top

diff --git a/README.md b/README.md
index e144bcfebb691ee201f22b6f66489d8d981d9ee1..ca70a397a072c817d857ce05a431c90f24a6538f 100644 (file)
--- a/README.md
+++ b/README.md
@@ -1,5 +1,8 @@
 # minimal-eth-burner
 
+> [!IMPORTANT]
+> [EIP-8246](https://eips.ethereum.org/EIPS/eip-8246) (scheduled for inclusion in [Glamsterdam](https://eips.ethereum.org/EIPS/eip-7773), targeting [November 2026](https://forkcast.org/schedule/)) will disable this method of burning ETH.
+
 On Ethereum, it's common to "burn" (destroy) ETH by sending it to a "burner address" like [`0x000000000000000000000000000000000000dead`](https://etherscan.io/address/0x000000000000000000000000000000000000dead).
 
 However, ETH sent to burner addresses is theoretically recoverable if private keys associated with the burner addresses are ever discovered. The only way to actually destroy ETH is by either:
@@ -66,10 +69,6 @@ await provider.request({
 
 Since the `deployer.eas` bytecode creates a new smart contract and then immediately calls it in the same transaction, its behavior is not changed by EIP-6780.
 
-## EIP-8246
-
-[EIP-8246](https://eips.ethereum.org/EIPS/eip-8246) (scheduled for inclusion in [Glamsterdam](https://eips.ethereum.org/EIPS/eip-7773), targeting [November 2026](https://forkcast.org/schedule/)) will disable this method of burning ETH.
-
 ## Assembly
 
 Use [`geas`](https://github.com/fjl/geas) to assemble the files: