EIP-8246 Removal of SELFDESTRUCT burn (Remove SELFDESTRUCT Burn)

No call decision · EVM & execution · EIP status Last Call · created 2026-05-01

Removes the last remaining case where ETH is burned when a contract created within the same transaction executes SELFDESTRUCT. Code, storage, and nonce are cleared, but the balance is preserved.

Why it is needed

Even with EIP-6780 in effect, one path still burns ETH: a contract created within the same transaction executes SELFDESTRUCT with itself as the beneficiary, or receives additional ETH in the same transaction after SELFDESTRUCT. Replaying the entire mainnet from genesis to roughly block 25 million showed only 2 cases of burning through this path since the Cancun upgrade. Even though it is almost never used, EVM implementations, specifications, and tests still have to keep handling this special case separately. This EIP removes all remaining burning, simplifying the semantics of SELFDESTRUCT and eliminating the last EVM mechanism by which ETH can leave total supply.

What changes

Today

After EIP-8246

Who is affected

In depth

The remaining burn path and its actual frequency of use

After EIP-6780, SELFDESTRUCT only deletes accounts for contracts created within the same transaction, and burning occurs in two cases: when the beneficiary is set to the contract itself, and when additional ETH is received via CALL or another SELFDESTRUCT in the same transaction after SELFDESTRUCT executes. Replaying the entire mainnet from genesis to roughly block 25M found 2 burns through this path since Cancun, and 0 cases of balance burning at the transaction finalization stage. Across the whole pre-Cancun history there were 54 cases of self-burning. Since the remaining burns are rarer than the burns EIP-6780 already eliminated, the complete removal proposed here affects even fewer transactions.

Specification: self-directed SELFDESTRUCT and transaction finalization

There are two changes. First, if a contract executes SELFDESTRUCT within the transaction in which it was created and the beneficiary is the executing account itself, that account's balance is preserved. Second, at transaction finalization, an account marked for self-destruction is no longer deleted but instead modified as follows: nonce is reset to 0, balance is left unchanged, code is cleared, and all storage is cleared. All other SELFDESTRUCT behavior is unchanged. As a result of this modification, if the balance is zero the account is an empty account and is removed from state under the EIP-161 rule.

Rationale: why the nonce is reset to 0

The design removes burning at its source rather than compensating for it elsewhere. The effect of clearing the state of a contract created in the same transaction is preserved, so even if the account remains in state, it becomes a non-executable, balance-only account. The nonce is reset to 0 so that an account with only a leftover balance does not block a later CREATE2 deployment to the same address. An alternative that preserved the nonce, code, and storage as well was considered; it would also eliminate burning, but it was rejected because it represents a larger semantic change that effectively disables SELFDESTRUCT entirely. This EIP removes only the burning behavior.

Backward compatibility and OP Stack's dependence on burn()

Because this changes consensus rules, a hard fork is required. Unlike mainnet, some L2s regularly use the burning function of SELFDESTRUCT. On the OP Stack, ETH withdrawn to L1 accumulates in the L2ToL1MessagePasser predeploy at address 0x4200000000000000000000000000000000000016, and a burn() function that anyone can call creates a contract whose constructor executes SELFDESTRUCT with itself as the beneficiary, eliminating this balance. This is the mechanism that keeps L2 ETH supply from inflating. Chains derived from this codebase inherit the same dependency unless they modify the predeploy, including chains that are not commonly classified as part of the Optimism family. Such chains will need a separate migration plan. Because this contract is deployed via CREATE, the leftover balance account that remains cannot be recreated with CREATE2.

Security Considerations: Dust Accounts and CREATE2 Redeployment

Use cases that relied on burning could leave behind dust accounts with locked balances. However, since the transaction pays the gas cost of creating a new account, this is not a free DoS vector, and only 2 such cases have been recorded on mainnet from Cancun through block 25M. An account with a preserved balance has its nonce, code, and storage all cleared, so it again becomes a valid CREATE2 target. Under EIP-684, an account with only a balance does not cause a creation collision. Since the (sender, salt, initcode) used for deployment is public data, if the sender is a factory anyone can use, anyone can redeploy to the same address and take the preserved balance.

Testing: Combinatorial Explosion and 17 Scenarios

SELFDESTRUCT is an opcode that has been modified multiple times in the past, so existing test coverage is already broad, and behavior that does not change is covered by updating the existing tests to match this EIP. Behavior that does change must be tested across combinations of factors such as call level (top-level transaction, internal call), call type (CALL, CREATE, CREATE2), code state (executing within initcode, executing within deployed code), success versus OOG failure, commit versus revert, and zero versus nonzero balance. 4 opcode-level scenarios, 12 transaction-finalization scenarios, and 1 multi-transaction scenario are defined. The testing burden is heavy due to multi-call and creation interactions, but a large portion of the existing EIP-6780 tests can be reused adapted to the new behavior.

Progress status

The source status is Last Call, with a last-call-deadline of 2026-11-04. Last Call is the final public review stage an EIP goes through before being finalized, and if content is revised during review the deadline may be reset, so details may still change before finalization. Neither the source nor the call records to date specify which hard fork this EIP will be included in. It requires EIP-161 and EIP-6780 as dependencies.

Original EIP · ← EIPs