What is Account Abstraction (ERC-4337)?

Account abstraction allows programmable authorization and execution. ERC-4337 supplies UserOperations, bundlers, EntryPoint and optional paymasters above Ethereum consensus; it does not introduce a third protocol account type. EIP-7702 also lets an externally owned account (EOA) delegate execution to contract code. These mechanisms can work together, but chain, account and infrastructure support must match.

Passkeys, recovery, spending limits and sponsored fees are features of the chosen account implementation and services, not automatic ERC-4337 guarantees. A paymaster can cover network fees under its policy, but someone still pays. Deposits, sponsorship budgets, abuse controls and failure costs belong in the design. The ERC-4337 specification defines the infrastructure boundary.

Hypothetical example: a payments app chooses a passkey-capable account, a sponsor with a bounded budget and a recovery policy with a delay and cancellation path. Test a lost device, compromised guardian, exhausted sponsor deposit and unavailable bundler before promising the user can always recover or transact. Compare gas using the exact calls, account code and chain; batching can amortize work without guaranteeing lower fees.

Wavect has shipped account-abstraction wallets and MetaMask Snaps. Start with the production checklist and inspect a failing operation with the local UserOperation debugger. For a build, our account-abstraction development service covers the implementation. Security depends on validation, upgrade controls, recovery and dependencies, not the AA label.