From a7da910fb774f6ac44b54d0a98cc0309a10de5fb Mon Sep 17 00:00:00 2001 From: Ardis Lu Date: Sat, 12 Sep 2026 22:29:25 -0700 Subject: [PATCH] Move EIP-8246 notice to top --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index e144bcf..ca70a39 100644 --- 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: -- 2.47.3