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

TIP-652: Announce EIP-6049 Deprecate SELFDESTRUCT #652

Open
yanghang8612 opened this issue Apr 10, 2024 · 6 comments
Open

TIP-652: Announce EIP-6049 Deprecate SELFDESTRUCT #652

yanghang8612 opened this issue Apr 10, 2024 · 6 comments
Labels
cancun compatible Ethereum Cancun Upgrade compatible plans

Comments

@yanghang8612
Copy link
Contributor

yanghang8612 commented Apr 10, 2024

tip: 652
title: Announce EIP-6049 Deprecate SELFDESTRUCT
author: yanghang8612@163.com
status: Draft
type: Meta
category: VM
created: 2024-04-10

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 a SELFDESTRUCT) 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.

@yanghang8612 yanghang8612 added discussions-to cancun compatible Ethereum Cancun Upgrade compatible plans labels Apr 10, 2024
@yanghang8612 yanghang8612 changed the title TIP-TBD: Announce EIP-6049 Deprecate SELFDESTRUCT TIP-652: Announce EIP-6049 Deprecate SELFDESTRUCT Apr 10, 2024
@Saraeutsza
Copy link

THPvaUhoh2Qn2y9THCZML3H815hhFhn5YC

@thuthu24
Copy link

TFrPnTJ4smGnyjF5eTWP6GSKGHdjThELiW

1 similar comment
@thuthu24
Copy link

TFrPnTJ4smGnyjF5eTWP6GSKGHdjThELiW

@tomatoishealthy
Copy link
Contributor

Would it be convenient to introduce this issue at the next tronprotocol/pm#99?

@yanghang8612
Copy link
Contributor Author

Would it be convenient to introduce this issue at the next tronprotocol/pm#99?

Yeah, of course.

@NaNOteh
Copy link

NaNOteh commented Nov 16, 2024

tip: 652
title: Announce EIP-6049 Deprecate SELFDESTRUCT
author: yanghang8612@163.com
status: Draft
type: Meta
category: VM
created: 2024-04-10

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 a SELFDESTRUCT) 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cancun compatible Ethereum Cancun Upgrade compatible plans
Projects
None yet
Development

No branches or pull requests

6 participants