Tron Network :: Prepares For Periander Upgrade

The TRON developer community is pleased to announce the release of an important update GreatVoyage-v4.7.2 (Periander) before 23:59, July 11th, 2023 (SGT).

The Periander release introduces several important optimizations and updates, adds two governance guidelines to optimize Stake 2.0, and greatly increases the flexibility of the TRON staking mechanism.

An instruction that not only ensures TRON and Ethereum compatibility at the virtual machine level, but also reduces the cost of using TRON smart contracts. A more user-friendly smart contract interface that improves the convenience of developing smart contracts.

TRON's P2P network module has been completely updated to support functions such as IPV6, node discovery via DNS, message compression, etc., and the performance of TRON's network infrastructure has been greatly improved.

In this review, we will look at the updates to the Stake 2.0 mechanism.

Support canceling unstaking

In the pre-Periander version, after initiating a no-stake transaction via the Stake 2.0 HTTP API, users had to wait 14 days before withdrawing the corresponding funds and could not cancel the non-stake transaction.

The release of Periander streamlines the Stake 2.0 mechanism by allowing users to cancel installations that have been initiated but not yet completed.

When an installation is canceled, installations that are still in the pending period are re-bid, and the resources from the repricing remain as before.

Developments that are outside the 14-day waiting period cannot be canceled, and part of the unallocated funds is automatically debited from the owner's account.

This feature is controlled by TRON network parameter 77 and must be enabled by administrative vote. Once this feature is enabled, the node will support new types of transactions, and users will be able to cancel indeterminate transactions using the wallet/cancelallunfreezev2 API.

Resource delegating supports customizable lock period

In Periander and earlier versions, users can choose whether or not to block resources when they log in. If they choose to lock, the resource whose recipient address they have delegated cannot be canceled for three days, making it more profitable for users to participate in the resource rental market.

The Periander version further optimizes the block time for resource delegation by changing it from the current fixed value of three days to a time interval that can be adjusted depending on the user's needs.

This function is controlled by parameter 78 of the TRON network. Enabling this feature requires an administrative vote. If this clause is enabled, you must provide a time parameter that specifies the maximum lock_period that can be configured. When the new lock_period parameter is enabled, it will be added to the wallet/delegation resource API.

The default value of lock_period is 86400, which is three days. This means that if lock is true and lock_period is not specified or is set to 0, lock_period will default to 86400 to ensure compliance before and after TIP-542 goes into effect.

In addition, the lock_period value cannot be less than the remaining lock_period value of a resource of this type that was previously delegated to the same recipient address, and this value overrides the remaining lock_period value of the previous delegation.

For example, user A delegates 100 shares of energy to user B, and lock_period is set to 57600 (2 days), so that after one day, the remaining lock_period is 28800. If A then decides to transfer energy back to B and lock it, the lock period must be set to at least at 28800 (1 day). Otherwise, an exception error will be thrown when creating the delegation transaction.

---

To earn TRX I use the service Feee.io is a TRON energy trading platform, you want to receive income from 50% APY. Join our friendly team!