Account Abstraction Hits 40M Wallets: Why ERC-4337 + EIP-7702 Finally Killed Private Keys
For fifteen years, crypto's onboarding experience has been inexcusably broken. New users download a wallet, get bombarded with twelve random words they don't understand, discover they need ETH to do anything (but can't buy ETH without first having ETH for gas), and rage-quit before completing a single transaction. The industry called this "decentralization." Users called it hostile design.
Account abstraction—specifically ERC-4337 paired with Ethereum's May 2025 EIP-7702 upgrade—is finally fixing what should never have been broken. Over 40 million smart accounts have been deployed across Ethereum and Layer 2 networks, with nearly 20 million created in 2024 alone. The standard has enabled over 100 million UserOperations, marking a 10x increase from 2023. And with 87% of those transactions gas-sponsored by paymasters, we're witnessing the death of the "you need ETH to use Ethereum" paradox.
This isn't incremental improvement—it's the inflection point where crypto stops punishing users for not being cryptographers.
The 40 Million Smart Accounts Milestone: What Changed
Account abstraction isn't new—developers have discussed it since Ethereum's early days. What changed in 2024-2025 was deployment infrastructure, wallet support, and Layer 2 scaling that made smart accounts economically viable.
ERC-4337, finalized in March 2023, introduced a standardized way to implement smart contract wallets without changing Ethereum's core protocol. It works through UserOperations—pseudo-transactions bundled and submitted by specialized nodes called bundlers—that enable features impossible with traditional externally owned accounts (EOAs):
- Gasless transactions: Paymasters sponsor gas fees, removing the ETH bootstrapping problem
- Batch transactions: Bundle multiple operations into one, reducing costs and clicks
- Social recovery: Recover accounts through trusted contacts instead of seed phrases
- Session keys: Grant temporary permissions to apps without exposing master keys
- Programmable security: Custom validation logic, spending limits, fraud detection
The 40 million deployment milestone represents 7x year-over-year growth. Nearly half of those accounts were created in 2024, accelerating through 2025 as major wallets and Layer 2s adopted ERC-4337 infrastructure.
Base, Polygon, and Optimism lead adoption. Base's integration with Coinbase Wallet enabled gasless onboarding for millions of users. Polygon's strong gaming ecosystem leverages smart accounts for in-game economies without requiring players to manage private keys. Optimism's OP Stack standardization helped smaller L2s adopt account abstraction without custom implementations.
But the real catalyst was EIP-7702, which activated with Ethereum's Pectra upgrade on May 7, 2025.
EIP-7702: How to Upgrade 300 Million Existing Wallets
ERC-4337 smart accounts are powerful, but they're new accounts. If you've used Ethereum since 2015, your assets sit in an EOA—a simple key-value pair where the private key controls everything. Migrating those assets to a smart account requires transactions, gas fees, and risk of errors. For most users, that friction was too high.
EIP-7702 solved this by letting existing EOAs temporarily execute smart contract code during transactions. It introduces a new transaction type (0x04) where an EOA can attach executable bytecode without permanently becoming a contract.
Here's how it works: An EOA owner signs a "delegation designator"—an address containing executable code their account temporarily adopts. During that transaction, the EOA gains smart contract capabilities: batch operations, gas sponsorship, custom validation logic. After the transaction completes, the EOA returns to its original state, but the infrastructure now recognizes it as account-abstraction-compatible.
This means 300+ million existing Ethereum addresses can gain smart account features without migrating assets or deploying new contracts. Wallets like MetaMask, Trust Wallet, and Ambire can upgrade user accounts transparently, enabling:
- Gasless onboarding: Apps sponsor gas for new users, removing the ETH paradox
- Transaction batching: Approve and swap tokens in one click instead of two transactions
- Delegation to alternative key schemes: Use Face ID, passkeys, or hardware wallets as primary authentication
Major wallets implemented EIP-7702 support within weeks of the Pectra upgrade. Ambire and Trust Wallet rolled out support immediately, making their users' EOAs account-abstraction-ready without manual migration. This wasn't just a feature upgrade—it was retrofitting the entire installed base of Ethereum users with modern UX.
The combination of ERC-4337 (new smart accounts) and EIP-7702 (upgraded existing accounts) creates a path to 200 million+ smart accounts by late 2025, as industry projections estimate. That's not hype—it's the natural result of removing onboarding friction that crypto imposed on itself for no good reason.
100 Million UserOperations: The Real Adoption Metric
Smart account deployments are a vanity metric if nobody uses them. UserOperations—the transaction-like bundles that ERC-4337 smart accounts submit—tell the real story.
The ERC-4337 standard has enabled over 100 million UserOperations, up from 8.3 million in 2023. That's a 12x increase in just one year, driven primarily by gaming, DeFi, and gasless onboarding flows.
87% of those UserOperations were gas-sponsored by paymasters—smart contracts that pay transaction fees on behalf of users. This is the killer feature. Instead of forcing users to acquire ETH before interacting with your app, developers can sponsor gas and onboard users instantly. The cost? A few cents per transaction. The benefit? Eliminating the number-one friction point in crypto onboarding.
Paymasters work in three modes:
- Full sponsorship: The app pays all gas fees. Used for onboarding, referrals, or promotional campaigns.
- ERC-20 payment: Users pay gas in USDC, DAI, or app-native tokens instead of ETH. Common in gaming where players earn tokens but don't hold ETH.
- Conditional sponsorship: Gas fees sponsored if certain conditions are met (e.g., first transaction, transaction value exceeds threshold, user referred by existing member).
The practical impact: a new user can go from signup to first transaction in under 60 seconds without touching a centralized exchange, without downloading multiple wallets, and without understanding gas fees. They sign up with email and password (or social auth), and the app sponsors their first transactions. By the time they need to understand wallets and keys, they're already using the app and experiencing value.
This is how Web2 apps work. This is how crypto should have always worked.
Gasless Transactions: The Death of the ETH Bootstrapping Problem
The "you need ETH to use Ethereum" problem has been crypto's most embarrassing UX failure. Imagine telling users of a new app: "Before you can try this, you need to go to a separate service, verify your identity, buy the network's currency, then transfer it to this app. Also, if you run out of that currency, none of your other funds work."
Paymasters ended this absurdity. Developers can now onboard users who have zero ETH, sponsor their first transactions, and let them interact with DeFi, gaming, or social apps immediately. Once users gain familiarity, they can transition to self-custody and managing gas themselves, but the
initial experience doesn't punish newcomers for not understanding blockchain internals.
Circle's Paymaster is a prime example. It allows applications to sponsor gas fees for users paying in USDC. A user with USDC in their wallet can transact on Ethereum or Layer 2s without ever acquiring ETH. The paymaster converts USDC to cover gas in the background, invisible to the user. For stablecoin-first apps (remittances, payments, savings), this removes the mental overhead of managing a volatile gas token.
Base's paymaster infrastructure enabled Coinbase to onboard millions of users to DeFi without crypto complexity. Coinbase Wallet defaults to Base, sponsors initial transactions, and lets users interact with apps like Uniswap or Aave before understanding what gas is. By the time users need to buy ETH, they're already experiencing value and have context for why the system works the way it does.
Gaming platforms like Immutable X and Treasure DAO use paymasters to subsidize player transactions. In-game actions—minting items, trading on marketplaces, claiming rewards—happen instantly without interrupting gameplay to approve gas transactions. Players earn tokens through gameplay, which they can later use for gas or trade, but the initial experience is frictionless.
The result: tens of millions of dollars in gas fees sponsored by applications in 2024-2025. That's not charity—it's customer acquisition cost. Apps have decided that paying $0.02-0.10 per transaction to onboard users is cheaper and more effective than forcing users to navigate centralized exchanges first.
Batch Transactions: One Click, Multiple Actions
One of the most frustrating aspects of traditional Ethereum UX is the need to approve every action separately. Want to swap USDC for ETH on Uniswap? That's two transactions: one to approve Uniswap to spend your USDC, another to execute the swap. Each transaction requires a wallet popup, gas fee confirmation, and block confirmation time. For new users, this feels like the app is broken. For experienced users, it's just annoying.
ERC-4337 and EIP-7702 enable transaction batching, where multiple operations bundle into a single UserOperation. That same Uniswap swap becomes one click, one confirmation, one gas fee. The smart account internally executes approval and swap sequentially, but the user only sees a single transaction.
The use cases extend far beyond DeFi:
- NFT minting: Approve USDC, mint NFT, and list on marketplace in one transaction
- Gaming: Claim rewards, upgrade items, and stake tokens simultaneously
- DAO governance: Vote on multiple proposals in a single transaction instead of paying gas for each
- Social apps: Post content, tip creators, and follow accounts without per-action confirmations
This isn't just UX polish—it fundamentally changes how users interact with on-chain applications. Complex multi-step flows that previously felt clunky and expensive now feel instant and cohesive. The difference between "this app is complicated" and "this app just works" often comes down to batching.
Social Recovery: The End of Seed Phrase Anxiety
Ask any non-crypto-native user what they fear most about self-custody, and the answer is invariably: "What if I lose my seed phrase?" Seed phrases are secure in theory but catastrophic in practice. Users write them on paper (easily lost or damaged), store them in password managers (single point of failure), or don't back them up at all (guaranteed loss on device failure).
Social recovery flips the model. Instead of a 12-word mnemonic as the sole recovery method, smart accounts let users designate trusted "guardians"—friends, family, or even hardware devices—who can collectively restore access if the primary key is lost.
Here's how it works: A user sets up their smart account and designates three guardians (could be any number and threshold, e.g., 2-of-3, 3-of-5). Each guardian holds a recovery shard—a partial key that, on its own, can't access the account. If the user loses their primary key, they contact guardians and request recovery. Once the threshold is met (e.g., 2 out of 3 guardians approve), the smart account's access is transferred to a new key controlled by the user.
Argent pioneered this model in 2019. By 2025, Argent has enabled social recovery for hundreds of thousands of users, with recovery success rates exceeding 95% for users who lose devices. The mental shift is significant: instead of "I need to protect this seed phrase forever or lose everything," it becomes "I need to maintain relationships with people I trust, which I'm already doing."
Ambire Wallet took a hybrid approach, combining email/password authentication with optional social recovery for high-value accounts. Users who prefer simplicity can rely on email-based recovery (with encrypted key shards stored across servers). Power users can layer social recovery on top for additional security.
The criticism: social recovery isn't purely trustless—it requires trusting guardians not to collude. Fair enough. But for most users, trusting three friends is far more practical than trusting themselves to never lose a piece of paper. Crypto's maximalist stance on "pure self-custody" has made the ecosystem unusable for 99% of humanity. Social recovery is a pragmatic compromise that enables onboarding without sacrificing security in realistic threat models.
Session Keys: Delegated Permissions Without Exposure
Traditional EOAs are all-or-nothing: if an app has your private key, it can drain your entire wallet. This creates a dilemma for interactive applications (games, social apps, automated trading bots) that need frequent transaction signing without constant user intervention.
Session keys solve this by granting temporary, limited permissions to apps. A smart account owner can create a session key that's valid for a specific duration (e.g., 24 hours) and only for specific actions (e.g., trading on Uniswap, minting NFTs, posting to a social app). The app holds the session key, can execute transactions within those constraints, but can't access the account's full funds or perform unauthorized actions.
Use cases exploding in 2025-2026:
-
Gaming: Players grant session keys to game clients, enabling instant in-game transactions (claiming loot, trading items, upgrading characters) without wallet popups every 30 seconds. The session key is scoped to game-related contracts and expires after the session ends.
-
Trading bots: DeFi users create session keys for automated trading strategies. The bot can execute trades, rebalance portfolios, and claim yields, but can't withdraw funds or interact with contracts outside the whitelist.
-
Social apps: Decentralized Twitter/Reddit alternatives use session keys to let users post, comment, and tip without approving each action. The session key is limited to social contract interactions and has a spending cap for tips.
The security model is time-boxed, scope-limited permissions—exactly how OAuth works for Web2 apps. Instead of giving an app full account access, you grant specific permissions for a limited time. If the app is compromised or behaves maliciously, the worst-case damage is contained to the session key's scope and duration.
This is the UX expectation users bring from Web2. The fact that crypto didn't have this for 15 years is inexcusable, and account abstraction is finally fixing it.
Base, Polygon, Optimism: Where 40M Smart Accounts Actually Live
The 40 million smart account deployments aren't evenly distributed—they concentrate on Layer 2s where gas fees are low enough to make account abstraction economically viable.
Base leads adoption, leveraging Coinbase's distribution to onboard retail users at scale. Coinbase Wallet defaults to Base for new users, with smart accounts created transparently. Most users don't even realize they're using a smart account—they sign up with email, start transacting, and experience gasless onboarding without understanding the underlying tech. That's the goal. Crypto shouldn't require users to understand Merkle trees and elliptic curves before they can try an app.
Base's gaming ecosystem benefits heavily from account abstraction. Games built on Base use session keys to enable frictionless gameplay, batch transactions to reduce in-game action latency, and paymasters to subsidize player onboarding. The result: players with zero crypto experience can start playing Web3 games without noticing they're on a blockchain.
Polygon had early momentum with gaming and NFT platforms adopting ERC-4337. Polygon's low fees (often <$0.01 per transaction) make paymaster-sponsored gas economically sustainable. Projects like Aavegotchi, Decentraland, and The Sandbox use smart accounts to remove friction for users who want to interact with virtual worlds, not manage wallets.
Polygon also partnered with major brands (Starbucks Odyssey, Reddit Collectible Avatars, Nike .SWOOSH) to onboard millions of non-crypto users. These users don't see wallets, seed phrases, or gas fees—they see gamified loyalty programs and digital collectibles. Under the hood, they're using account-abstraction-enabled smart accounts.
Optimism's OP Stack standardization made account abstraction portable across rollups. Any OP Stack chain can inherit Optimism's ERC-4337 infrastructure without custom implementation. This created a network effect: developers build account-abstraction-enabled apps once, deploy across Base, Optimism, and other OP Stack chains with minimal modifications.
Optimism's focus on public goods funding also incentivized wallet developers to adopt account abstraction. Retroactive Public Goods Funding (RPGF) rounds explicitly rewarded projects improving Ethereum UX, with account abstraction wallets receiving significant allocations.
The pattern: low fees + distribution channels + developer tooling = adoption. Smart accounts didn't take off on Ethereum mainnet because $5-50 gas fees make paymaster sponsorship prohibitively expensive. They took off on L2s where per-transaction costs dropped to cents, making gasless onboarding economically viable.
The 200 Million Smart Account Endgame
Industry projections estimate over 200 million smart accounts by late 2025, driven by ERC-4337 adoption and EIP-7702 retrofitting existing EOAs. That's not moonshot speculation—it's the natural result of removing artificial friction.
The path to 200 million:
1. Mobile wallet adoption. Ambire Mobile, Trust Wallet, and MetaMask Mobile now support account abstraction, bringing smart account features to billions of smartphone users. Mobile is where the next wave of crypto adoption happens, and mobile UX can't tolerate seed phrase management or per-transaction gas confirmations.
2. Gaming onboarding. Web3 games are the highest-volume use case for account abstraction. Free-to-play games with play-to-earn mechanics can onboard millions of players, sponsor initial transactions, and enable frictionless gameplay. If 10-20 major games adopt account abstraction in 2025-2026, that's 50-100 million users.
3. Enterprise applications. Companies like Circle, Stripe, and PayPal are integrating blockchain payments but won't subject customers to seed phrase management. Account abstraction enables enterprise apps to offer blockchain-based services with Web2-grade UX.
4. Social apps. Decentralized social platforms (Farcaster, Lens, Friend.tech) need frictionless onboarding to compete with Twitter and Instagram. Nobody will use decentralized Twitter if every post requires a wallet approval. Session keys and paymasters make decentralized social apps viable.
5. EIP-7702 retrofit. 300+ million existing Ethereum EOAs can gain smart account features without migration. If just 20-30% of those accounts adopt EIP-7702 features, that's 60-90 million accounts upgraded.
The inflection point: when smart accounts become the default, not the exception. Once major wallets (MetaMask, Trust Wallet, Coinbase Wallet) create smart accounts by default for new users, the installed base shifts rapidly. EOAs become legacy infrastructure, maintained for compatibility but no longer the primary user experience.
Why BlockEden.xyz Builders Should Care
If you're building on Ethereum or Layer 2, account abstraction isn't optional infrastructure—it's table stakes for competitive UX. Users expect gasless onboarding, batch transactions, and social recovery because that's how Web2 apps work and how modern crypto apps should work.
For developers, implementing account abstraction means:
Choosing the right infrastructure: Use ERC-4337 bundlers and paymaster services (Alchemy, Pimlico, Stackup, Biconomy) rather than building from scratch. The protocol is standardized, tooling is mature, and reinventing the wheel wastes time.
Designing onboarding flows that hide complexity: Don't show users seed phrases on signup. Don't ask for gas fee approvals before they've experienced value. Sponsor initial transactions, use session keys for repeat interactions, and introduce advanced features gradually.
Supporting social recovery: Offer email-based recovery for casual users, social recovery for those who want it, and seed phrase backup for power users who demand full control. Different users have different threat models—your wallet should accommodate all of them.
Account abstraction is the infrastructure that makes your app accessible to the next billion users. If your onboarding flow still requires users to buy ETH before trying your product, you're competing with one hand tied behind your back.
For developers building applications with account abstraction, BlockEden.xyz provides the RPC infrastructure to support smart accounts at scale. Whether you're implementing ERC-4337 UserOperations, integrating paymaster services, or deploying on Base, Polygon, or Optimism, our APIs handle the throughput and reliability demands of production account abstraction. Explore our API marketplace to build the next generation of crypto UX.
Sources
- ERC-4337 Documentation
- What is ERC-4337? | Alchemy
- EIP-7702 Implementation Guide | QuickNode
- Ethereum Pectra Upgrade Overview | Alchemy
- Pectra Upgrade & EIP-7702 Give EOAs Smart Wallet Superpowers | Circle
- What are Paymasters? (ERC-4337) | Alchemy
- Gasless transactions with paymaster | Base Documentation
- What is Account Abstraction? | Ambire Blog
- Why Account Abstraction Will Fix Crypto's Biggest Problem | Medium