All Guides
InfrastructureEIP-4337Account Abstraction

EIP-4337: Account Abstraction Explained

How EIP-4337 works, what it enables for dApp UX, and the key concepts: UserOperations, Bundlers, EntryPoint, and Paymasters.

Updated March 25, 2026 8 min read

EIP-4337 (Account Abstraction) is the most important Ethereum UX improvement since MetaMask. It enables smart contract wallets to function as primary accounts — without requiring any changes to the consensus layer.

The Problem It Solves

Ethereum's standard accounts (EOAs) have fundamental limitations: users must always hold ETH for gas, every action requires a wallet signature and pop-up, private key loss means permanent loss of funds (no recovery), and multi-sig requires complex coordination. These UX issues are major barriers to mainstream adoption.

How EIP-4337 Works

Instead of standard transactions, users submit UserOperations — objects describing the action they want to take. Bundlers (specialized nodes) collect UserOperations, bundle them together, and submit them to a singleton EntryPoint contract on-chain. The EntryPoint validates each UserOperation, calls the user's smart account, and handles gas accounting.

Paymasters: Gasless Transactions

Paymasters are contracts that pay gas on behalf of users. A dApp can deploy a Paymaster that covers gas costs for its users — making transactions 'free' from the user's perspective. The dApp pays in the background. This completely changes onboarding: users can interact with your dApp without ever buying ETH for gas.

Session Keys

Smart accounts can grant session keys — temporary, scoped signing keys that allow specific actions without requiring a full wallet approval each time. A game can receive a session key that allows it to submit game actions for the next 24 hours. Users approve once and play without pop-ups. This is the pattern that makes Web3 gaming feel like Web2 gaming.

Social Recovery

Smart accounts can implement custom recovery logic. A 3-of-5 guardian recovery scheme lets users designate trusted contacts who can collectively recover access to a lost account. This eliminates the seed phrase problem — no single point of failure, no permanent loss from a lost private key.

Adoption Status in 2026

EIP-4337 is live on mainnet and all major L2s. Safe, Biconomy, ZeroDev, and Pimlico provide smart account SDKs. Coinbase Smart Wallet, Privy's embedded wallets, and Dynamic all use EIP-4337 under the hood. The infrastructure is production-ready. Adoption is accelerating in gaming and consumer apps — anywhere that wallet UX is a conversion bottleneck.

For Developers

Use ZeroDev, Biconomy's Nexus SDK, or Pimlico's permissionless.js for smart account integration. Implement paymasters if you want to cover gas for users. Add session keys for game-like interactions. Use Safe's infrastructure for institutional or high-value accounts. The Account Kit by Safe is the most feature-complete enterprise-grade implementation.

Ready to build your Web3 project?

Tell us about your project and get a precise quote.

Get a Project Quote