Tron Hard-Fork Update: TRX Odyssey’s TIP12, TIP16, and TIP17 Deployed
As many of our readers are already aware of, the highly anticipated Tron hard fork has finally gone live — with the latest network update providing the platform with a whole host of new features, operational enhancements, and fixes.
Odyssey-v3.5 have been released! The TIP12,TIP16 and TIP17 have been implemented in 3.5. #TRON #TRX $TRX #BitTorrent #BTT $BTT
Check 3.5 release herehttps://t.co/WhBMIGewbP
Check the TIP12,TIP16,TIP17 herehttps://t.co/HSyCr1hvWo
— Justin Sun (@justinsuntron) February 28, 2019
In this regard, Tron CEO Justin Sun recently took to Twitter to talk about the release of the brand new Odyssey v3.5 update. Not only that, but he also spoke about the Tron Improvement Protocol [TIP] — including TIP12, TIP16, and TIP17 — that too went live recently.
(i) TIP 12:
This particular protocol has been devised using Tron’s event subscribe model that is used to keep track of blockchain/transaction events, network contract logs etc. Not only that, but TIP 12 is also designed to help enable developers to
“set up filters to subscribe to specific events in order to export them for further development”.
(ii) TIP 16:
This protocol addresses some of the issues that have been prevalent with Tron’s multi-signature account interfaces. As per a recent blog release, Tron’s multi-sig module requires an authority seal for each individual transaction so as to reach “customized weight dist.” before final execution.
In this regard, the three different types of permission schemes that are needed for carrying out contract executions (as well as block generation activities) include:
(iii) TIP 17:
The TIP17 protocol primarily deals with the standard interface of the Tron ecosystem’s adaptive
“energy limit model”.
To elaborate on the matter, we can see that the Tron network’s current energy consumption for the creation and operation of smart contracts can be calculated using the following mathematical formula:
Consumed Energy = TRX/Total TRX* Energy Limit of the whole network for obtaining Energy frozen.
In this regard, a recent post by the TRON dev team reads:
“For example, if the total amount of TRX frozen for Energy in the current network is 1_000_000_000 TRX, and an account with 1_000 TRX frozen accounts for one millionth of the total amount frozen, then the Energy limit for that account is 32400 Energy.”