If you use a Coinbase Smart Wallet (now also branded as a Base Account) to connect to apps on Base, you may have noticed that some apps feel different. Instead of a passkey prompt for every single click, the app seems to act on its own for small, routine actions, and only asks you to confirm when something bigger happens. In many cases, what is happening behind the scenes is that the app created a sub account.
This article explains what a sub account is, why developers use them, and what it changes for you as a wallet holder. It is a technical feature of account abstraction on Base, not a product Simple Base Swap offers, but understanding it helps you make sense of prompts you may see in other Base apps.
The problem sub accounts try to solve
A passkey backed smart wallet is more convenient than typing a recovery phrase into a signing prompt, but it still asks for a biometric or device confirmation on every transaction by default. For an app where you take one action, like a single swap, that is fine. For an app where you might take dozens of small actions in a session, such as a game or a trading interface, confirming each one gets tiresome fast.
Sub accounts are Coinbase's and Base's answer to that friction. Rather than asking your main wallet to sign every action, an app can set up a separate account that belongs to a specific app context, and that account can act with far fewer prompts.
What a sub account actually is
A sub account is a smart contract account that is linked to your main Smart Wallet as a child account. Base's documentation describes this as a parent and child relationship, standardized through a wallet method called ERC-7895, which lets an app request the creation of this kind of linked account during connection.
A few things are worth being precise about:
- The sub account is its own onchain address. It is not simply a nickname for your main wallet, and it does not automatically hold your main wallet's tokens.
- Your main Smart Wallet is typically set as an owner of the sub account, which is how you keep ultimate control over it even though the app is the one driving day to day activity.
- Because it is a separate account, a sub account can be scoped to a single app. Activity in one app's sub account does not reach into another app's sub account or into your main wallet, except through whatever permission you explicitly grant.
In practice, this means a sub account is less like a master key and more like a limited access card tied to one building.
How a sub account gets funded
A sub account with nothing in it cannot do much, so it needs a way to act on your behalf without being handed a copy of your main wallet. The common pattern is to pair a sub account with a spend permission, a related but separate feature covered in spend permissions and recurring payments on Base.
A spend permission lets you authorize a specific amount of a specific token, over a specific time window, that the sub account is allowed to pull from your main wallet. For example, you might approve a sub account to spend up to a small daily amount of USDC. The app can then act within that allowance without asking you to sign off on each individual transaction, while anything beyond the limit still requires your explicit approval.
Gas is often handled separately as well. Because many sub account transactions are small and frequent, apps frequently pair them with a paymaster, so the sub account's actions can be sponsored rather than requiring you to hold ETH in an account you may barely think about.
How this differs from session keys and regular approvals
If you have read about session keys and temporary wallet permissions, you might wonder how sub accounts are different. The short version is that they address overlapping problems in slightly different ways.
A session key is a temporary, scoped signing credential: a limited key that can act for your existing account during a defined window, then expires. A sub account is a different structure entirely: a new, separate onchain account that your main wallet owns and can revoke access to. Many real implementations combine both ideas with spend permissions, so the lines blur in practice, but the sub account itself is about account structure, while a session key is about signing authority.
It is also worth distinguishing a sub account from a token approval. An approval, which you can read about in how to check and revoke token approvals, gives a contract permission to move tokens that are already sitting in your wallet. A sub account is a different account altogether, with its own address and its own balance, that only reaches into your main wallet's funds through a spend permission you set.
What to actually check as a user
If an app on Base asks to set up this kind of account structure, a few questions are worth asking before you accept:
- What spend limit and token is being requested, and is it an amount you are comfortable an app repeatedly accessing without asking again.
- What time window applies. A permission that resets daily is different from one with no expiry.
- Whether the app's own interface gives you a way to see or revoke the sub account's permissions later, not just to grant them once.
None of this makes a sub account inherently risky. The isolation from your main wallet is, if anything, a safety improvement over handing an app a blanket approval. The part that deserves attention is the spend permission attached to it, since that is the actual door between the sub account and your funds.
Why this matters even if you never create one yourself
You do not need to use any particular app to benefit from understanding this. As account abstraction features spread across wallets built for Base, prompts referencing "sub accounts," "spend permissions," or "linked accounts" are becoming more common. Knowing that a sub account is a separate, limited account rather than a full extension of your main wallet makes it much easier to read those prompts correctly and decide, with real information, what to approve.