top of page
Lion Blau

Lion Blau

Making self-custody usable for everyday users

Exploring how familiar web2 patterns can reduce complexity, risk, and cognitive load in web3 wallets. A concept project focused on onboarding, transactions, and trust in self-custodial crypto experiences.

2023  ·  Role: Concept, Product & UX/UI Design

2023

Role: End-to-end Product Design (UX/UI, Research, Prototyping)

ONBOARDING 1.1.png

Guided onboarding over flexibility

Make first-time setup safe and understandable with clear defaults

Reduce risk, not just friction

Design flows that prevent irreversible mistakes

End-to-end wallet flows

Cover onboarding, transactions, and key management

Familiar patterns for unfamiliar systems

Use web2 mental models to explain web3

Key insights from research

Users don’t understand what actions actually do

Transactions feel opaque—users confirm actions without fully understanding outcomes, fees, or consequences.

Fear of irreversible mistakes blocks engagement

Self-custody introduces high perceived risk, leading to hesitation or reliance on external tools.

Web2 mental models don’t transfer

Users expect confirmation, feedback, and reversibility—patterns that are often missing in web3 tools.

These insights shaped how I approached onboarding, transactions, and risk reduction across the product.

Detail View_NFT.png

Clear transaction summaries reduce uncertainty before committing on-chain.

Detail View_NFT-1.png

Even simple actions like swapping tokens require understanding fees, networks, and outcomes upfront.

Context

Understanding web3 shouldn’t feel fragmented

Web3 tools are still built for crypto-native users. Newcomers are expected to manage wallets, fees, and transactions across disconnected interfaces—often without clear feedback or guidance. This creates high cognitive load in environments where mistakes are irreversible.

Portal explores how familiar web2 UX patterns can reduce risk, clarify actions, and make self-custody usable for everyday users.

Frame 8657.png

Approach

Translating web2 UX to web3 systems

Web3 introduces new constraints—irreversible actions, visible transactions, and decentralized logic. Instead of reinventing interaction patterns, I explored how established web2 principles—like feedback, confirmation, and progressive disclosure—can be adapted to these constraints.

This approach makes complex systems more understandable without hiding their underlying mechanics.

Screenshot 2025-11-15 at 17.39.45.png

Principles

Designing for clarity, safety, and trust

Make actions understandable

Clearly communicate what will happen before users commit.

Reduce irreversible risk
Design safeguards for high-impact decisions.

Guide users through complexity

Break down flows into manageable steps.

Expose system status

Show what’s happening and what just happened.

Leverage familiar patterns

Use known interaction models to explain new systems.

Flows

Structuring complex actions into clear flows

I mapped key user journeys—from onboarding to transactions—into structured, step-by-step flows to make complex actions understandable and predictable.

Mapping these flows made friction, decision points, and missing safeguards explicit—especially around irreversible actions and transaction feedback. These insights directly informed how guidance, confirmations, and constraints were introduced across the product.

Wallet top-up flow

Revealed early drop-off points around funding and network selection—informing where defaults and guidance were needed.

Portal Flow 1
Portal Flow 2

Token swap flow

Exposed confusion around fees and irreversible confirmations—leading to clearer review steps and stronger transaction feedback.

To support these flows at scale, I defined a clear underlying structure:

Portal Sitemap

Information architecture

Defined a system that separates assets, interactions, and permissions—making complex wallet behavior easier to navigate and reason about.

Solutions

Making transactions understandable and safe

Interacting with smart contracts is one of the most critical and risky moments in web3. I designed a system of bottom sheets that guides users through approvals, signatures, and confirmations — breaking complex actions into clear, step-by-step decisions.

Contextual information such as fees, outcomes, and risks is surfaced at the right moment, helping users act with confidence.

ONBOARDING 1_1.avif

Confirm transaction — Clear transaction summaries reduce uncertainty before committing on-chain.

ONBOARDING 1_1-1.avif

Custom transaction fees — 

Flexible fee controls balance simplicity for beginners with control for advanced users.

Group 865633.avif

Real-time feedback helps users understand system state and outcomes.

ONBOARDING 1_1-2.avif

Kill switch — A single action to revoke permissions enables fast recovery in high-risk situations.

Portal's browser includes bookmarks and shortcuts to last visited dApps and websites. The user can personalize the browser homepage to, e.g., show current gas prices and recent on-chain bounties

ONBOARDING 1_1-4.avif

Browser — Integrated dApp access reduces context switching and keeps interactions in one place.

ONBOARDING 1_1-7.avif

Network selection — Making networks explicit helps users understand where actions happen.

ONBOARDING 1_1-1 (1).avif

Allowance management — Visibility into permissions reduces hidden risk in DeFi interactions.

reflecton

Designing for responsibility in web3

Designing for self-custody means designing for responsibility. Unlike traditional products, mistakes in web3 are often irreversible, which fundamentally changes how users approach interaction.

This project reinforced that usability in web3 isn’t about removing complexity—it’s about making it understandable and safe to navigate. The goal is not to hide systems, but to expose them in a way that users can build confidence over time.

It also highlighted the importance of designing beyond individual screens. Trust emerges across flows, feedback, and consistency—not from isolated UI decisions.

Ultimately, the challenge is not reducing friction, but placing it intentionally—where it protects users without blocking progress.

I design systems, not just screens—products that stay clear under real-world use.

iPhone 17.webp

Next case

Designing a reusable LiveOps system for a Telegram-native game

From a simple tap mechanic to a reusable LiveOps system powering repeatable events, progression, and long-term retention.

Lead Product Design · LiveOps systems

View case
iPhone 17.webp
Rectangle 6.png
bottom of page