Account Abstraction

In a standard EVM chain, every account is either an Externally Owned Account (a private key) or a smart contract. ERC-4337 introduces a third class: a smart-contract account that the user transacts as. Because the account is a contract, it can hold logic. That logic can sponsor gas, recover from a lost key via guardians, batch multiple calls into one transaction, or enforce custom auth rules like a daily spending cap.

The user experience implications are large. With AA, an end user can sign up with an email and a passkey instead of a seed phrase. Gas fees can be paid by the application or in the application’s token, not in ETH. The wallet can rate-limit suspicious transactions. The trade-off is increased on-chain complexity and higher gas cost per transaction.

Worked example: a consumer payments app wants non-crypto-native users. Without AA, onboarding means “write down these twelve words, lose them and your money is gone forever”, which kills the funnel. With AA, the user signs up with a passkey, the app sponsors the first transactions so they never see a gas fee, and a lost device recovers through guardians instead of a seed phrase. The same pattern lets the wallet enforce a daily spend cap on-chain, which is the kind of guarantee a centralised app could never make credibly.

The common founder mistake is treating AA as a checkbox. It changes the security model: social recovery removes the seed-phrase footgun for normal users but introduces guardian compromise as a new attack class, which is strictly worse for power users who would rather hold the key themselves. The honest trade-off is that AA buys mainstream UX at the cost of more contract code to audit and more gas per action. Wavect has shipped account-abstraction wallets and Snaps (MetaMask plugins) to production. The technology is real and increasingly mainstream. The implementation is non-trivial. If a vendor quotes AA as a cheap add-on, ask which infrastructure they are using and which security audits the contract code has been through. The same audit discipline that applies to zero-knowledge circuits applies here.