Product Iteration

Multi-Wallet

Multi-Wallet hero
The hard part wasn't the wallet switcher. It was deciding what 'current wallet' means in a multi-surface terminal.
Role

Lead Product Designer + Frontend

Company

Quickscope

Timeline

2025–2026

Type

Product Iteration · Security UX · Crypto

Problem

Serious meme coin traders run multiple wallets — hot wallets for active trading, separate wallets per strategy, team wallets. Quickscope initially supported one wallet per user, which limited power users and created friction for traders driving most of the volume. Multi-wallet isn't just a UI feature. It requires decisions about security architecture, global vs local context, and progressive complexity across a 3-phase rollout.

01

Basic multi-wallet

Add, import, and switch between wallets. Establish the security model for private key visibility — show only for wallets the user explicitly unlocked, with friction to prevent accidental exposure.

02

Global vs local context

Define how 'active wallet' propagates — globally (everything switches) vs per-widget (only the focused panel updates). Designed the wallet context model and the selector component that makes the current state legible.

Multi-Wallet — Global vs local context 1Multi-Wallet — Global vs local context 2
03

Wallet dashboard

A full wallet management interface — view balances, track performance per wallet, deposit, transfer, manage labels. Becomes the account layer for the entire terminal.

Outcome
Back to work