Account Abstraction
Letting a user's account be a programmable contract, so rules such as spending limits or social recovery replace a single private key.
An ordinary account is controlled by exactly one key and must hold the network's fee asset to do anything, which is why a new user with tokens but no gas can be stuck. A smart account defines its own validation logic instead, so it can require several signers, accept a passkey held in a phone's secure element, grant a temporary session key to a game, enforce daily limits, or appoint guardians who can help restore access. ERC-4337 delivers this without changing Ethereum itself, using a separate pool of user operations, bundlers who submit them, and paymasters that can sponsor fees or accept payment in another token; EIP-7702 lets an ordinary account temporarily execute contract code so existing addresses can use the same features. The aim is to end the situation where one written phrase is the only thing between a user and permanent loss.
In practice
A paymaster can cover the fee for a user's first transaction, so someone holding only a token can transact without first acquiring the network's fee asset.
The common misunderstanding
Account abstraction does not remove key management; it distributes control across keys and rules, and a poorly configured recovery setup can still lose everything.