Hello, and welcome back to another Greymass Progress Update! We hope everyone had a restful and joyful holiday season. Today we have improvements for Unicove and several updates to Wharfkit’s components on the docket. So let’s dive right in!
Unicove, our web wallet, has gotten some attention lately with support for new tokens and a few bug fixes. Users can now enjoy:
- Support for new tokens on the Transfer page — We’ve added USDT, SEOS, BOX, and USN to Unicove’s Transfer page, to help users who may want to transfer these tokens between EOS and the EOS EVM bridge.
- Token balance bug fix — Some users may have noticed that sEOS and CHEX token balances were not displaying properly. We have now resolved this issue.
The Session Kit has had two new releases in the last six weeks, with both v1.2.1 and v1.2.2 going live. The updates include:
- Implementation of return values — Previously, the Session Kit focused only on performing transactions, and did not do anything with values that were returned after a transaction was completed. Now the Session Kit watches for these values, decodes them, and returns them to the developers application so they can use those values in their app.
- Web renderer updates — We released v1.1.4 of the Session Kit’s web renderer, to fix a build issue with the “style overwrite” feature. This allows developers to customize the web renderer to some extent.
- Various bug fixes — For users who log into Wharf with Cleos, we’ve now updated the related plugin so that the wallet logo displays properly. We also addressed a bug within the Session Kit where some return values could not be decoded and were not returning values properly. If you’ve run into either of these issues, please update to the latest version.
We released version 1.1.2 of the Contract Kit, in order to resolve an issue with the “get” method. Previously, it was throwing an error when the Table_get method didn’t return any results. We’ve now updated it so that when no results are found, the result comes back as “undefined,” to alert the developer that there weren’t any results without throwing an error. If you’ve been running into this issue, please update to the latest version.
We’ve now released v1.0.0 of the AtomicAssets library for Wharfkit, which allows developers to access the AtomicAssets and AtomicMarket API endpoints to retrieve data from the chain. Developers can also create strongly typed assets, collections, schemas, offers, and more for use in their applications.
This library also showcases how the Contract Kit and CLI tools can be used together to create a comprehensive library dedicated to a smart contract, so we hope people will check it out here.
The ABI Cache has now been updated to version 1.2.1 based on developer feedback, in order to address an issue where some data was being duplicated in the cache. This has now been resolved.
CLI (Command Line Interface)
The CLI has received a few different updates over the last six weeks, with the latest being v2.5.0. These updates include:
- Account name flexibility — The generated code now allows you to pass in an account name where the contract is deployed, rather than it just being a fixed value based on where it was generated from.
- Improved action parameters — We’ve changed how action parameters were being generated in the output code, so that they’re now usable by application developers.
- Streamlined command line parameters — We’ve removed the need for some command line parameters when generating code locally from an ABI.
- Various bug fixes — We resolved an issue with how variants were being generated for advanced use-cases, fixed an issue where structs that extend other structs weren’t being properly reflected in the generated code, adjusted how the CLI treats upper/lowercasing in order to maintain consistency with the defined smart contract, and changed how types are generated in the ActionParams to reduce errors.
You can find the latest version of the CLI here.
We recently released v1.0.2 and v1.0.3 of the Antelope library, which is now a part of Wharfkit. The latest versions take developer feedback into consideration, and now include:
- New field for network resource data — We’ve added a field for network resource data from an account, which indicates the last time resources were used, the amount currently being used, and the account’s subjective billing usage.
- Added get_block_info API call — Previously the Antelope library did not include this API endpoint, which is offered by Leap and returns information about a specific block. It was added in v1.0.3.
- Various bug fixes — We addressed a dependency issue, among other bug fixes.
The latest version of the Antelope library can be found here.
And that’s all for now, folks! Stay safe out there, and we’ll see you in the next progress update.