Sonar Wallet — Importing & Creating Crypto Wallets Simplified
This article aims to provide a general explanation about the process by which a user will be able to create, import, sort or understand wallet management within Sonar Wallet. This will also be shown through a real image of the filter view from a working Sonar Wallet Alpha (not a mockup!). We will not delve into the technical details and explanations, but rather just a general overview of what a Sonar Wallet user can expect.
Before we get into the details, it is important to note that we are considering a “wallet” as a multichain aggregated view which can only be imported or created through a unique seed phrase. On the other hand we are considering “accounts’’ as specific addresses which can only be imported or created by a unique private key.
As with every aspect of our development, we first identify the problem and then address it using the best UI/UX possible. In this particular case, we have tested multiple wallets currently used in DeFi and we found that in most cases there are limitations to importing or creating multiple wallets or accounts. For example, Metamask allows you to create one wallet by using a seed phrase. Then it allows you to create multiple accounts, each with a separate private key, falling under the same original wallet.
On the other hand, Trust Wallet allows you to import or create several wallets with separate seed phrases, but lacks the ability to simplify user experience through multiple account creation. This leads to a very annoying problem when trying to import wallets or accounts to and from each of those wallets. This means that it is difficult or impossible to import multiple Metamask “accounts” into Trust Wallet using a private key, and conversely, it is difficult or impossible to import multiple Trust Wallet “wallets” into Metamask using seed phrases.
Sonar is solving this dilemma by providing both options. You may choose to create or import both entire wallets or single accounts. Each wallet will be a multichain solution, an aggregated view of all holdings and is made up of several accounts. Each account falling under that wallet shall have a separate address pertaining to the blockchains supported. At Beta stage, each Sonar Wallet will have a minimum of 3 types of account addresses, mainly:
- EVM Account Address (this address includes all the EVM compatible chains, such as ETH, BSC, POLYGON)
- NEAR Account Address
- SOLANA Account Address
This is more clearly explained in the image below.
The image above is a screenshot of a working Sonar Wallet Alpha, which we have successfully tested by importing wallets from other providers. In this case we have imported one multichain wallet from Trust Wallet using a seed phrase (wallet 2). This includes the Multi EVM, Solana and Near Accounts.
Furthermore, we have imported one wallet from Metamask through a seed phrase (wallet 1), but also added another Metamask EVM account (Multi EVM 2) by using a private key. We believe this system solves the two main issues pertaining to existing solutions:
- It simplifies the understanding of how wallets, accounts, addresses, and multichain solutions work.
- It enables the users to import or create wallets and accounts as they please, while also making Sonar Wallet compatible with all other existing wallets for any system of wallet importation.
Whilst we are confident that this will satisfy prospective Sonar Wallet users, we are always happy to hear of any suggestions the community has, and we invite you to reply on any of our social networks.
Disclaimer: Designs and functionalities may be slightly revised or updated by the time BETA is launched. However, the above images provide a clear idea of the direction taken.