Korea's budget office says stablecoins could save merchants $3.8B annually. Visa says stablecoin settlement is at $20B/year and growing. These numbers assume users and merchants can interact with stablecoins.
Current wallet UX is the blocker. MetaMask and hardware wallets are power-user tools. Embedded wallets bet that the wallet should be invisible—created at login, managed by the application, never shown to the user.
Summary
Embedded wallets are wallets created and managed within an application, using existing authentication (email, social login, passkeys) instead of seed phrases. The user never sees a wallet address or manages private keys—the application handles that. The core bet: UX trumps self-custody purity. Users who won't manage seed phrases will use embedded wallets; users who won't use embedded wallets won't use crypto at all.
What is an Embedded Wallet?
Traditional wallets put the user in control of key management. Embedded wallets put the application in control, with various trust and recovery mechanisms.
Traditional Wallet Flow:
1. Download MetaMask
2. Write down 24 words
3. Fund wallet with ETH (from where?)
4. Approve transactions one by one
5. Pay gas in ETH
6. Pray you don't lose the seed phrase
Embedded Wallet Flow:
1. Sign in to app with email/Google/Apple
2. Wallet exists (you don't know, don't care)
3. App requests action: "Buy this NFT for $50"
4. You confirm (app handles gas, signing)
5. Done
What happened behind the scenes:
- Privy/Dynamic/Magic created a wallet at signup
- Key is sharded across trusted servers + device
- App requested signature, submitted tx
- Gas sponsored by app or deducted from balance
The user experience looks like any normal app. The blockchain is invisible.
The UX-Custody Tradeoff
Here's the honest tension: embedded wallets are more usable because they're less self-custodial.
When you control your keys with a hardware wallet, you're genuinely sovereign—no one can freeze your funds. When an application creates and manages your wallet, that application (and its key management provider) has power over your funds.
Custody Spectrum:
Full Self-Custody (Hardware Wallet):
- You control keys completely
- No one can help if you lose keys
- No one can freeze your funds
- UX: Painful
Embedded Wallet (Privy-style):
- Key sharded across providers + device
- Recovery possible via auth provider
- Application could theoretically restrict access
- UX: Seamless
Centralized Custody (Exchange):
- Exchange controls everything
- Full recovery, full restriction
- Not your keys, not your coins
- UX: Most familiarEmbedded wallets sit in the middle—more recoverable than self-custody, more user-controlled than exchanges.
Impact
Consumer crypto applications become viable. Games, social apps, and loyalty programs can have onchain elements without wallet onboarding friction. Users just use the app.
The $3.8B Korea savings becomes achievable. Merchants accepting stablecoins need customers who can pay in stablecoins. Embedded wallets in payment apps make that possible for normal users.
But power users won't use them. Anyone with significant assets will want self-custody. Embedded wallets serve normies, not whales. That's the right market, but it limits TVL potential.
Regulatory clarity is pending. Are embedded wallet providers custodians? The answer affects licensing requirements, user protections, and viable business models. Unclear regulation is a risk.
Failure Modes
Key Management Provider Failure: If Privy's key management infrastructure fails, users lose access to their wallets. The provider is a single point of failure—exactly what crypto was supposed to eliminate.
Social Recovery Compromise: Embedded wallets often use social recovery (email, OAuth). If someone compromises your email, they might compromise your wallet. The attack surface includes your auth provider.
Application Rug Pull: The application manages your wallet. A malicious application could drain user wallets. Users trust the application more than they trust a random DeFi contract.
Regulatory Seizure: If regulators classify embedded wallet providers as custodians, they might force compliance measures—freezes, reporting, restrictions—that users didn't expect.
What I'd Change
Transparent custody models. Every embedded wallet provider should clearly explain: who has key shares? What's the recovery process? What can the application do without user consent? Publish this prominently.
Export to self-custody path. Users should be able to export their embedded wallet to a self-custody solution. This is technically possible but often hidden. Make it a first-class feature.
Application capability limits. Let users set limits: "This app can spend up to $100/day without additional confirmation." Prevent applications from draining wallets through accumulated small transactions.
Provider diversity. Don't let one provider dominate embedded wallet infrastructure. If Privy controls 80% of embedded wallets, their failure is systemic.
Lessons
-
UX wins mass adoption. The crypto community overvalues self-custody purity. Most users will never manage seed phrases. Embedded wallets meet them where they are.
-
Custody is a spectrum, not binary. "Not your keys, not your coins" is technically true but unhelpful. Embedded wallets offer meaningful user control with practical recoverability.
-
The application is the trust relationship. With embedded wallets, users trust the application more than the blockchain. That's a different security model than traditional crypto.
-
Auth providers become critical infrastructure. Google, Apple, and email providers are now in the crypto security stack. Their security practices matter for crypto users who don't know they're crypto users.
-
Payment use cases are the killer app. The Korea merchant savings, the Visa settlement volume—these need embedded wallet UX. Trading and DeFi can tolerate power-user wallets; payments cannot.
If you're building consumer-facing applications, embedded wallets are the default recommendation. The UX improvement is transformational. Just be honest with users about the custody model—they might not care, but they deserve to know.