Lumen is a self-custodial crypto wallet designed for people who want financial sovereignty without needing to become blockchain engineers. Hold, swap, and spend onchain assets with the interaction simplicity of a banking app — and complete control over your own keys.
01 — The Problem
Self-custodial wallets have historically been the domain of users already fluent in seed phrases, gas fees, and chain-switching. The UX complexity wasn't accidental — it was inherited from the underlying technical architecture and nobody had bothered to abstract it away. Lumen's mandate was to serve the next cohort of users: people who want sovereignty over their assets but won't read a 40-page technical guide to get it.
The paradox at the centre of this project: make the most technically complex consumer financial product feel like opening a current account. The answer turned out to be progressive disclosure — not hiding complexity, but sequencing it so the user only encounters it when they're ready for it.
Self-custody means the user holds all the risk. Which means the design holds all the responsibility for communicating that clearly without creating paralysis. Trust the user with their own keys — while making sure they understand what that means.
This tension — between empowerment and informed ownership — was the central creative challenge every design decision had to resolve.
Research Insights
02 — User Research
Lumen's users range from DeFi-native engineers who want true key ownership and multi-chain access, to financial professionals seeking non-custodial yield, to crypto-curious newcomers who want to buy their first ETH without a YouTube tutorial.
03 — Business Challenges
Seed phrase generation and backup is the most critical and most failure-prone moment in self-custody onboarding. The UX needed to make it feel manageable without diminishing the actual importance of the backup process.
Supporting 12 chains is a strength and a UX liability simultaneously. Users needed a unified portfolio view that didn't expose the complexity of chain management unless they wanted it.
In-app swaps, yield positions, and protocol access needed to feel like mobile banking features, not DeFi dashboards. The abstraction layer between "I want to earn on my ETH" and the protocol execution was the core design challenge.
Self-custody means Lumen cannot recover lost funds. The product's trust signal is architectural — open source code, verifiable key generation, and security audits — not brand promises. Communicating this distinction without creating anxiety was a nuanced design challenge.
04 — Secondary Research
73% of users who begin a self-custody wallet onboarding process abandon at the seed phrase step — either due to confusion about what it is, fear of losing it, or friction in the backup process. This is the most critical UX problem in Web3. (Source: a16z Crypto State of Crypto 2024)
The total value of assets held in self-custodial wallets exceeded $1.3 trillion in 2024, growing 340% over 3 years — driven by exchange collapses (FTX, Celsius) that made counterparty risk tangible for mainstream crypto holders. (Source: Chainalysis Crypto Crime Report 2024)
67% of crypto-curious users who have not adopted self-custody cite "too complicated" as the primary barrier — above security concerns (42%) and fee complexity (38%). UX is the primary adoption lever, not education. (Source: Galaxy Digital Crypto User Survey 2024)
05 — User Stories
06 — Competitor Analysis
| Feature | MetaMask | Phantom | Rainbow | Trust Wallet | Lumen |
|---|---|---|---|---|---|
| Non-Custodial | ✓ | ✓ | ✓ | ✓ | ✓ |
| Multi-Chain | ~ | ~ | ~ | ✓ | ✓ |
| Banking-App UX | ✕ | ~ | ✓ | ~ | ✓ |
| In-App Swap | ✓ | ✓ | ✓ | ✓ | ✓ |
| DeFi Yield Access | ~ | ~ | ✕ | ~ | ✓ |
| Easy Onboarding | ✕ | ~ | ✓ | ~ | ✓ |
| Open Source | ✓ | ✕ | ~ | ✕ | ✓ |
07 — User Flow
08 — Toolkits
Tools and methods used throughout the Lumen design process — from crypto UX audit and banking app benchmarking through to iridescent visual system execution.
09 — Process
The process for Lumen kept circling back to a single tension: every time we simplified an interaction, we risked hiding information that a user genuinely needed to make a safe decision about their money. Simplification and informed consent are in constant negotiation in Web3 UX. The process below is an honest account of how we resolved that tension, which direction we chose at each decision point, and what we would do differently.
Solution Exploration
10 — Design
Web3 product design has a documented dark pattern problem: gas fees that appear only at confirmation, slippage hidden in small print, "confirm" buttons that look like "cancel." Lumen was designed with an explicit brief to surface total cost — asset value plus gas — on the swap preview screen, before any commitment. That's not a nice-to-have; it's a trust foundation. The iridescent visual system communicates that this is native internet finance, not a legacy bank trying to look modern. The distinction matters to the users this product is trying to reach.
Lumen — Web3 Self-Custodial Wallet UX
Design Highlights
Design System
A cohesive design system built to communicate financial empowerment at every touchpoint — from the iridescent mesh to the amber action accent, every token was chosen to make the user feel powerful, not anxious.
Violet anchors sovereign identity. Amber warms human action. Cyan communicates the precision and speed of onchain execution. Deep void provides the infinite depth of the onchain universe.
Syne leads display with geometric confidence. Sora handles body copy with clean, universal legibility.
11 — Impact
Lumen demonstrated that self-custody UX is a solvable problem — not through simplifying the technology, but through designing the emotional experience of key ownership with the same care as the technical execution.
Key Learnings