-
Notifications
You must be signed in to change notification settings - Fork 211
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
TIP-652: Announce EIP-6049 Deprecate SELFDESTRUCT #652
Comments
THPvaUhoh2Qn2y9THCZML3H815hhFhn5YC |
TFrPnTJ4smGnyjF5eTWP6GSKGHdjThELiW |
1 similar comment
TFrPnTJ4smGnyjF5eTWP6GSKGHdjThELiW |
Would it be convenient to introduce this issue at the next tronprotocol/pm#99? |
Yeah, of course. |
|
Summary
The
SELFDESTRUCT
opcode has been deprecated after the Ethereum Shanghai upgrade and its behavior has been modified after the Ethereum Cancun upgrade. For compatibility, EIP-6049: Deprecate SELFDESTRUCT is required to be announced in the TRON community firstly.The following compatibility issues require community attention.
Contracts that depended on re-deploying contracts at the same address using
CREATE2
(after aSELFDESTRUCT
) may not function properly.It may be no longer possible to burn TRX by calling
SELFDESTRUCT
targeting the executing contract as the beneficiary.Original content from EIP-6049:
Abstract
This EIP deprecates the
SELFDESTRUCT
opcode and warns against its use. A breaking change to this functionality is likely to come in the future.Motivation
Discussions about how to change
SELFDESTRUCT
are ongoing. But there is a strong consensus that something will change.Specification
Documentation of the
SELFDESTRUCT
opcode is updated to warn against its use and to note that a breaking change may be forthcoming.Rationale
As time goes on, the cost of doing something increases, because any change to
SELFDESTRUCT
will be a breaking change.The Ethereum Blog and other official sources have not provided any warning to developers about a potential forthcoming change.
Backwards Compatibility
This EIP updates non-normative text in the Yellow Paper. No changes to clients is applicable.
Security Considerations
None.
The text was updated successfully, but these errors were encountered: