Safety-First Blockchain UX
Crypto / Blockchain Patterns
The app NEVER sees or touches seed phrases or private keys.
Wallet adapters delegate signing. We only know public keys.
Why This Exists
A wallet's notification about a "Genesis token" was clicked. The flow silently deleted the active seed phrase. No balance detection. No explicit warning. Funds permanently inaccessible.
These patterns demonstrate how to prevent such disasters.
Core Safety Rules
App never sees private keys
Wallet adapters handle all signing
Balance check before destruction
Block actions that would strand funds
Nuclear warnings for one-way ops
Multi-step confirmation with typed phrase
Asset ops ≠ Key ops
NFT transfers never modify seed phrases
Blockchain Explorations
Solana
Wallet adapter patterns, transaction simulation, balance guards. Reference implementation.
Ethereum
RainbowKit/wagmi patterns, EIP-712 signing, ENS resolution.
Sui
Move-based object model, Sui wallet patterns.
Safety Pattern Categories
Connection Patterns
Safe wallet connection without key exposure. Proper state management and disconnection flows.
Transaction Safety
Simulate transactions before signing. Show users exactly what will happen to their balances.
Destructive Operations
Nuclear warnings with multi-step confirmation for any action that could cause irreversible harm.
Asset Handling
Correct patterns for NFT/token operations. Asset ops NEVER trigger key lifecycle changes.
The Safety Mindset
Blockchain transactions are irreversible. Lost funds are lost forever. This fundamentally changes how we design interfaces.
Prevention over recovery — There is no undo button.
Friction is a feature — Dangerous actions should feel dangerous.
Show, don't tell — Simulate the outcome before execution.
Never surprise — Users must understand exactly what will happen.