Based on this we started sketching rough ideas of how our elements would into this layout
Why this layout was chosen:
Quick switch on wallets between wallets and a clear visibility
Main navigation was grouped based on purpose rather than actions
Information hierarchy was defined with progressive disclosure model
Ease of Wallet management
Managing a wallet in the web3 domain is more complex than it seems. To grasp it, you need to understand some basics first.
EVM & Non-EVM chains:
Ethereum Virtual Machine (EVM) is like a computer inside Ethereum. It runs smart contracts.
Non-EVM platforms use different computers and languages for their contracts.
Wallet Address:
A wallet address is a unique code for your digital wallet. It's how you send or get coins.
Crypto Wallets:
A crypto wallet is like a digital purse for your coins. It keeps your secret codes and helps you use your coins on different systems. But here's the tricky part: some wallets only work on certain systems. So, sometimes you need different wallets for different coins.
a simple illustration for the same would be
Our design smoothly imports standard wallets and connects multi-chain wallets. While sending one request for multiple connections isn't possible, we keep a database of supported chains. This lets users connect with them individually, offering flexibility and convenience in managing multiple wallets.
And voilà!
