If you have only ever used a wallet like the one behind Simple Base Swap, "connect your wallet" probably means opening an app, confirming a request, and occasionally checking your recovery phrase. But a growing number of apps built on Base, including some games and Farcaster mini apps, skip that flow entirely. You sign in with an email address or a Google account, and a wallet simply appears, ready to hold funds and send transactions. There is no seed phrase screen at any point.
This article explains how that works, what an embedded wallet actually is under the hood, and why it is a genuinely different custody model from the self-custody wallet this site is about, not just a friendlier login screen.
What an embedded wallet is
An embedded wallet is a crypto wallet that lives inside another app's login flow instead of existing as its own separate application. The app you are using, a game, a marketplace, a social client, integrates a wallet provider's software development kit, and that kit creates and manages a wallet for you the first time you sign in. From your side, the experience looks like signing into any ordinary web account. Underneath, a real blockchain address with real keys is being created and controlled on your behalf.
This is different from a browser extension or mobile wallet you install yourself, and it is also different from an exchange account, even though it can feel similar to both. The address is genuinely yours in the sense that it exists on Base and you can see its activity on a block explorer. What differs is who holds the keys that control it, and how.
Where MPC fits in
Most embedded wallet providers rely on a technique called multi party computation, usually shortened to MPC, and specifically a variant called threshold signature schemes, or TSS-MPC.
In a standard wallet, one private key exists somewhere, whether that is on your device, on a hardware wallet, or written on paper, and whoever holds that single key can sign transactions. MPC changes this by never assembling a full private key at all. Instead, the key is mathematically split into several shares, distributed across different parties, for example one share on your device and one on the wallet provider's servers. When a transaction needs signing, those parties each perform part of a cryptographic computation and combine the results into a valid signature, without any single party ever seeing the complete key.
The practical effect is that no single compromised device or server hands over full control of the wallet. Someone who steals your phone does not get a usable key share on its own, and a breach of the provider's servers does not expose a working key either, since neither side holds the whole thing. This is a real security improvement over a single, unguarded private key sitting in one place.
What you gain
The appeal of this model is straightforward. There is no seed phrase to write down, lose, or have stolen through the kind of phishing described in our recovery phrase safety guide. Account recovery generally works the same way it does for a normal web account, through the app's own login and identity checks, rather than through a phrase that permanently disappears the moment it is lost. For a game or a social app where most people have never touched crypto before, this removes the single biggest onboarding obstacle.
What actually changes about custody
This is the part worth sitting with. In a self-custody wallet, you alone hold the key material, and no company can freeze, recover, or move your funds on your behalf, for better and for worse. In an MPC embedded wallet, you typically hold one share and the provider infrastructure holds another. That means the provider is not a bystander. It is one of the parties required to produce a valid signature.
In practice, this shifts real decisions onto the provider and the app built on top of it. Their infrastructure choices determine whether your share of the key is genuinely inaccessible to them, how account recovery is verified, what happens if their service goes offline, and what their terms of service say about their ability to restrict an account. Reputable providers publish detail on how they structure this, but it is contractual and infrastructural trust, not the mathematical guarantee you get from holding every key share yourself.
None of this makes embedded wallets unsafe. It makes them a different point on the custody spectrum, closer to self-custody than a centralized exchange account, but not identical to a wallet where you are the only party who can ever sign.
How to tell which kind of wallet you are using
A few signs point to an embedded wallet rather than a traditional self-custody one:
- You created the wallet by signing in with an email address, phone number, or social account, and were never shown a recovery phrase.
- The wallet only exists inside one specific app, rather than being an independent app or browser extension you installed yourself.
- Recovering access after losing your device involves the app's normal login process, not a 12 or 24 word phrase.
If any of those apply, you are using an embedded wallet, and it is worth reading that provider's own documentation on how they handle key shares and recovery before moving meaningful funds into it.
Why this matters even if you only use a self-custody wallet
You do not need to use an embedded wallet to benefit from understanding one. Base's ecosystem includes both models side by side, and you will likely encounter apps built on embedded wallets even if your main holdings stay in a wallet you fully control. Knowing the difference helps you make a deliberate choice about where to keep what, rather than assuming every address labeled "wallet" carries the same guarantees. A self-custody wallet like the one this site supports puts you as the only required signer. An embedded wallet trades some of that independence for a smoother first experience. Neither is automatically the right answer for every amount or every use case, and knowing which one you are holding funds in is the first step to deciding that for yourself.