Best account-abstraction wallets, ranked by the job you need done
"Account abstraction" now covers a passkey wallet on your phone, a multisig treasury, a developer SDK, and a one-line upgrade to the MetaMask address you already own.
The useful question is what the wallet lets you delegate, to whom, and how you take it back. That is the property that separates account-abstraction wallets from ordinary ones. A normal address has one key that can do everything. A smart account can grant a narrower permission: this app may trade, for this long, with this much, and nothing else.
This page ranks account-abstraction wallets by four jobs, explains the two standards underneath them, and ends with the checks that matter if the reason you want one is to let a strategy trade for you.
Key takeaways
- Two standards, one idea. ERC-4337 deploys a smart contract as your account. EIP-7702 lets an existing address borrow smart-account behaviour without moving funds.
- The feature that matters is scoped permission with revocation. Gas sponsorship and passkeys are conveniences; session keys are the reason to switch.
- Pick by job: everyday self-custody, upgrading an address you already use, running a team treasury, or delegating execution to an agent.
- Key export is the custody test. If you cannot take the key with you, you depend on the provider to reach your funds.
The two standards in one paragraph each
ERC-4337 puts your account in a smart contract. Instead of signing transactions with one private key, you submit "user operations" that the contract validates according to its own rules: a passkey, a multisig threshold, a session key with a spending limit. Bundlers submit them to the chain and paymasters can sponsor gas. The account is a contract, so it can be upgraded, extended with modules, and made to enforce policy.
EIP-7702, live on Ethereum since the Pectra upgrade in 2025, lets an ordinary address delegate its code to a smart-account implementation. Your address stays the same, your funds stay where they are, and the address gains batching, gas abstraction, and permission features. It is the path for people who do not want a new address.
Both standards deliver the capability this page cares about: a permission narrower than the whole key.
How the wallets compare
| Wallet | Standard | Best for | Session keys or scoped permissions | Key export |
|---|---|---|---|---|
| Coinbase Smart Wallet | ERC-4337, passkeys | Everyday self-custody without a seed phrase | Spend permissions and sub-accounts for apps | Passkey-based; no seed phrase to export |
| MetaMask Smart Accounts | EIP-7702 | Upgrading an address you already use | Delegations via the Delegation Framework | Yes, same key as before |
| Ambire | ERC-4337 and EIP-7702 | Power users who want gas abstraction and batching in an extension | Yes | Yes |
| Safe | ERC-4337-compatible multisig | Teams, DAOs, and anyone who wants a threshold | Via modules and roles | Signer keys remain yours |
| Ready (formerly Argent) | Native AA on Starknet; 4337 elsewhere | Mobile self-custody with guardians | Session keys on Starknet | Yes |
| Privy embedded + smart wallets | ERC-4337 (multiple implementations) | Apps that need to create wallets for users and delegate scoped actions | Yes, session keys | Yes, user-exportable |
| ZeroDev Kernel, Biconomy Nexus, Alchemy Modular Account | ERC-4337, ERC-7579 modular | Developers building their own wallet or agent stack | Yes, as modules | Developer-defined |
Where a cell says "yes", confirm the specifics in the wallet's current documentation. Permission features change quickly in this category.
1. For everyday self-custody: Coinbase Smart Wallet
Coinbase Smart Wallet removes the seed phrase. The account is an ERC-4337 contract controlled by a passkey stored on your device, so signing is a fingerprint or face scan, and recovery goes through your device's passkey sync rather than twelve words on paper.
Its permission features are aimed at apps: spend permissions let an app draw a capped amount over a period, and sub-accounts give an app its own scoped account under yours. That is the pattern that makes delegated trading possible without handing over the account.
Custody rests on the passkey and the device ecosystem that stores it. There is no seed phrase to export, which some people count as a feature and others as a dependency. Pick it if you want onchain apps without managing keys; skip it if you want a key you can move anywhere.
2. For upgrading an address you already use: MetaMask Smart Accounts
Most people who want account abstraction already have an address with history, approvals, and balances they do not want to migrate. MetaMask's smart-account upgrade uses EIP-7702 to give that address smart-account behaviour in place: transaction batching, gas paid in tokens or sponsored, and delegations.
Delegations are the relevant feature. MetaMask's Delegation Framework lets you grant another party a scoped permission, with caveats that bound what they can do and for how long, and revoke it. That is a session key by another name.
The trade-off is that 7702 delegates code to your address, so the security of the account is now the security of the implementation you delegated to, in addition to your key. Review what the upgrade points to. Choose it to keep your address and gain permission features; it is also open to the largest number of existing users.
3. For power users: Ambire
Ambire has shipped an account-abstraction wallet since before the standards settled, and now supports both ERC-4337 accounts and EIP-7702 upgrades from one extension. Gas abstraction, batching, and transaction simulation are built in rather than added.
It ranks here because it treats account abstraction as the default rather than a mode. The cost is that it is a smaller ecosystem than MetaMask or Coinbase, with fewer app integrations that assume it. If you want the full feature set today and are comfortable being on a less common wallet, it is the most complete option in an extension.
4. For teams and treasuries: Safe
Safe is the multisig smart account that most DAOs and onchain companies already run. Funds sit in a contract that requires a threshold of signers, and the account can be extended with modules that grant specific permissions to specific parties: a role that can rebalance but not withdraw, a spending allowance for an operator, a recovery path.
For delegated execution, Safe's roles and module system is the most mature. It is also the heaviest. Every action is a multisig flow unless a module says otherwise, and setting up modules correctly is real work. Use it when more than one person needs to control the funds. For a single owner, the multisig overhead buys little.
5. For mobile-first self-custody: Ready
Ready, the wallet formerly called Argent, built its reputation on native account abstraction on Starknet, where session keys and social recovery through guardians were available before Ethereum mainnet had a standard for them. It has since expanded across chains.
It ranks here because its mobile experience assumes account abstraction throughout, and its guardian model is a recovery path that does not depend on a seed phrase or a single device. The limitation is that the deepest feature set is on Starknet, and what you get elsewhere depends on the chain.
6. For apps that delegate to agents: Privy
Privy is not a consumer wallet; it is the infrastructure that apps use to create wallets for users and let those wallets delegate scoped actions. An app signs you in with email or a social login, Privy generates an embedded wallet whose key is split and controlled by you, and the app can pair it with an ERC-4337 smart wallet that supports session keys.
This is the architecture Deploy Finance runs. Sign in, get a wallet you control, and grant an agent a session key that can trade on whitelisted venues and cannot transfer or withdraw. The self-custody and session keys page explains the boundary, and key export shows that the key is yours to take.
It ranks here for one job only: when the reason you want account abstraction is to let a strategy act for you inside a specific app. It is not a wallet you download and use everywhere.
7. For developers: Kernel, Nexus, and Modular Account
ZeroDev's Kernel, Biconomy's Nexus, and Alchemy's Modular Account are ERC-4337 smart-account implementations built on the ERC-7579 modular standard. Permissions, session keys, recovery, and policies are modules you install rather than features you wait for.
If you are building an agent, a treasury tool, or a wallet product, these are where session keys with fine-grained policies live today. If you are not building anything, they are the layer underneath the wallets above rather than a choice you make directly.
The five checks before you delegate anything
If the reason you are reading this is that you want a strategy, a bot, or an agent to trade for you, the wallet choice reduces to five questions. The best wallets for automated strategies page compares architectures against them; here they are as a checklist.
- Can the permission be scoped? Which contracts, which actions, which amounts, for how long. A permission that can do anything is a key copy.
- Can it withdraw or transfer? If the delegate can move funds to another address, the scope is wrong for trading.
- Can you revoke it in one action, yourself? Not through support, not after a cooldown.
- Can you export the key? The wallet may be convenient; the key must be portable.
- What is the delegate whitelisted to touch? A trading permission that can call any contract is broader than it sounds.
Deploy Finance's review-permissions guide applies these to its own session keys. Apply them to anything else the same way.
Verdict
For a new user who wants onchain apps without a seed phrase, Coinbase Smart Wallet. For someone with an existing address, the MetaMask 7702 upgrade. For teams, Safe. For a mobile-first self-custody wallet with recovery, Ready. For a power user in an extension, Ambire. For an app that needs to delegate execution to an agent, the Privy pattern, which is what Deploy Finance uses.
Whichever you pick, the feature to test is scoped permission with one-click revocation and key export.
Learn more
- Best wallets for automated onchain strategies
- Self-custody and session keys
- Deploy Finance wallets
- How to export your keys
- ERC-4337 specification
- EIP-7702 specification
Start with Deploy Finance
Create a self-custodial Deploy Finance wallet and review the live agents.