⚙️ Understanding TIP-6780 on TRON — Simple Breakdown
TIP-6780 updates the SELFDESTRUCT opcode to match Ethereum’s EIP-6780, improving security, predictability, and EVM alignment.
1️⃣ What Changes
▫ Updates SELFDESTRUCT behavior
▫ Follows TIP-652, which discouraged its use
▫ Strengthens TRON–Ethereum compatibility
2️⃣ New SELFDESTRUCT Rules
Scenario A — Normal transaction:
▫ Contract is not deleted
▫ Code + storage stay
▫ Execution stops
▫ Assets transfer normally
▫ No burn if sent to itself
Scenario B — During contract creation:
▫ Contract is deleted
▫ Code + storage removed
▫ Assets transferred
▫ Balance burned if sent to itself
Energy: Now costs 5,000 Energy.
3️⃣ Developer Impact
▫ DELETE-based patterns no longer work
▫ CREATE2 + SELFDESTRUCT upgrades invalid
▫ Not suitable for wiping data
▫ TRX burn only works in same-tx create-and-destroy
4️⃣ Ecosystem Benefits
▫ Stronger EVM compatibility
▫ Safer, more predictable contracts
▫ Better long-term maintenance patterns
5️⃣ On-Chain Reality
▫ Very few contracts use SELFDESTRUCT
▫ Most follow create-and-destroy pattern (still supported)
➡ No disruption expected
6️⃣ Governance
TIP-6780 activates after Java-tron v4.8.1 release + community vote.
🔗 Follow governance progress: tronscan.org
TIP-6780 strengthens TRON’s EVM alignment, boosts contract safety, and encourages modern, reliable smart-contract design.
@justinsuntron @TRON DAO #Developers #EVMCompatibility #TRONEcoStar