Building a public chain ecosystem can be seen as building an online city, in both of them, the infrastructure is a basic requirement.
As the most important underlying infrastructure of the ecosystem, the mainnet’s performance determines the development of the public chain ecosystem. In the more than a year since the mainnet launch, the IOST development team has maintained a technically innovative attitude and has carried out multiple and frequent version updates and optimizations. Today, the Olympus v3.3.3 IOST mainnet is officially launched!
The key improvement of the newly released version is the developer experience. By improving the RPC interface and improving the command line tools and other three major improvements, developers’ working experience and efficiency of developing DApps on the IOST mainnet have been greatly improved.
The following is a detailed introduction to the main optimizations of v3.3.3:
A. RPC improvements
1. Fixed the issue of transaction sending failure caused by inaccurate end-user system time
Fixed an issue where some users’ inaccurate system time was causing transactions to be rejected and displaying “TimeError”.
2. Added RPC showing all RAM used by the contract
Added ListContractStorage API to get the key-value pairs of all RAM consumed by the specified contract. It is convenient for contract developers to analyze their RAM usage and for developers to debug contracts.
B. iWallet command line improvements
1. When using the -s option to specify the RPC address, it is possible to omit the default port number 30002
E.g: iwallet -s 18.209.137.246:30002 state
Can be written as: iwallet -s 18.209.137.246 state
2. If the contract call parameters are of a single string type, simplification is allowed.
E.g: iwallet -s 18.209.137.246 -a lispcc call vote_producer.iost getVoterBonus ‘[“obvote”]’
Can be written as: iwallet -s 18.209.137.246 -a lispcc call vote_producer.iost getVoterBonus obvote
3. If the RPC node allows the transaction to not be executed on the chain (because of the large resource consumption, this feature is not enabled by default. You can modify trytx: true in the configuration.) When the iwallet call command invokes a contract, you can add the — try_tx option to make the contract execute but not go to the chain.
C. Tool improvements
Contract version management tool
We have developed a new contract version management tool. When the contract owner needs to upgrade the contract, he can use this tool to compare the difference between the local contract and the on-chain contract, to better ensure the correctness of the changes.
Link:
Join IOST Community
IOST is committed to building a developer-friendly public chain platform. In the future, IOST will continue to innovate and to upgrade and optimize the mainnet, bringing more powerful underlying infrastructure support and good development experience to all mainnet ecosystem users.
Thanks to the unremitting efforts of the IOST development team, developers from all over the world are also welcome to join our developer community.
- IOST Developer Documents: https://developers.iost.io
- IOST Developer Community: https://invite.iost.io
If you would like to hang out with the IOST community, check out the following official channels:
- International English Telegram Group: https://t.me/officialios
- IOST Announcement Channel: https://t.me/iost_announcements
- IOST Official Twitter: https://twitter.com/IOStoken
- IOST CTO Terry Wang Twitter: https://twitter.com/terrence_iost
- IOST CEO Jimmy Zhong Twitter: https://twitter.com/jimmyzhong_iost
- Reddit: https://www.reddit.com/r/IOStoken
- Facebook Page: https://www.facebook.com/IOSTofficial
- Facebook Group: http://bit.ly/IOST-FB-Group
…………………………………………………….
