TronGrid 1.0 was upgraded to v1.0 on July 2, 2020. In this new version, we added some features including better stability and performance improvement. Following are some detailed launch notes.
TronGrid’s objective is for users to acquire data from the TRON blockchain in a faster, simpler, and safer manner, and that’s why we continue to improve the user experience.
TronStack is a service we provide for users. It is a distributed version of TronGrid, and users will need to deploy it locally. TronStack is implemented with java-tron’s new event subscription model. On top of the basic inquiry, users can also trigger subscribe blocks, events, contract logs, and contract events. A key advantage for TronStack is that it can be deployed locally, offering faster access and freeing users from concerns of not being able to visit TronGrid when it’s overloaded or due to external network issues. Furthermore, users can customize features according to their needs, and access information they wish to know through event subscription. It is also much more convenient to identify problems locally if they do occur. For more information, please refer to https://github.com/tronprotocol/tron-eventquery
With the previous interface, users do not receive certain information as the returned results are incomplete, and sometimes users are forced to call other interfaces to get the information needed. This is neither fast nor convenient enough for our users. Therefore, after investigating what information is usually needed for the transaction inquiry, we now have all the information returned through the transaction interface. We’ve also added the resource consumption field and others in the https://api.trongrid.io/v1/accounts/address/transactions interface.
The field of withdraw_amount is added for WithdrawBalanceContract type of transactions while the field of unfreeze_amount is added to UnfreezeBalanceContract type of transactions. As there is too little useful information returned from the https://api.trongrid.io/v1/accounts/address/transactions/trc20 interface, we’ve also added other information on top of the aforementioned resource consumption fields. They are
By adding these frequently-used fields, we empower users to access as much transaction information as possible through one call. On the account of compatibility, a request parameter, get_detail=True, is added to access these detailed information while keeping the pre-existing information returned. This would make it easier for users to factor TronGrid-based applications.
One of the requested features is to query the time of casting the latest vote from an account. To this end, Tron-Grid developers decided to add a parameter vote_tx=true (false by default) in the transaction interface so users can filter transactions to look at voting-related ones and use the parameter to locate only the latest vote. For example:https://api.trongrid.io/v1/accounts/address/transactions?vote_tx=true&limit=1
Time of casting the vote is also available in the returned value. Users can also adjust a combo of parameters to retrieve more information on voting transactions at once. For other parameters please refer to: https://developers.tron.network/reference
Query timeout had been an issue with transaction interface. To solve the problem, we combed through the entire TronGrid system and optimized the access layer, business process layer and data persistence layer to clear the bottleneck and better the performance of other parts of the system. Tested interface access speed on average is now 5 times faster than before.
In the old TronGrid version, request parameters can only be written in lowercase letters, which is not convenient enough. The new version now supports retrieving data normally by entering parameters in capital letters.
USDJ is a stablecoin issued via decentralized smart contracts on the TRON network that is pegged to US dollars at 1:1; JST is the native token of TRON’s DeFi project that can be used for interest payment, platform maintenance, voting-based governance and other activities on JUST. TronGrid is among the first to support the two tokens. Feel free to try out the new feature!
Users with the old TronGrid version could not query account information of unactivated addresses even though such addresses may hold USDT and USDC. This has been fixed in the new version where users can query account information of unactivated addresses via TronGrid.