Account Abstraction

Account abstraction is a design that lets a crypto account be controlled by smart contract code with its own rules for approving transactions, rather than by a single private key. On Ethereum, it is mainly implemented through the ERC-4337 standard for smart accounts.

A standard Ethereum account, an externally owned account (EOA), is controlled by one private key. The protocol treats a transaction as valid if it carries a correct signature from that key. Account abstraction instead lets the account be a smart contract that defines its own validation logic. ERC-4337 achieves this without changing Ethereum's core protocol. Users sign "UserOperations," which travel through a separate mempool. Bundlers package them and submit them to a shared EntryPoint contract, which checks and executes them.

Because the rules are code, a smart account can require several signers or set spending limits. It can also batch several actions, such as a token approval and a swap, into one step, or grant temporary session keys to an app. A third party called a paymaster can even cover gas fees. A common example is social recovery. An owner names five guardians, such as a hardware wallet, a friend and a relative, and any three of them can jointly approve replacing a lost signing key. This avoids a single seed phrase as the only line of defence.

A smart account is only as safe as its code and configuration. Bugs in the wallet contract can put funds at risk. Guardians who collude or are compromised could use recovery to take over the account. "Gasless" transactions are not free, because someone else pays the fee. A smart account deployed on one network also does not automatically exist on another, so funds sent to the same address on a different chain may not be accessible.

Learn more

Related terms