Ethereum developer William Entriken opened the proposal that became EIP-6049 on November 27, 2022, seeking to formally deprecate the Ethereum Virtual Machine’s `SELFDESTRUCT` opcode. The proposal did not change Ethereum’s consensus rules or require client software to behave differently. Its immediate purpose was narrower but consequential: warn developers that the opcode’s behavior was likely to change in a future network upgrade.
The associated pull request was recorded as opened at 22:34 UTC on November 27. Entriken’s discussion post followed at 22:37 UTC. The surviving EIP record assigns the proposal a creation date of November 27, 2022.
What the proposal actually did
EIP-6049 called for Ethereum documentation to discourage use of `SELFDESTRUCT` and disclose the possibility of a breaking change. Its specification was limited to non-normative documentation in the Ethereum Yellow Paper. The proposal expressly said that no client modification applied.
That distinction is essential to the event-day record. Ethereum did not disable the opcode on November 27, 2022. Existing contracts did not acquire new execution rules, and developers were not given a settled replacement design. The action was a proposed warning rather than an activated hard fork.
The warning nevertheless addressed a real protocol-design conflict. `SELFDESTRUCT` had semantics involving an account’s balance, code and storage. A separate proposal created on November 25, EIP-6046, explained that deleting an account’s storage was difficult to reconcile with contemplated Verkle-tree state organization, where an account’s properties and storage could be distributed across separate keys. EIP-6046 proposed replacing the instruction with a different deactivation model, illustrating that the design discussion was active but unresolved.
Why a documentation change mattered
The importance of EIP-6049 was prospective. Smart contracts can be difficult or impossible to revise after deployment, so warning developers only when new consensus rules activate can leave applications dependent on behavior the protocol intends to remove or restrict. Entriken’s contemporaneous explanation characterized the proposal as notice of a significant forthcoming change.
For application developers, the prudent inference on November 27 was therefore limited: new systems should avoid assuming that `SELFDESTRUCT` would retain its existing semantics indefinitely. It was not yet possible to state which replacement proposal would prevail, when a change would activate or how every deployed contract pattern would be treated.
For Ethereum governance, the proposal also separated two decisions that are often conflated. A community can signal that a feature is deprecated before agreeing on the exact consensus change that will replace it. That sequencing gives tooling authors, auditors and contract developers time to identify dependencies while protocol contributors continue debating implementation.
No defensible market-impact claim follows from the surviving records. EIP-6049 contained no price, trading-volume, adoption or usage measurement, and the discussion did not establish that the proposal caused a movement in ether. This reconstruction therefore makes no market calculation for November 27, 2022.
What was knowable on November 27
The primary records establish that the proposal and discussion existed on the assigned date, that their stated objective was formal deprecation, and that the proposed warning required no client change. They do not establish event-day adoption by Ethereum client teams or final inclusion in a scheduled upgrade.
That uncertainty should remain part of the historical framing. Later acceptance cannot be treated as something developers already knew when the pull request opened.
Later context
On March 28, 2023, the Ethereum Foundation’s Protocol Support Team listed EIP-6049 among the execution-layer items in the scheduled Shapella upgrade. The announcement emphasized that it was only a deprecation warning and that `SELFDESTRUCT` behavior would remain unchanged in Shanghai. That later primary record confirms the warning’s eventual protocol status, but it does not convert the November 27 proposal into an event-day network change.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.