Today, we’re excited to announce updates for Sui Wallet. In addition to a refreshed look, you’ll find several refined features that will improve how you use and interact with the wallet.
We recently introduced Sui Wallet, an open source self-custody wallet that is part of a strategy to bootstrap and expedite the growth of the Sui ecosystem.
1. Enhanced User Experience & Polish
Wallets are simultaneously the biggest onboarding tool and a potentially significant barrier to entering web3. Because most users need a wallet to interact with dApps and access their assets, the experience of using a wallet can be painful due to low context and high requirements for trust.
With each release, the team behind Sui Wallet strives to improve the wallet experience for all users. To list a few changes since July:
Redesigned NFT Tab
- Owned NFTs are presented in a grid. Click into each NFT to view more detail.
- From a detailed NFT view, you can go directly to the explorer or trigger the send NFT flow.
Redesigned Activity Tab
- Click into each line item to view a detailed receipt of each past transaction and track your activities.
- When available, the amount of SUI tokens and the NFT involved in the transaction are also listed for easy access.
App Connection Status in Wallet Header
- Once connected with an apps, the wallet header will show connectivity status and the app’s URL.
- For extra security, you can now easily disconnect from the app with one click.
2. Updated Human-Readable Transactions
Sui Move's object-based and ownership-centric model protects users from fraud and phishing attacks. By design, the Move function called in each signing request requires both involved objects, and how these objects will be involved as arguments.
Currently Sui Wallet supports three levels of permissions for each signing request:
- arg: &<arg_type> means this arg can only be read in the function.
- arg: &mut <arg_type> means this arg can only be read and modified, but cannot be transferred or destroyed.
- arg: <arg_type> means full access to this arg, including ability to transfer and destroy. Related ownership checks are also enforced.
With this implementation, access permissions in web3 are as simple and easy to understand as web2 Android-style or iOS-style permissions.
3. The New Apps Tab
A new addition to the Sui Wallet basic interface is the Apps Tab.
First, the Active Connections view shows a list of apps your wallet is connected to. This allows you to quickly find a list of apps your wallet is connected with, similar to browsing history, and gives you the ability to disconnect from those apps.
Second, in the Playground view, we added buttons for immediate testing. quickly mint a DevNetNFT with Mint an NFT and view your address in the Sui Explorer with View account on Sui Explorer. In addition, as a way to amplify projects being built on the Sui Network, the Sui Wallet will periodically features apps that are live on DevNet. Please *note* that this list of apps does not suggest any affiliation or endorsement, as the Sui Wallet team does not conduct audits nor make endorsements. For a list of current partners, please see our list of official partners on the Sui Ecosystem Overview page.
In addition to UI and feature updates, there are also several ongoing developer experience improvements happening behind the scenes.
4. Updates on Wallet Adapters
Wallet adapters, through normalizing interactions with wallets, can be a gamechanger for boosting network effects. They handle detecting which wallets are installed on a users' device, and provide dApp developers an easy-to-use API to send transactions through a user-selected wallet. This enables both developers and users to gain access to the whole ecosystem easily.
Browser wallets: We are currently working on a standard for browser wallets (in collaboration with Solana), which should dramatically simplify the process for wallet adapters for extensions. In general, browser wallet developers will not need to develop or maintain wallet adapters, and will instead just need to ensure that their wallet is discoverable in the browser through a standardized interface. We're still in the process of developing and documenting this interface, and will share more in upcoming weeks.
Non-browser wallets: We welcome contributions for adding support for non-browser wallets! Feel free to look through the wallet adapter packages in our repo to see the general interface that needs to be adhered to. We're happy to engage with you to explore the best way to integrate your wallet into the wallet adapter ecosystem.