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

BEP-312: Announce EIP-6049 Deprecate SELFDESTRUCT #312

Merged
merged 1 commit into from
Nov 17, 2023

Conversation

buddh0
Copy link
Contributor

@buddh0 buddh0 commented Oct 30, 2023

  BEP: 312
  Title: Announce EIP-6049: Deprecate SELFDESTRUCT
  Status: Draft
  Type: Standards
  Created: 2023-10-30

BEP-312: Announce EIP-6049 Deprecate SELFDESTRUCT

1. Summary

As part of Shanghai upgrade, EIP-6049: Deprecate SELFDESTRUCT is required to be announced in the BSC community.

2. 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.

3. Motivation

Discussions about how to change SELFDESTRUCT are ongoing. But there is a strong consensus that something will change.

4. Specification

Documentation of the SELFDESTRUCT opcode is updated to warn against its use and to note that a breaking change may be forthcoming.

5. 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.

6. Backwards Compatibility

This EIP updates non-normative text in the Yellow Paper. No changes to clients is applicable.

7. Security Considerations

None.

8. License

The content is licensed under CC0.

9. Reference

William Entriken (@fulldecent), "EIP-6049: Deprecate SELFDESTRUCT," Ethereum Improvement Proposals, no. 6049, November 2022. [Online serial]. Available: https://eips.ethereum.org/EIPS/eip-6049.

@fulldecent
Copy link

Thank you for sharing. I am not an expert on BSC. Hopefully appropriate references can be added to the BEP to mention any official statements the BSC project has made or any analysis that has been made of impact on deployed BSC contracts.

It is possible that because BSC was deployed after ETH a more aggressive implementation of this BEP can be done than has been done on ETH with EIP-6049.

Copy link
Contributor

@brilliant-lx brilliant-lx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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.

3 participants