eip-6780

ChainCatcher news, recently, according to the latest news from the TRON community, at the TRON #43 developer meeting, community developers conducted an in-depth discussion on the SELFDESTRUCT instruction upgrade proposal, proposing a plan compatible with Ethereum EIP-6780, aimed at adjusting the behavior and execution cost of the instruction to enhance network security and compatibility.According to the meeting content, the upgrade proposal mainly includes the following adjustments: the SELFDESTRUCT instruction will only completely remove the contract from the chain and transfer assets to the target address when called "in the same transaction that creates the contract"; otherwise, it will only transfer assets within the contract, and the contract itself will be retained. In addition, the energy consumption for executing SELFDESTRUCT will be adjusted from the current 0 to 5000, to prevent abuse of the instruction and potential denial-of-service attack risks.Community developers stated that this upgrade references Ethereum's Gas cost updates, aiming to achieve higher compatibility with Ethereum. If the proposal is approved, contracts will support multiple executions of SELFDESTRUCT, while a more reasonable execution cost will further enhance the security and stability of the TRON network, providing developers with a more reliable development environment.

ChainCatcher message, Ethereum co-founder Vitalik Buterin published an article titled "Follow-up Steps for Simplifying the Ethereum Protocol and Reducing Node Resource Load: Purge Explanation." Vitalik stated that EIP-6780 in the Dencun hard fork removed most of the functionality of the SELFDESTRUCT opcode, simplifying the protocol by eliminating complexity and adding new security guarantees. Therefore, Vitalik marked it as an important part of the "Purge," regarding other "Purge" actions that are currently taking place.Additionally, regarding other areas that may need "Purge," Vitalik listed precompiles, history (EIP-4444), LOG reforms, and migration to SSZ. Concerning precompiles, Vitalik pointed out that the demand for some precompiles is far lower than expected, and these precompile functions are a significant source of consensus errors and a major pain point for new EVM implementations.