User Interaction: Wallets & dApps

10 min readUpdated: March 2026

Your wallet is your identity, your bank account, and your login credential in Web3 — all in one. Understanding wallet architecture isn't just a technical skill; it's the foundation of every interaction you'll have in decentralised applications.

Wallet Architecture

A blockchain wallet doesn't store tokens — it stores private keys. Your assets exist on the blockchain; the wallet is the cryptographic tool that proves you control them. This distinction matters enormously for security design.

Modern wallets derive all keys from a single 12 or 24-word seed phrase using the BIP-39 standard. A hierarchical deterministic (HD) derivation path then generates unique key pairs for every chain and account — meaning one seed phrase can control thousands of addresses. This is powerful and dangerous: lose the seed phrase, lose everything.

Hot Wallet

Security:Medium
Convenience:High
Best for:Daily DeFi transactions, small balances
Examples:MetaMask, Rabby, Rainbow

Hardware Wallet

Security:Very High
Convenience:Low
Best for:Long-term holdings, cold storage
Examples:Ledger Nano X, Trezor Model T

Smart Contract Wallet

Security:High
Convenience:High
Best for:Teams, corporate treasuries, AA-enabled UX
Examples:Safe (Gnosis), Argent, Coinbase Smart Wallet

Multi-Sig Wallet

Security:Very High
Convenience:Low
Best for:DAO treasuries, protocol governance
Examples:Safe with 3-of-5 signers

dApp Interaction Patterns

Every action in a dApp — swapping tokens, providing liquidity, minting an NFT — follows the same underlying transaction lifecycle. Understanding this flow helps professionals debug issues and communicate clearly with users.

Transaction Lifecycle

1

Connect Wallet

WalletConnect / injected provider

2

Sign Request

EIP-4361 auth or transaction

3

Broadcast

Node submits to mempool

4

Confirm

Block inclusion + finalisation

WalletConnect v2 is the dominant protocol for connecting mobile wallets to desktop dApps — it establishes an end-to-end encrypted session via a relay server. EIP-4361 (Sign-In with Ethereum) standardises how dApps authenticate users without passwords by requesting a signed message instead of a transaction.

Gas estimation is one of the most user-confusing aspects of Web3 UX. Wallets use `eth_estimateGas` to calculate computational cost, then add a safety buffer. EIP-1559's base fee + priority tip model made gas prediction significantly more predictable on Ethereum, but estimations can still fail if state changes between simulation and execution.

Popular Wallet Ecosystem

The wallet landscape reflects the multi-chain reality — no single wallet dominates all chains. MetaMask commands the EVM ecosystem with over 30 million monthly active users, while Phantom owns Solana. Hardware wallets remain the gold standard for securing significant holdings.

MetaMask

Browser ext / Mobile

30M+ MAU

EVM

Phantom

Browser ext / Mobile

Leading Solana wallet

Solana / EVM

Rabby

Browser ext

Security-focused

EVM multi-chain

Rainbow

Mobile

Consumer-first UX

Ethereum L2s

Ledger Nano X

Hardware

6M+ devices sold

5,500+ assets

Trezor Model T

Hardware

Open-source firmware

1,000+ coins

UX Challenges and Account Abstraction

The current Web3 UX creates significant friction: users must hold native tokens for gas on every chain, seed phrases are catastrophic single points of failure, and every action requires manual transaction approvals. These barriers keep mainstream adoption limited.

ERC-4337 (Account Abstraction) fundamentally changes the model. By making wallets smart contracts rather than externally owned accounts, it enables: gas sponsorship (dApps pay gas for users), social recovery (replace seed phrase with trusted contacts), session keys (auto-approve routine transactions), and batch transactions (multiple operations in one click).

Coinbase Smart Wallet, launched in 2024, brought ERC-4337 to millions of users with passkey-based authentication — no seed phrases required. For professionals building dApps, designing around Account Abstraction primitives is rapidly becoming the expected standard rather than an advanced feature.

Key Takeaways

  • 1Wallets store private keys, not tokens — your assets live on-chain; the wallet proves ownership.
  • 2HD derivation from a single seed phrase generates unlimited addresses; seed phrase security is non-negotiable.
  • 3Four wallet types serve different needs: hot (daily use), hardware (cold storage), multi-sig (teams), smart contract (advanced UX).
  • 4Every dApp interaction follows: connect → sign → broadcast → confirm — understanding this flow is essential for debugging.
  • 5ERC-4337 Account Abstraction removes seed phrases, enables gas sponsorship, and dramatically improves Web3 UX.