Skip to content

core, core/vm: Rename selfdestruct log to burn#33851

Merged
jwasinger merged 1 commit into
ethereum:bal-devnet-2from
raxhvl:eips/amsterdam/eip-7708-burn
Feb 16, 2026
Merged

core, core/vm: Rename selfdestruct log to burn#33851
jwasinger merged 1 commit into
ethereum:bal-devnet-2from
raxhvl:eips/amsterdam/eip-7708-burn

Conversation

@raxhvl
Copy link
Copy Markdown
Member

@raxhvl raxhvl commented Feb 15, 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.

@tellabg
Copy link
Copy Markdown
Contributor

tellabg commented Feb 15, 2026

@raxhvl read the contributor guidelines

@jwasinger jwasinger merged commit 8909a48 into ethereum:bal-devnet-2 Feb 16, 2026
1 of 3 checks passed
@raxhvl raxhvl changed the title ✨ feat(EIP-7708): Rename selfdestruct log to burn core, core/vm: Rename selfdestruct log to burn Feb 16, 2026
@lvhxar
Copy link
Copy Markdown

lvhxar commented Feb 16, 2026

@tellabg I return enlightened after studying the sacred text

@jwasinger
Copy link
Copy Markdown
Contributor

I merged this but it was a mistake: this is a consensus-breaking change that can only go in next devnet.

@raxhvl
Copy link
Copy Markdown
Member Author

raxhvl commented Feb 16, 2026

My bad. What is the correct target branch for such a change? devnet-3?

FYI: Nethermind merged it into devnet-2 too, erigon merged this into main.

@jwasinger
Copy link
Copy Markdown
Contributor

There's not a branch for devnet 3 yet.

@jwasinger
Copy link
Copy Markdown
Contributor

FYI: Nethermind merged it into devnet-2 too, erigon merged this into main.

Well this change wasn't spec'd for the current devnet so those clients shouldn't have merged/activated it.

@barnabasbusa
Copy link
Copy Markdown
Member

I think nethermind also made a mistake by merging it in. I'd create a new branch bal-devnet-3, and start merging prs like these in there.

@jwasinger jwasinger mentioned this pull request Mar 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants