Hello, and welcome back to another Greymass Progress Update! We have several exciting developments to share in this edition. The Anchor Wallet for Android has received substantial updates, significantly improving performance, stability, and user experience. We’re making remarkable progress on the MetaMask snap plugin for the EOS network. Additionally, we’ve been hard at work enhancing Wharfkit’s components.
Let’s dive right in!
Anchor Wallet for Android
As you probably know, the Anchor Wallet for Android recently received a significant UI update. During this development cycle, we have continued to polish the UI, add new features, and fix bugs. This update marks a substantial step forward in the wallet’s development, ensuring it stays at the forefront of digital wallet technology.
Let’s take a closer look at what’s new:
Modern UI updates
We are continuing to enhance the user interface. This time, we have implemented updates to the Signing screen, Identity request screen, and a more informative transaction error screen. The new UI will now become the default to streamline future releases.
New Features
The DayNight theme has been implemented to address several visual issues. This includes correctly setting the Status Bar theme on launch and displaying a dark background on the Splash screen (hooray! No more flashbang when launching the app!). It also ensures the dark background is correctly displayed behind the Navigation Bar in dark mode. This will enhance the consistency of the app’s UI in dark mode within the new interface.
The error screen now features a copy button, allowing you to copy the error message quickly. The error message has also been added to appState, so we ensure it is included in the support email JSON file for easier troubleshooting.
We have implemented lazy loading for screens associated with less commonly used routes. This optimization should speed up app loading times, as the code for features like the Export Backup Sheet will only be loaded if the user accesses that specific route.
The default setting for new accounts has been changed to enable exportable private keys. This setting can still be disabled through the Advanced options.
The account details screen has also been updated to transition from “buttons” to “list actions,” making it more consistent with other app areas.
Various bug fixes
The update also includes a range of bug fixes and improvements that address minor issues, enhancing the wallet’s overall performance and stability. These fixes ensure a smoother and more reliable user experience, reducing the likelihood of crashes and other interruptions.
Metamask Snap plugin for Antelope
The Greymass team has been diligently working on the MetaMask snap plugin for Antelope-based blockchains. This innovative plugin will enable users to integrate their accounts with MetaMask, allowing them to sign transactions using the familiar MetaMask interface. We have reached a significant milestone in this project: successfully listing EOS accounts in MetaMask and signing transactions.
This effort represents the first step toward our broader vision of easing the onboarding experience. By integrating with MetaMask, we aim to make the ecosystem more accessible and user-friendly, ultimately driving greater adoption and ease of use.
The plugin is currently in closed development and unavailable to the public while we conduct additional tests and develop the UI. Despite this, we are very excited about this project and eagerly anticipate presenting it to the public soon.
Wharf Kit Updates
Common Library
To support the MetaMask integration, the wharfkit/common library received an update to include SLIP-0044 codes. This update is essential for the MetaMask plugin, as it helps identify the key derivation methods for various Antelope-based blockchains.
Antelope Core Library
The antelope library also received updates:
- A new quantity field has been added to the Asset class, which can return the formatted number of tokens without including the token symbol in the string.
- The error messages from the Serializer have been updated to include the field and path, indicating where errors occur during serialization.
Autocorrect Plugin
Additionally, the transact-plugin-autocorrect received a fix for an issue where a lack of RAM could cause renting CPU and NET to fail. A check is now performed to ensure that the rental of resources will succeed by purchasing additional RAM when required during this process.
And that’s all for now, folks! Stay safe out there, and we’ll see you in the next progress update.
