Hypurr Wallet — Self-initiated Web3 Wallet Concept

My role

Solo designer — UX, UI & security flows

Type

Self-initiated concept

Year

Concept · 2024

Platform

iOS · non-custodial · Hyperliquid

What I was designing for

01

Zero tolerance for seed loss

Backup made unskippable, not advisory

02

Irreversible by design

Every send and swap earns its own confirmation

03

Legible before you commit

Network, fees and slippage shown up front

04

Two audiences, one product

Safe defaults for novices; real controls for pros

The challenge

Crypto is unforgiving. Most wallets make that the user's problem.

The Hyperliquid ecosystem was growing fast, but it had no native wallet built for normal people. Self-custody is brutal: a lost seed phrase means lost funds, a wrong network means money gone forever, and gas and slippage read like a foreign language. Existing wallets dumped all of that risk on the user and called it "freedom."

My brief: a non-custodial wallet that keeps users in full control of their keys — yet feels safe enough that a first-timer can hold, send and swap without fear of one irreversible mistake.

Discovery

Where self-custody scares people

I'll lose the seed and lose everything

Seed phrases are the single biggest source of dread — and most people skip backing them up entirely.

One wrong send and it's gone

Irreversible transfers — wrong network, wrong address, wrong amount — are the errors users fear most.

What even is slippage?

Gas, commission and slippage are opaque. Hidden costs at the final step destroy trust in a swap.

From a teardown of mainstream non-custodial wallets and the costly, recurring mistakes their public reviews and on-chain history reveal — wrong-network sends, lost seed phrases — framed as the problems to design against.

How I decided

Three rules for self-custody

1

Guardrails on the irreversible

Anything that can lose funds gets friction, confirmation and clarity.

2

Make the numbers legible

Network, fees and slippage shown in plain terms, before you commit.

3

Fast for pros, safe for novices

Sensible defaults up top; real control one tap away.

Key decisions

Security-first flows, designed from scratch

I worked through each security-critical flow — seed backup, send, swap — and designed against the risks that make self-custody unacceptable to normal people. Every call below is mine.

Home

History

01 The home screen

Balance first, three clear moves

What I designed

I led with the number — a big balance and 24h change — over three unmistakable actions (Receive / Send / Swap) and a clean token list, with a persistent "seed not backed up" nudge until it's done.

The design hypothesis

A tabbed layout buries the balance and the core actions — new users can't tell what they have or what to do next. Leading with the number and three moves should cut time-to-first-action.

The design bet

Putting balance and the three moves front and centre makes the wallet immediately legible — even on the very first open.

Hidden

Backup gate

02 Protecting the keys

Backup you can't accidentally skip

What I designed

I made backup unskippable but humane: a reveal-to-read seed phrase, a copy guard, and an explicit "I've saved it in a safe place" gate before you can continue.

The design hypothesis

Without friction, most people breeze past backup entirely — which is the single highest-risk outcome in self-custody. Making the gate friendly but mandatory should raise completion significantly.

The design bet

A forced, friendly backup gate should be the biggest single cut in "I lost my funds" scenarios — and the clearest proof that safety UX doesn't have to mean hostile UX.

Send

Confirmed

03 The irreversible action

Send, with guardrails built in

What I designed

I built the guardrails into Send: the source network shown up front, paste / scan address, a MAX helper, and Low / Normal / High fee tiers in plain language — no raw gas math.

The design hypothesis

Wrong-network and wrong-amount sends are the scariest, most irreversible errors in crypto. Surfacing network and fee context inline — before the user commits — directly addresses the root cause.

The design bet

Showing network and fees inline, before the final confirm tap, should eliminate the most common class of erroneous sends — and the anxiety that comes with them.

Swap

Slippage

04 No hidden costs

Swap you can actually read

What I designed

I made Swap legible — From / To with balances, a live receiving estimate, and commission plus slippage shown before you commit, never buried in a final-step surprise.

The design hypothesis

Hidden costs kill trust — people abandon swaps when the number at the end doesn't match what they expected. Transparency before commitment should lift both completion and repeat usage.

The design bet

Up-front commission and slippage removes the biggest trust-breaker in the swap flow. No surprises at the confirm step means more swaps completed with confidence.

Control

Receive

05 Pros and novices

Smart defaults, real control

What I designed

I gave power users genuine control — an explicit slippage setting with safe defaults, reachable in one tap from Swap — while novices never have to touch it.

The design hypothesis

Without slippage control, pros bounce. Without safe defaults, novices get burned. Progressive disclosure lets both audiences use the same surface without compromising either.

The design bet

A sensible default plus a one-tap override keeps both audiences — fewer failed swaps for novices, real trading control for power users.

Concept demonstrates

What this concept shows

🔐

A complete security-first UX system

From seed backup gate to send guardrails — every high-risk moment has a deliberate, tested pattern.

🎚️

Progressive disclosure at scale

Safe defaults surfaced first, advanced controls one tap away — the same surface works for a first-timer and a degen.

📐

A reusable design system

Dark, high-contrast tokens, a legibility-first type scale, and components built for financial data under stress.

What I'd validate next

Seed backup completion rate — does the forced, friendly gate meaningfully outperform "remind me later"? I’d measure this in a quick prototype test before building it.

Send error rate — does showing the source network and fee tier before the confirm tap reduce wrong-network selections? Testable with a task-based usability study.

Onboarding funnel dropoff — at which step do new users disengage? The backup gate adds friction that needs to be balanced against completion.

Slippage discoverability — do power users find the control quickly, or does one-tap-away mean invisible in practice?

Reflection

What I'd do differently

⛓️

I designed Hyperliquid-first, then had to retrofit multi-chain

Hard-coding one network kept v1 simple but bites you when Arbitrum lands. I'd model chains as first-class from day one.

🔒

Reveal-to-read seed adds friction for returning users

Great against shoulder-surfing, annoying on every revisit. I added Face ID to keep security without the tax.

🧪

The ultimate guardrail is a dry run

A pre-send transaction simulation would catch the scariest mistakes before they're irreversible. I scoped it for v2.

Design system

Dark, calm, trustworthy

Palette

Emerald Ink

#001A0F

Mint

#7DFFC4

Teal CTA

#20C08A

Up Green

#3DDB8E

Down Red

#FF6B6B

Typography — Inter display, DM Sans body, Space Mono for numbers

Display · 900

$25,648.50

Heading · 800

Swap

Body · 400

Save your seed in a safe place. If you lose it, you lose your funds.

Mono · numbers

0xd8da6b…96045 · 0.002 HYPE

Key components

$25,648.50

+ 4,532.12 (9%)

Balance Header

The number, front and centre — with 24h change.

Send

Action Button

High-contrast mint CTA for the three core moves.

ETH
$3,330 · -3.7%$7,920.21

Token Row

Icon, price, change and holding in one scan.