Committee proposal 89 is a voting request for modifying the №76 chain parameter on TRON network, activating the PUSH0 instruction in TRON virtual machine (TVM), please refer to here for the origin discussion. …

In the last three months, the transaction volume on the TRON network has reached over 11 million per day, performing its robust capabilities and offering developers with stable and highly efficient service. However, it is found that there were a large number of low-value in the network. In addition, some…

Committee proposal 88 is a voting request for setting the №77 and №78 chain parameters on the TRON network, which aims to enable the usage optimization of Stake 2.0. It allows users to cancel the unstaking that has been initiated but not yet completed, and allows users to specify the…

Committee proposal 87 is a voting request for modifying the №61 chain parameter on TRON network, reducing the daily free bandwidth of the account from 1500 to 600, please refer to here for the origin discussion. …

The TRON developer community has released the GreatVoyage-v4.7.2(Periander) version, this is a mandatory upgrade. Please complete your upgrade to the new version before 23:59, July 11th, 2023 (SGT). The Periander version introduces several important optimizations and updates, adding two governance proposals to optimize Stake 2.0, greatly improving the flexibility of…

TIP-541 and TIP-542 are features introduced in the Periander version. By adding 2 proposals to expand Stake 2.0, they further improve the flexibility of the TRON staking mechanism. TIP-541 In the versions previous to Periander, after initiating an unstaking transaction through the HTTP API in Stake 2.0, the user needs to…

GreatVoyage-v4.7.2(Periander) is estimated to be released at the end of June. You are welcome to check new improvements in advance here. Changes planned to be included in Periander: 1.TIP-541: Support canceling unstaking in Stake 2.0 2.TIP-542: Resource delegating supports customizable lock period 3.TIP-543: Implement EIP-3855 PUSH0 instruction 4.TIP-544: Add data…

Committee proposal 85 is a voting request for modifying the №71 parameter, optimizing the return value of the chainid opcode in TVM, please refer to here for the origin discussion. …

At present, the return value of the chainid instruction in the smart contract on TRON is the hash of the genesis block. After the optimization is enabled, the return value of the chainid instruction will be the last four bytes of the genesis block hash, please refer to TIP-474. …