Update EIP-7708: Add ETH burn logs and improve spec consistency#11311
Merged
Conversation
github-actions
Bot
added
c-update
Collaborator
|
✅ All reviewers have approved. |
eth-bot
changed the title
p21117118-lab
approved these changes
Feb 13, 2026
etan-status
approved these changes
Feb 13, 2026
Contributor
etan-status
left a comment
etan-status
left a comment
There was a problem hiding this comment.
Thanks, this also corrects the order, when a TX deploys a contract and selfdestructs it, and then that TX is packed into a block that selects that contract as coinbase. The Prio fee should be burned in that case, and only prio fees of subsequent transactions would be effectively credited.
eth-bot
approved these changes
Feb 13, 2026
Collaborator
eth-bot
left a comment
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
Contributor
|
Also, |
This was referenced Feb 14, 2026
jwasinger
pushed a commit
to ethereum/go-ethereum
that referenced
this pull request
Feb 16, 2026
ethereum/EIPs#11311 renamed the "Selfdestruct" log topic to "Burn" in the EIP-7708 specification. The rationale is that "Burn" better describes what happens (ETH is destroyed) rather than how it happens (via the SELFDESTRUCT opcode). This creates a more consistent API, which reflects the outcome, not the mechanism. Co-authored-by: raxhvl <raxhvl@users.noreply.github.com>
yperbasis
pushed a commit
to erigontech/erigon
that referenced
this pull request
Feb 16, 2026
This PR renames the log topic from `Selfdestruct` to `Burn` as defined in the `EIP-7708` specification. The new name Burn clearly describes what happens - ETH is permanently removed - instead of referring to the internal opcode used. This makes the API more clear and focused on the result. Refrence: ethereum/EIPs#11311
edg-l
added a commit
to lambdaclass/ethrex
that referenced
this pull request
Feb 17, 2026
Per ethereum/EIPs#11311, the EIP-7708 log event is renamed from Selfdestruct(address,uint256) to Burn(address,uint256) with a new topic hash.
edg-l
added a commit
to lambdaclass/ethrex
that referenced
this pull request
Feb 17, 2026
Per ethereum/EIPs#11311, the EIP-7708 log event is renamed from Selfdestruct(address,uint256) to Burn(address,uint256) with a new topic hash.
edg-l
added a commit
to lambdaclass/ethrex
that referenced
this pull request
Feb 19, 2026
Per ethereum/EIPs#11311, the EIP-7708 log event is renamed from Selfdestruct(address,uint256) to Burn(address,uint256) with a new topic hash.
edg-l
added a commit
to lambdaclass/ethrex
that referenced
this pull request
Feb 26, 2026
Per ethereum/EIPs#11311, the EIP-7708 log event is renamed from Selfdestruct(address,uint256) to Burn(address,uint256) with a new topic hash.
edg-l
added a commit
to lambdaclass/ethrex
that referenced
this pull request
Mar 1, 2026
Per ethereum/EIPs#11311, the EIP-7708 log event is renamed from Selfdestruct(address,uint256) to Burn(address,uint256) with a new topic hash.
edg-l
added a commit
to lambdaclass/ethrex
that referenced
this pull request
Mar 3, 2026
Per ethereum/EIPs#11311, the EIP-7708 log event is renamed from Selfdestruct(address,uint256) to Burn(address,uint256) with a new topic hash.
yperbasis
pushed a commit
to erigontech/erigon
that referenced
this pull request
Mar 6, 2026
This PR renames the log topic from Selfdestruct to Burn as defined in the EIP-7708 specification. The new name Burn clearly describes what happens - ETH is permanently removed - instead of referring to the internal opcode used. This makes the API more clear and focused on the result. Refrence: ethereum/EIPs#11311
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
ETH can be minted (added to circulation), transferred (moved between accounts), and burned (removed from circulation). Changes in circulation or ownership should be logged. The focus should be on what changed, not how it changed.
This is done correctly for transfers, which emit a
Transferlog. It does not specify how the transfer happened (CALLvsSELFDESTRUCT).When ETH is burned, it should emit a
Burn(address,uint256)log ("the what"), not aSELFDESTRUCT(address,uint256)log ("the how").We are currently tracking a subset of changes. A consistent API allows for easier extensions. Logging ETH burns in other ways besides
SELFDESTRUCT, for example.What changed
This PR: