Account abstraction makes blockchain accounts programmable. On Ethereum, a normal account (an externally owned account, EOA) is controlled by a single private key: lose the key and you lose the funds, and every transaction must be signed by that key and paid for in ETH. With account abstraction, the account is a smart contract wallet (smart account) whose rules you define in code: who may sign, how, which limits apply and who pays the gas. On Ethereum and other EVM chains, account abstraction is mainly implemented through the ERC-4337 standard.
How does ERC-4337 work?
- UserOperation: instead of a normal transaction, the user's wallet creates a UserOperation, a description of what the account should do, signed according to the account's own rules.
- Alternative mempool: UserOperations are sent to a separate mempool, not to the normal transaction pool.
- Bundler: a service that collects UserOperations, checks them, and submits them in one transaction to the blockchain.
- EntryPoint contract: a shared, audited contract that validates and executes each UserOperation via the user's smart account.
- Paymaster (optional): a contract that pays the gas on behalf of the user, or accepts payment in another token.
ERC-4337 needed no change to the Ethereum protocol itself, which is why it could be adopted quickly. Since the Pectra upgrade in 2025, EIP-7702 also lets existing EOAs temporarily use smart account code, which complements ERC-4337. Some networks, such as zkSync and Starknet, have account abstraction built into the protocol (native account abstraction).
Want users to transact without holding gas? See gasless transactions for every method, from paymaster sponsorship and EIP-7702 to relayers and permit signatures.
What does account abstraction make possible?
- Gasless transactions: the app pays the gas, so new users don't need ETH first.
- Gas in other tokens: users pay transaction costs in stablecoins or other ERC-20 tokens.
- Batching: several actions, such as approve and swap, in one confirmation.
- Session keys: temporary, limited keys so games and trading apps don't ask for a signature for every action.
- Social recovery and multisig: regain access through trusted guardians, or require several signers.
- Passkeys and other signing methods: sign with a phone's fingerprint or face recognition instead of a seed phrase.
When is account abstraction worth it?
Account abstraction removes the biggest barriers for mainstream users: seed phrases, needing ETH for gas, and endless signing prompts. It is especially valuable for consumer apps, games, loyalty programmes, payments and any product where users shouldn't have to understand crypto first. The trade-offs are extra infrastructure (bundlers, paymasters), slightly higher gas costs per operation and the security of the smart account code itself. See our account abstraction services, ERC-4337 implementation and smart account development.
Frequently Asked Questions about Account Abstraction
What is the difference between an EOA and a smart account?
An EOA is controlled by one private key and has fixed rules. A smart account is a smart contract whose rules for signing, limits, recovery and gas payment are programmable.
Is ERC-4337 the same as account abstraction?
ERC-4337 is the most widely used standard for account abstraction on Ethereum and EVM chains. Account abstraction is the broader concept, which can also be built into a protocol natively.
Are smart accounts secure?
They can be more secure than a single private key, thanks to recovery and multisig, but the smart account code must be audited. Most projects build on established, audited account implementations rather than writing their own.
Do users need ETH to use a smart account?
Not if a paymaster sponsors the gas or accepts another token. That is one of the main reasons to use account abstraction.