Latest developments on TIP-6780: TRON Developer Community releases notes on changes to the SELFDESTRUCT instruction.
TL;DR
TRON's TIP-6780 restricts SELFDESTRUCT to same-transaction creation and increases energy cost to 5000, aligning with Ethereum EIP-6780. The change, in java-tron v4.8.1, will activate after network upgrade and governance voting, with minimal impact on existing contracts.
Tags
On November 19th, the TRON developer community released a new explanation titled "TIP-6780: Change to the SELFDESTRUCT Opcode" on Medium, and discussed the impact of the instruction change in detail at a recent developer meeting. According to the plan, this change will be incorporated into the upcoming java-tron v4.8.1 version, but will not take effect immediately upon release. The official implementation time will be determined through on-chain governance voting after the entire network upgrade is completed.
According to the description, the core adjustment in TIP-6780 is to restrict the use cases of SELFDESTRUCT, allowing it to truly delete account data (such as code, storage, and the account itself) only when invoked within the same transaction where the contract was created. It also raises the barrier to entry by adjusting the fixed energy cost from 0 to 5000 to reduce the risk of abuse. This change will align TRON's behavior with Ethereum EIP-6780, thereby further enhancing EVM compatibility.
In addition, the developer community conducted a statistical analysis of contracts containing the SELFDESTRUCT instruction on the current TRON network, showing that such contracts account for a very small percentage and even fewer actually hold assets. Since 2025, most internal transactions related to SELFDESTRUCT have been in a "create-and-destroy" usage pattern, which will still work normally after the upgrade. Therefore, the actual impact on existing contracts and user assets is expected to be limited.