Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update EIP-6780: Move to Final #8336

Merged
merged 2 commits into from
Mar 29, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions EIPS/eip-6780.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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 `eip6780_selfdestruct` folder of the `ethereum/execution-spec-tests`
lightclient marked this conversation as resolved.
Show resolved Hide resolved

## Security Considerations

The following applications of `SELFDESTRUCT` will be broken and applications that use it in this way are not safe anymore:
Expand Down
Loading