Skip to main content

This site is for educational purposes only. Nothing here constitutes financial advice.

Topic 40 of 189

Account Abstraction (ERC-4337)

How ERC-4337 brings smart-contract wallets, social recovery, gasless transactions, and arbitrary signature schemes to Ethereum without changing the protocol — and why every wallet UX of the next decade will use it.

Beginner
8 min readUpdated November 2026Block Clarity Hub Editorial Team

The basics

What's Wrong With Regular Wallets

A regular Ethereum wallet (technically: an Externally Owned Account, or EOA) is just a private key and the address derived from it. If you lose the key, your funds are gone forever — no recovery, no password reset, nothing. You also have to pay gas fees in ETH, which means new users need to acquire ETH before they can do anything. And every signature must use ECDSA on the secp256k1 curve, period. These constraints have been the source of much of Ethereum's user-experience pain for a decade.

What ERC-4337 Changes

ERC-4337 is a standard that lets users have 'smart contract wallets' instead of EOAs. Instead of one private key controlling everything, the wallet is a small contract you control, and that contract can have any logic you want — multiple signers, social recovery, daily spending limits, payment in tokens other than ETH, biometric authentication, anything. And it works on Ethereum and every EVM chain without any protocol change, because the magic is in a separate mempool called the 'bundler network.'

Why You'll Encounter It

Wallet projects including Safe and Ambire support ERC-4337 smart accounts. If you've used 'pay gas in USDC' or 'social recovery' or 'one-tap sign in with passkey,' you've used 4337 under the hood. Expect this to spread across the entire wallet ecosystem over the next few years.

  • Old way (EOA): one private key controls everything; lose it, lose your funds
  • New way (ERC-4337): a smart-contract wallet you fully control, with any auth logic you want
  • Works on Ethereum and every EVM chain with no protocol change
  • Enables: social recovery, multi-sig, biometric / passkey auth, paying gas in tokens other than ETH

Key Takeaways

  • ERC-4337 brings smart-contract wallets to Ethereum without any protocol changes
  • Smart-contract wallets enable features that have been UX wishlist for a decade
  • Major wallets are shipping it now; the standard is gaining wide adoption
  • If you've used social recovery, passkey login, or gas-in-USDC, you've used 4337

Going deeper

The 4337 Architecture

ERC-4337 introduces three new pieces. UserOperations are a new transaction-like object that users sign and submit. Bundlers are off-chain actors who collect UserOperations from a separate mempool and bundle them into a single Ethereum transaction. The EntryPoint contract is a singleton smart contract that processes bundled UserOps, calls the user's wallet contract, and enforces the rules. The flow is: user signs a UserOp → bundler picks it up → bundler submits to EntryPoint → EntryPoint calls the user's wallet → wallet executes.

Paymasters and Gas Abstraction

A paymaster is a smart contract that can pay gas on behalf of UserOps. This is what enables 'gasless' transactions (sponsored by dapps), gas-in-tokens (the paymaster accepts USDC and pays the ETH gas itself), and subscription models. Paymasters integrate into the 4337 flow at the EntryPoint stage — the paymaster's `validatePaymasterUserOp` runs before execution to decide whether to sponsor the transaction.

Signature Abstraction

Because the user's wallet is a contract, it can verify any signature scheme it wants — not just secp256k1 ECDSA. This means passkeys (WebAuthn) on the secp256r1 curve, BLS signatures, multi-sig schemes, threshold signatures, hardware-backed keys — all become first-class auth options. Coinbase Smart Wallet uses passkeys via WebAuthn; users sign with Face ID or Touch ID rather than typing a seed phrase, and there's no seed phrase to lose.

The EntryPoint Is Audited Public Infrastructure

The EntryPoint contract is deployed at the same address on most EVM chains (0x5FF1...2789 for v0.6, with v0.7 released in 2024 and v0.8 in 2025). It's been extensively audited and is treated as part of the standard. Wallets and paymasters interact with it; users don't directly call it. This singleton design is part of why 4337 has spread so quickly.

Key Takeaways

  • Three new pieces: UserOperations, Bundlers, and the EntryPoint contract
  • Paymasters enable gasless tx, gas-in-tokens, and sponsored UX
  • Signature abstraction enables passkeys, biometrics, BLS, threshold, hardware-backed keys
  • The EntryPoint is a singleton deployed at the same address across most EVM chains

Under the hood

Bundler Economics and DOS Defence

Bundlers pay gas for the bundled Ethereum transaction up front and recover it from the UserOp's bundled value. If a UserOp's validation passes but its execution reverts after the bundler has paid, the bundler loses money. ERC-4337 defines a strict validation regime — only certain opcodes are allowed during validation, time-locked storage access is restricted, and the system uses reputation tracking to penalise bundlers and paymasters that submit failing operations. This is a delicate economic design that took multiple revisions to stabilise.

EIP-7702: The EOA-Compatible Cousin

ERC-4337 doesn't migrate existing EOAs — users have to create a new smart-contract wallet. EIP-7702 (in the Pectra upgrade, May 2025) takes a different approach: it lets an existing EOA set a delegation to a smart-contract wallet's code, which stays in place until the account replaces or clears it. This means an existing user can opt into smart-wallet features (bundling, sponsorship, batched operations) without migrating their address. EIP-7702 and ERC-4337 are complementary, not competing.

Cross-Chain Sessions and Stealth Addresses

Smart-contract wallets enable session-key patterns — temporary keys with limited authority (e.g., 'this dapp can sign transactions under $10 for 24 hours without prompting'). Game and high-frequency-trading UX is being rebuilt around this. They also compose well with stealth-address standards (ERC-5564) where each interaction uses a different observable address, improving privacy. These are advanced patterns enabled by the architecture but not standardised in 4337 itself.

Real Adoption Numbers

As of November 2026, the community BundleBear dashboard (built by 0xKofi) reports about 1.36 billion cumulative ERC-4337 UserOps across the chains it tracks. Dashboards such as BundleBear and Dune track UserOp counts by chain and app; the standard's EntryPoint has been live on Ethereum mainnet since March 2023.

Smart Wallets Are More Powerful and More Complex

A smart-contract wallet is itself a contract that could have bugs. The code that runs your auth logic must be audited; the social-recovery mechanism must be designed carefully to avoid being a backdoor. The leading 4337 wallet codebases (Safe, Coinbase Smart Wallet) are heavily audited, but custom or off-the-shelf 4337 wallets are an attack surface. Use established implementations.

Key Takeaways

  • Strict validation rules + reputation tracking protect bundler economics from DOS
  • EIP-7702 (Pectra, May 2025) brings smart-wallet features to existing EOAs without migration
  • Session keys and stealth addresses are powerful patterns enabled by the architecture
  • Public dashboards such as BundleBear track ERC-4337 adoption by chain and app
  • Use established 4337 wallet codebases; custom implementations are an attack surface

Related Content

AI Meets Crypto: What's Real, What's Hype

Where artificial intelligence and cryptocurrency actually intersect — AI agents with wallets, decentralized compute, verifiable inference, and the new scam vectors AI creates.

Bitcoin ETFs & Institutional Crypto

How spot Bitcoin ETFs work, what institutional adoption means for the market, and why owning ETF shares is fundamentally different from owning the coin.

UTXO vs Account Model

How Bitcoin's UTXO model differs from Ethereum's account model — what each gets right, what each makes harder, and why the choice shapes everything from parallelism to replay protection.

EIP-4844 and Proto-Danksharding

How Ethereum's March 2024 Dencun upgrade introduced blob space — a new transaction type that cut rollup data costs by ~10x and set the stage for full danksharding.

Data Availability Sampling

How light nodes can be cryptographically confident that a block's full data was published — without downloading it — and why this is the key unlock for Ethereum's full danksharding and the modular blockchain stack.

Finality and Fork Handling

What it means for a transaction to be 'final,' why different chains finalise differently, how reorgs happen, and the MEV incentives that complicate the picture.

State Pruning and Expiry

Why Ethereum's node storage needs have grown to terabytes, what 'archive,' 'full,' and 'light' nodes actually store, and how proposals like EIP-4444 and new state-tree designs (verkle or binary) aim to keep node hardware accessible for years to come.

ECDSA vs EdDSA vs BLS

The three signature schemes you'll meet across the crypto stack — what each does well, what tradeoffs they impose, and why Ethereum uses three of them simultaneously.

References & further reading