What is an Embedded Wallet? An embedded wallet is a wallet created inside an application, typically via email or social login, that removes the need for users to install a wallet extension or manage a seed phrase to get onchain.
Embedded Wallet Explained Traditional crypto onboarding asks a newcomer to install an extension, write down twelve secret words, and fund the wallet, before they have done anything in your app. Most people leave.
An embedded wallet removes all of that. The user signs up with an email or Google account, like any normal app, and a wallet is created for them invisibly in the background.
They can transact immediately, and the app can sponsor gas so the first transaction is free. The tradeoff: key management shifts to infrastructure providers, with various models for how much control the user ultimately holds.
What an Embedded Wallet Means For Audience
Use Case
Product and onboarding teams
Remove wallet setup friction so mainstream users can reach a first transaction in minutes
Developers
Integrate wallet infrastructure SDKs instead of requiring external wallet extensions
Growth teams
Lift activation rates by collapsing the wallet install and seed phrase steps out of the funnel
Examples A consumer app creates an embedded wallet at email signup, and the user mints their first item without knowing a wallet was involved.
A game pairs embedded wallets with sponsored gas so new players transact onchain without buying crypto first.
A team A/B tests embedded wallets against extension-only onboarding and doubles its connect-to-transaction rate.
A DeFi app offers embedded wallets for newcomers with an export path to self-custody as users gain confidence.
FAQs How do embedded wallets work? A wallet keypair is generated and managed by infrastructure integrated into the app, secured through methods like key sharding or secure enclaves, and authenticated by the user's email, social login, or passkey.
Are embedded wallets custodial? It depends on the implementation. Many are non-custodial via distributed key management where no party holds the full key; others are effectively custodial. The key model matters.
Why do embedded wallets improve activation? They remove the biggest onboarding cliffs, extension installs, seed phrases, and acquiring gas, which are where most new users abandon Web3 funnels.
Can users move from an embedded wallet to self-custody? Good implementations allow key export or asset transfer to an external wallet, giving users an upgrade path as their experience grows.
How do embedded wallets affect analytics? Every user has a wallet from signup, so wallet-level analytics covers the entire user base rather than only users who brought their own wallet.