Does the TRON Network currently have plans to follow up on the Ethereum EL Cancun Upgrade?

[lily309]

We see that the Ethereum EL Cancun Upgrade has been activated on the mainnet and this upgrade contains several improvements. As an EVM-compatible blockchain, does the TRON Network have any plans to consider following suit in the near future?

Below is a detailed list of the upgrade features and the instructions that have been added or modified, does TRON need to support all or just some of these features?

• EIP-1153: Transient storage opcodes
  • TLOAD (0x5c) new!
  • TSTORE (0x5d) new!
• EIP-4788: Beacon block root in the EVM
  • Is there any reference to the concept of deploying system contracts in hard fork upgrades?
• EIP-4844: Shard Blob Transactions
  • BLOBHASH (0x49) new!
• EIP-5656: MCOPY - Memory copying instruction
  • MCOPY (0x5e) new!
• EIP-6780: SELFDESTRUCT only in same transaction
  • SELFDESTRUCT (0xff) changed!
• EIP-7516: BLOBBASEFEE opcode
  • BLOBBASEFEE (0x4a) new!

We also see that deploying contracts on TRON requires the use of the TRON-specific Solidity compiler. Are there any plans to upgrade the support for the Solidity compiler?

Looking forward to your answers. Thank you!

[ferdinand026]

Due to TRON’s unique mechanism, for example the stake system, it needs special TVM instructions, so deploying such smart contract which related with TRON’s unique features on TRON requires to use the TRON solidiy compiler, but not Etherum solidity sompiler. But for smart cotract which have nothing related with TRON’s unique features, we can use either of them.

[lily309]

@ferdinand026

Thank you for your answer.

First of all, are there any compatible upgrades planned?

Second, the Ethereum Solidity compiler has been updated to v0.8.25 and the default EVM version is set to cancun, which means that the bytecode of some contracts compiled with the default configuration of the Ethereum Solidity compiler can no longer run on TRON, as the operations for memory copies in it will use the MCOPY instruction in place of the former MLOAD/MSTORE.

Once again, thank you sincerely for your answer.

[yanghang8612]

@lily309

The TRON community is already moving forward with compatibility plans. Details will be released to the TIPs repository in the near future, so stay tuned.

If you have any questions, please move to the TIPs repository to discuss. Thank you.

[tomatoishealthy]

The TRON community is already moving forward with compatibility plans. Details will be released to the TIPs repository in the near future, so stay tuned.

As far as I know, EIP-4844 is to optimize the gas fee for Rollups, TRON currently does not have too many rollup projects, nor does it have a high gas fee, so maybe this EIP is not a high priority.

But considering the compatibility, does TVM need to be compatible with EIP-7516, e.g. return 0. Same question for EIP-4788.

I understand that the remaining three EIPs will definitely be compatible.

[yanghang8612]

@tomatoishealthy

Yes, for the instructions in EIP-4844 as well as EIP-7516, we tend to implement them simply, returning only 0 or the default value. For EIP-4788, we tend not to implement them since there are no new instructions or pre-compiled contracts.

[Federico2014]

@tomatoishealthy

Yes, for the instructions in EIP-4844 as well as EIP-7516, we tend to implement them simply, returning only 0 or the default value. For EIP-4788, we tend not to implement them since there are no new instructions or pre-compiled contracts.

There have already deployed TRON zkEVM testnet, we may need to reconsider whether TRON should support EIP-4844 or not.

[tomatoishealthy]

There have already deployed TRON zkEVM testnet, we may need to reconsider whether TRON should support EIP-4844 or not.

But apart from this project, there are currently no more rollups and gas fee issues. Maybe we can discuss this in the AlldevsMeetings