Problem Framings Index
38 structural questions across 8 opportunity areas
Each pain point is reframed as a precise structural question that opens up the design space instead of collapsing it into one answer. 8 are Critical severity. These framings are the classification layer between what a contract exposes and what design decisions it forces.
User Onboarding
The moment someone decides to try Ethereum, a clock starts. Within five minutes, they will either complete their first action or leave permanently. These are the walls between curiosity and that first transaction.
The Gas Hurdle
CriticalUsers must buy and transfer ETH before they can do almost anything. This multi-step onramp process creates a massive barrier for newcomers. Sponsoring initial transactions through paymasters is the most promising path forward.
Problem framing
How does a product get a first-time user to their first transaction without requiring them to understand, acquire, or manage ETH for gas first?
Solutions live
- —ERC-4337 Paymasters (54M+ smart accounts)
- —EIP-7702 Delegation (9 wallets on mainnet)
- —SmolRefuel (80+ chains)
Inscrutable Jargon
CriticalThe entire space is filled with unexplained technical terms. Worse, fundamental concepts lack consistent naming: "seed phrase," "mnemonic," "secret key," "recovery phrase," and "secret recovery phrase" all refer to the same thing. No industry glossary standard exists.
Problem framing
How does a product introduce and consistently use plain-language terms for core crypto concepts, so users build accurate mental models without needing prior knowledge?
Solutions live
- —UX writing guidelines (nobody building this)
- —Industry glossary standard (nobody building this)
English-Only Recovery Phrases
HighBIP-39 defines wordlists in several languages, yet virtually no wallet implements them. Over 75% of crypto users are non-native English speakers, leaving them to memorize words in a foreign language.
Problem framing
How does a product handle the recovery phrase step for users whose primary language is not English — whether by eliminating it, localizing it, or offering a genuinely understandable alternative?
Solutions live
- —BIP-39 multilingual wordlists (spec exists, not implemented)
- —Account Abstraction (removes seed phrase entirely)
Geographic Onramp Restrictions
HighFiat onramps inside wallets rely on third-party providers that largely cater to Western banking systems. Users in emerging markets or highly regulated jurisdictions frequently face KYC rejection and unsupported local currencies.
Problem framing
How does a product handle onboarding for users in regions where standard fiat-to-crypto onramps are unavailable, so they can reach their first transaction without hitting a dead end?
Solutions live
- —P2P onramps (Paxful, Remitano, 0.5–2% fees)
- —Local exchange partnerships (building, no global standard)
Forced Backup Friction
MediumA new user installs a wallet out of curiosity with no funds, no tokens, nothing at stake. Yet many wallets immediately present a 12-word recovery phrase and block all access until it is written down. This kills the moment of curiosity and trains users to dismiss security prompts later.
Problem framing
How does a product sequence the backup step so it matches the user's actual level of commitment and risk, without skipping it when it actually matters?
Solutions live
- —Account Abstraction (54M+ accounts)
- —Delayed or seedless onboarding (~30–40% of wallets)
Transaction Clarity
Every wallet transaction is a trust decision. Users are asked to approve things they can't read, in formats that obscure risk. These are the gaps between what the user sees and what actually happens.
Blind Signing
CriticalUsers are prompted to approve transactions without a clear, human-readable summary. This is the leading enabler of phishing attacks. Clear signing could prevent wallet drainer losses ($84M in 2025, down from $494M in 2024).
Problem framing
How does a wallet present a signing request so users can understand what they are actually authorizing, in plain language, before they commit?
Solutions live
- —Transaction simulation (standard in major wallets)
- —ERC-7730 clear signing (draft)
- —EIP-712 typed data (live, widely supported)
Signing Fatigue
HighUsers are constantly prompted with pop-ups asking them to "sign." The volume leads to rubber-stamping, creating massive security risks. Learned behavior is the primary reason phishing succeeds on experienced users.
Problem framing
How does a product reduce the number of signing steps required to complete a common action, without users losing awareness of what they're authorizing?
Solutions live
- —EIP-5792 batched calls (Final)
- —Session keys ERC-7715 (Draft, MetaMask Delegation Toolkit)
Redundant Token Approvals
HighBefore users can swap or interact with most dapps, they must first "approve" the token in a separate transaction. This is where most first-time users abandon their first DeFi interaction — they assume the dapp is broken.
Problem framing
How does a product eliminate or explain the token approval step so users can complete their intended action without hitting an unexpected blocker first?
Solutions live
- —EIP-5792 batched calls (Final)
- —Permit2 (Live, Uniswap, deployed on ETH/OP/ARB/BASE/POLY)
- —EIP-2612 permit (Live, USDC, DAI, UNI)
Token Approval Management
HighUsers can't easily find, review, or revoke existing token approvals from within their wallet. Stale unlimited approvals are ticking time bombs — exploited contracts months later drain funds from forgotten approvals.
Problem framing
How does a product give users ongoing visibility and control over the approvals they've granted, without requiring third-party tools?
Solutions live
- —Exact-amount approvals via EIP-5792 (Final)
- —Revoke.cash (Live, 100+ networks)
- —In-wallet revocation (Live, growing in major wallets)
Missing Signing Context
MediumWhen a user needs to sign multiple messages in a row, the wallet shows no context about how many signatures are needed. Without context, users can't distinguish legitimate multi-step requests from phishing inserted between steps.
Problem framing
How does a wallet communicate the full scope of a multi-step signing flow upfront, so users know what they're committing to before they start?
Solutions live
- —Multi-step signing UI (no standard, nobody building this)
Blanket Warnings
MediumWallets apply identical red warnings to all unlimited token approvals regardless of context. Users stop reading alerts entirely after repeated false alarms — truly dangerous approvals are treated identically to routine ones.
Problem framing
How does a product differentiate warning severity so that high-risk actions stand out, instead of training users to dismiss every warning?
Solutions live
- —Contextual risk scoring (building: Blockaid, Blowfish, TRM Labs)
Cross-chain Flow
Ethereum now spans dozens of networks. Users see fragmented balances, manual chain switching, and bridges that feel like sending money into a void. The protocol solved scaling. The UX hasn't caught up.
Bridging Pain
Critical70% of onboarded wallet users never complete a bridge transaction. Users who bridge incorrectly can lose funds permanently with no recourse. Bridging between chains is expensive for small amounts, slow, and anxiety-inducing.
Problem framing
How does a product make moving assets between chains feel like a single coherent action, with predictable cost, clear status, and no catastrophic failure modes?
Solutions live
- —ERC-7683 cross-chain intents (Live, $35B+ via Across)
- —Native bridges (Live per-chain)
Different L2 Addresses
HighSmart contract accounts are deployed per chain, risking different addresses on different L2s. Funds sent to an Ethereum address on a new L2 may be unreachable — irreversible and deeply frustrating with no standard recovery mechanism.
Problem framing
How does a product handle addresses across chains so users can share one address confidently, without risk of sending funds to an unreachable location?
Solutions live
- —ERC-7828 chain-specific addresses (active Draft, restructured Feb 2026)
- —CREATE2 deterministic addresses (Live, Permit2, Safe)
- —Keystore rollups (Research, Base, Scroll)
Asset Fragmentation
HighTokens scattered across chains create artificial friction. $100 spread across 5 chains can't meet DeFi minimum amounts. Users can't participate in opportunities on the "wrong" chain.
Problem framing
How does a product let users act on their total holdings across all chains without requiring them to manually consolidate assets first?
Solutions live
- —Intent-based protocols (Live: Across $35B+, Uniswap, CoW Swap)
- —Interop layer (Building, testnet live)
Fragmented Asset View
MediumUsers must manually switch networks to see their full balances. "I find myself mostly sticking to 2-3 chains max. Every time I try to spread out more, tracking everything becomes a nightmare."
Problem framing
How does a product show a user's complete holdings across all chains in one place, without hiding the chain-specific context that matters for their decisions?
Solutions live
- —Unified balance display (Live, common in major wallets)
- —EIP-7811 unified balances (Draft, no implementations)
- —Chain abstraction (Building, Particle Network, Arcana)
Manual Network Switching
MediumWhen a wallet is connected to chain A and the user wants chain B, they must manually switch. Users don't understand why their transaction "didn't work." Funds sent on the wrong network require recovery steps.
Problem framing
How does a product handle network switching so users are never blocked by being on the wrong chain when they try to take an action?
Solutions live
- —Auto-switching dapps (Building, few dapps implementing)
Safety & Security
One bad experience, one lost transaction, and a user is gone for good. Solutions should empower user agency with transparent, controllable defenses rather than opaque restrictions users never opted into.
Prevalence of Scams
CriticalSophisticated phishing attacks and address poisoning cause thousands of victims monthly. Each major scam event suppresses adoption across the entire ecosystem — media narratives after high-profile thefts erode public trust broadly.
Problem framing
How does a product help users identify fraudulent requests, contracts, and interfaces at the moment of interaction, before they've already been compromised?
Solutions live
- —Transaction simulation (Live, standard in major wallets)
- —Address poisoning detection (Building, Blockaid)
- —Wallet warnings (Live, standard)
Sending to Wrong Address
CriticalAddresses are cryptic hexadecimal strings. Clipboard hijack malware swaps addresses silently. Sending to wrong address is the #1 fear preventing mainstream users from sending transactions, and there is no recourse — no undo, no customer support.
Problem framing
How does a product reduce the risk of sending assets to an unintended address, through human-readable names, verification steps, or confirmation patterns, in a context where mistakes are permanent?
Solutions live
- —ENS support (Live, 910K+ active domains)
- —Address book (Live, not universal)
- —Transaction preview (Live, standard in major wallets)
Key Management Burden
HighUsers are solely responsible for securing a private key or seed phrase that controls all their assets. Lose it and everything is gone. Get phished and everything is gone. This single point of failure is the primary reason mainstream users stay on centralized exchanges.
Problem framing
How does a product communicate the responsibility of self-custody and offer meaningful recovery options, without misleading users about the risks or overwhelming them into giving up?
Solutions live
- —Smart accounts ERC-4337 (Live, 54M+ accounts)
- —EIP-7702 delegation (Live, 9 wallets)
- —Social recovery (Live, 44% YoY adoption)
- —Passkey signing (Building)
Spam & Junk Tokens
MediumUsers are airdropped random junk tokens and NFTs. Interacting with malicious tokens can trigger approval phishing. Token names containing URLs are social engineering at scale.
Problem framing
How does a product handle unsolicited tokens in a user's wallet in a way that neutralizes phishing vectors without hiding legitimate assets or requiring manual management?
Solutions live
- —Token list curation (Live, standard practice)
- —Spam filtering (Building, uneven across wallets)
Mobile & Connectivity
More than half of web traffic is mobile. Yet connecting a wallet from a phone browser remains one of the most broken flows in the ecosystem.
Mobile Connection Dance
CriticalOn mobile, tapping a dapp link opens the default browser, not the wallet. The user must copy the URL, switch to the wallet app, paste it into the in-app browser, and reconnect. iOS 17+ made this worse by removing automatic redirect back to browser-based dapps.
Problem framing
How does a product handle wallet connection on mobile so users can complete the connection without being bounced between apps, tabs, or broken deep links?
Solutions live
- —Deep linking standards (Building, few wallets)
- —In-wallet browsers (Live, iOS)
- —Embedded wallets (Live, Privy, Dynamic, Passport)
Mobile Apps Don't Respond
HighMobile wallet apps drop WalletConnect sessions silently. A Safari bug from iOS 15 still causes socket failures. A Chrome WebSocket change in May 2025 broke Android flows. Users tap "confirm" and nothing happens — no error, no feedback, just silence.
Problem framing
How does a product handle wallet connection failures on mobile gracefully, with clear status and recovery paths, rather than leaving users at a silent dead end?
Solutions live
- —WalletConnect mobile SDKs (Live)
- —Embedded wallets (Live, bypass connection problem entirely)
Connection Failures
MediumEIP-6963 has largely solved wallet extension conflicts on desktop. The remaining friction is on mobile, where EIP-6963 does not apply and users still face unreliable connection flows between browser and wallet apps.
Problem framing
How does a product communicate connection state clearly — connected, disconnected, or waiting — and give users a reliable path to recover when connection fails?
Solutions live
- —EIP-6963 multi-wallet discovery (Live, major wallets)
- —WalletConnect v2 (Live, many providers)
Wallet Lock-in
MediumEmbedded and app-scoped wallets tie users to a single application. Users who switch apps start over with a new address, losing transaction history, DeFi positions, governance participation, and on-chain reputation.
Problem framing
How does a product support wallet portability so users can switch providers without losing their history, identity, or access to what they've built?
Solutions live
- —Portable account standards EIP-8141 (Draft)
- —Portable embedded wallets (Building)
- —Better wallet comparison (Building)
Accessibility
Over 75% of cryptocurrency users are non-native English speakers. Most dapps are English-only, jargon-heavy, and fail basic accessibility standards. This is the largest unaddressed audience in the ecosystem.
Inscrutable Jargon
CriticalThe entire space is filled with unexplained technical terms. Even where localization exists, there is no shared glossary. Terms are either left in English surrounded by local-language UI, or translated inconsistently.
Problem framing
How does a product introduce and consistently use plain-language terms for core crypto concepts across languages, so users build accurate mental models without prior knowledge?
Solutions live
- —i18n frameworks (Live, tooling exists)
- —Industry glossary (nobody building this)
Conflicting Mental Models
HighUsers arriving from traditional finance expect bank-like concepts: accounts with balances, simple transfers, customer support. Instead they encounter gas fees, signing prompts, and token approvals. Every dapp assumes prior knowledge of both financial and blockchain mechanics.
Problem framing
How does a product bridge the gap between what users expect from Web2 apps and how Ethereum products actually behave — especially around ownership, custody, and irreversibility?
Solutions live
- —Progressive disclosure patterns (Research)
- —Contextual education (Building, mostly missing)
No Accessibility Features
HighAn estimated 80% of protocols fail to meet WCAG accessibility standards. Research shows 6 out of 10 widely used wallets have no dedicated accessibility features. As digital accessibility regulation tightens globally, this is becoming a legal compliance issue.
Problem framing
How does a product meet baseline accessibility standards — screen reader support, keyboard navigation, contrast, font sizing — in a way that's maintained as the product evolves?
Solutions live
- —WCAG compliance (Live in small amounts, 80% of protocols still fail)
- —Accessibility audits (Research, rare)
No Trustworthy Help Channels
HighWhen users get stuck, they turn to Telegram groups and Discord servers where scammers pose as helpers. There is no way for a newcomer to distinguish a real community moderator from someone trying to drain their wallet.
Problem framing
How does a product give users a reliable, scam-resistant path to get help when they are stuck, without sending them into communities where they are most vulnerable?
Solutions live
- —Official help centers (Building, Live on small scale)
- —Verified support channels (Research, nobody building)
Poor Localization
MediumMost dapps run English-only. Even where localization exists, there is no shared glossary for translating crypto-specific terms. Each project invents its own translations for gas, staking, and wallet — creating inconsistencies across languages.
Problem framing
How does a product localize not just its UI copy but its core crypto terminology, consistently and accurately, for users whose primary language is not English?
Solutions live
- —i18n frameworks (Live, tooling exists)
- —Community translations (Building, no single DeFi-dapp registry)
Protocol Design
Some UX problems can't be solved at the wallet layer. They originate in protocol design decisions that ripple outward as confusion, friction, and risk for end users.
No Default Native Account Abstraction
HighOn Ethereum, EOAs remain the default account type. Users must manage private keys, pay gas in ETH, and approve every action individually. Without native AA, dapps must support two account models, increasing complexity.
Problem framing
How does a product communicate the difference between EOA and smart account behavior, and help users access smart account benefits without requiring them to understand the underlying architecture?
Solutions live
- —ERC-4337 (Live, 54M+ accounts, 1B+ UserOps)
- —EIP-7702 (Live, 9 wallets on mainnet)
- —EIP-8141 Frame Transactions (active Draft)
On-chain Activity Is Public by Default
HighEvery transaction on Ethereum and major L2s is permanently public. Users often don't realize their complete financial activity — salary, purchases, DeFi positions — is visible to anyone who knows their address.
Problem framing
How does a product communicate the public nature of on-chain activity and offer users practical privacy options, without making privacy feel like a tool for illicit activity?
Solutions live
- —Railgun shielded balances (Live, $4.5B+ volume)
- —Stealth addresses ERC-5564 (Live, 77k via Umbra)
- —Aztec L2 (Building, ignition mainnet live)
Daily Operations
The tasks people do every day: sending tokens, checking balances, managing gas. These should be the most polished flows in the ecosystem. They are often the most frustrating.
Unpredictable Gas Fees
MediumGas costs have dropped dramatically — fee market averages around 3 gwei in 2025. But users still cannot predict what a transaction will cost before they commit. Fee spikes during network congestion still catch people off guard.
Problem framing
How does a product help users understand what a transaction will cost before they commit, including timing tradeoffs, without requiring them to understand gas mechanics?
Solutions live
- —EIP-1559 fee market (Live)
- —EIP-4844 L2 costs (Live)
- —Predictive fee UI with timing guidance (Building, Beyond tool only)
Fiat-Based Values Missing
MediumSome wallets force users to enter transaction amounts denominated in token (e.g., 0.0012 ETH) rather than in their local currency. Users have to mentally convert token prices before every send or swap.
Problem framing
How does a product let users think and transact in their local currency rather than token denominations, without obscuring the actual token amounts being moved?
Solutions live
- —Fiat denomination toggle (Live, Uniswap, major wallets)
- —Price oracle display (Live, 1 wallet practice)
No Portfolio & Tax Tracking
MediumTracking a complete financial picture across multiple chains, wallets, DeFi positions, LP rewards, airdrops, and bridge transactions is still impossible in a single tool. Users who actively use DeFi face hours of manual work each tax season.
Problem framing
How does a product help users understand their complete financial position across chains and generate accurate records for tax purposes, without requiring third-party reconciliation tools?
Solutions live
- —Koinly, CoinTracker (Live, external, not integrated)
- —Wallet-native tax tracking (Research, nobody building)
NFTs Don't Load
MediumWallets struggle to display NFTs across multiple chains. RPC endpoints go down, indexers serve stale data, and IPFS-hosted media loads slowly or not at all. The result is blank thumbnails and users who think their NFTs are gone.
Problem framing
How does a product reliably display a user's NFTs across chains, with accurate metadata and media, and communicate clearly when an asset is slow to load versus genuinely missing?
Solutions live
- —Multi-chain NFT indexing (Building, uneven)
- —NFT metadata standards ERC-4906, ERC-1155 (Live)
Token List Friction
MediumThere is no universal token registry. Users regularly encounter tokens that do not appear in their wallet or swap interface, forcing manual contract address imports that most newcomers will not attempt.
Problem framing
How does a product help users find and add tokens that aren't on default lists, without exposing them to the scam risk that manual contract address entry creates?
Solutions live
- —Token list standards (Live, Uniswap)
- —Community-curated lists (Live, Rotki, no single registry)
No Shared Design Infrastructure
MediumThere is no common component library or interaction pattern library for Ethereum dapps. Every team reinvents wallet connection, transaction confirmation, error states, and gas estimation UI from scratch.
Problem framing
How does a product contribute to and draw from shared interaction patterns, so that users can build familiarity across Ethereum interfaces rather than relearning every time?
Solutions live
- —Open-source design kits (Live, Shadcn, etc.)
- —Ecosystem design system (Research, nobody building this)
Transaction Cancellation Pain
InfoCancelling a pending transaction requires sending a replacement with the same nonce and a higher gas fee. Most major wallets now offer speed-up and cancel buttons. On L2s, where transactions confirm in seconds, stuck transactions are rare.
Problem framing
How does a product handle stuck or pending transactions, giving users clear options to cancel or speed up, without requiring them to understand nonce mechanics?
Solutions live
- —Speed-up/cancel UI (Live, common in major wallets)
- —Intent-based cancellation (Research)