Helping people understand, protect, and pass on their digital assets.
01. Overview
Nearly 90% of crypto holders worry about what happens to their assets when they die. Only 24% have a will that accounts for it.
Most wallets are built purely around transactions. Security, recovery, and inheritance often live in separate, disconnected tools, forcing users to manage ownership across fragmented experiences.
TrustCore explores a different idea: What if ownership became the very foundation of the wallet experience?
02. The Problem & Discovery
Early Findings: A Clash of Mental Models
Through our discovery phase, we realized users weren't struggling because information was missing. They were struggling because the product spoke a language they didn't understand:
- Users talked about: Assets, security, and protecting what they owned in plain language.
- Wallets talked about: Accounts, addresses, permissions, and cryptographic signatures.
Core Pain Points
- Fragmented Experience: Users must rely on multiple disconnected products to manage security, recovery, and ownership.
- The Identity Crisis: Wallet and Account are often confused, making true asset ownership difficult to grasp.
- Premature Decisions: Advanced features force critical configuration choices before users even understand what those decisions mean.
03. The Solution: A New Mental Model
How do you redesign a wallet without just adding another settings screen?
Instead of organizing the experience around wallet technologies, TrustCore organizes it around ownership hierarchy:
Assets (First)
Protection (Second)
Advanced Configuration
04. Design Execution
Guided Account Creation
The Approach: Users learn the purpose of Standard, Smart, and Multisig accounts before choosing one.
UX Impact: Decisions are framed around user goals and structural benefits rather than technical jargon.
Multisig Made Understandable
The Approach: Instead of throwing signer thresholds and technical permissions at the user, TrustCore starts with context.
UX Impact: Users learn why multisig exists for their specific use case before being asked to configure it.
05. Design Principles
Familiar Patterns
Leverage conventions users already understand from traditional banking.
Progressive Disclosure
Show architectural complexity only when it becomes relevant to the task.
Clarity & Trust
Use plain language and strict visual hierarchy to support high-stakes, confident decisions.
Key Takeaways
"Mental models matter more than interface polish."
Users gain true confidence when products match how they naturally think. For crypto wallets, ownership is a far more intuitive mental model than accounts, permissions, and technical architecture. Trust doesn't come from hiding complexity, it comes from making complexity understandable.
Other Screens
