Account abstraction makes blockchain accounts programmable. Instead of one private key that controls everything and must pay gas in the chain's own token, a smart account can follow rules you define: log in with a passkey, let the application pay gas, batch several actions into one confirmation, set spending limits, or recover access without a seed phrase. For products aimed at people who are not crypto natives, it removes most of the friction. New to the concept? Read what is account abstraction.
Three Routes to Account Abstraction
- ERC-4337: smart accounts with UserOperations, bundlers and paymasters, without changes to the protocol. Available on Ethereum and most EVM chains.
- EIP-7702: since the Pectra upgrade, an existing key-based account can delegate to smart account code, so users keep their address and gain smart account features.
- Native account abstraction on chains such as zkSync and Starknet, where every account is a smart account by design. See zkSync development.
What You Can Build With It
- Gasless onboarding: new users transact without buying ETH first, see gasless transactions.
- Login without seed phrases: passkeys, email or social login as signers, with recovery options.
- One-click flows: approve and swap, or mint and list, as one batched action.
- Session keys for games, trading and automation, limited in time, contracts and amounts. See session keys.
- Team and treasury accounts with roles, limits and multiple approvers. See smart accounts.
How We Approach It
We start from the user flow you want and choose the simplest route that delivers it: an existing audited smart account with modules where possible, custom logic in Solidity only where needed. Bundler and paymaster infrastructure is either a provider or self-hosted, depending on cost, control and the chains you use. Signatures follow EIP-712 so users can see what they approve.
Frequently Asked Questions
Do users need a new wallet?
Not necessarily. With ERC-4337 they get a smart account that their existing key or a passkey controls; with EIP-7702 they can upgrade their current address.
Who pays for the gas?
That is your choice: the user, your application through a paymaster, or the user in a token such as USDC.
Is account abstraction secure?
Smart accounts add code, and code needs care: audited account implementations, limited permissions and thorough testing. Done well, they are often safer than a single key.
Who owns the code?
Ownership of the source code is set out in the contract, and the code can be fully yours, including documentation and tests.
Make Your dApp Easy to Use
Tell us where users drop off today. We will design an account setup that removes those steps.
Book a free call about account abstraction
ERC-4337 Account Abstraction: Explained and Implemented
What is ERC-4337? Account abstraction without protocol changes: UserOperations, EntryPoint, bundlers and paymasters explained, and how we implement it.
ERC-4337 Bundler Development and Integration
ERC-4337 bundlers explained and built: how bundlers process UserOperations, provider versus self-hosted, validation rules, gas strategy and monitoring.
Session Keys for Smart Accounts: Scoped, Temporary Access
Session keys explained and implemented: temporary keys with limited permissions for games, trading and automation, enforced on-chain by smart accounts.
Smart Account Development: Smart Wallets With Passkeys
Smart account development: contract wallets with passkeys, recovery, batching, spending limits and modules, built on Safe, Kernel or custom implementations.