Tools/Explorers

Account Abstraction Wallets Compared: ERC-4337 Providers

Compare account abstraction wallet providers by gas sponsorship, social recovery, session keys, chain support, and pricing. Biconomy, Safe, ZeroDev, Alchemy, Pimlico, and Stackup.

Spark Team

Account Abstraction Provider Overview

Account abstraction replaces traditional externally owned accounts (EOAs) with smart contract wallets that can sponsor gas, batch transactions, enforce spending policies, and recover access without a seed phrase. The ERC-4337 standard, deployed on Ethereum mainnet in March 2023, introduced a permissionless infrastructure layer for these smart accounts: bundlers submit UserOperations on behalf of users, and paymasters can cover gas fees entirely.

Six providers dominate the ERC-4337 ecosystem: Biconomy, Safe, ZeroDev, Alchemy Account Kit, Pimlico, and Stackup. They differ in what they provide. Some ship full-stack SDKs with smart accounts, bundlers, and paymasters bundled together. Others are infrastructure-only, offering bundler and paymaster APIs that work with any compatible smart account. The table below summarizes each provider's role and core features.

ProviderTypeSmart AccountModule StandardBundlerPaymasterEIP-7702
BiconomyFull-stack SDKNexusERC-7579MEEVerifying + ERC-20Yes
SafeSmart account + modulesSafe (v1.4.1)ERC-7579 (via Safe7579)Third-partyThird-partyYes
ZeroDevFull-stack SDKKernelERC-7579Ultra RelayVerifyingYes
Alchemy Account KitFull-stack SDKModular Account v2ERC-6900Alchemy BundlerGas ManagerYes
PimlicoInfrastructureAccount-agnosticAnyAltoVerifying + ERC-20Yes
StackupInfrastructureAccount-agnosticAnyStackup BundlerVerifyingYes

For a broader comparison of wallet SDKs including non-AA options, see our embedded wallet comparison.

Smart Account Standards: ERC-7579 vs ERC-6900

The two competing standards for modular smart accounts determine how plugins, validators, and executors attach to a wallet contract. This choice affects which ecosystem of modules your account can use.

ERC-7579 defines a minimal interface for smart account modules: validators (who can sign), executors (what actions to run), and hooks (pre/post execution checks). Biconomy's Nexus, ZeroDev's Kernel, and Safe (via the Safe7579 adapter) all implement ERC-7579. This standard has the broadest adoption by account count, and Rhinestone maintains a growing registry of compatible modules.

ERC-6900, championed by Alchemy, adds more lifecycle hooks including runtime validation and pre/post-execution checks with richer plugin interfaces. Alchemy's Modular Account v2 is the primary implementation. ERC-6900 plugins can enforce session keys, cold storage rules, and multi-owner configurations through a single standard.

For a deeper technical overview of how these standards work within the ERC-4337 flow, see our research on ERC-4337 account abstraction.

Gas Sponsorship and Paymaster Models

Gas sponsorship is the primary reason most developers adopt account abstraction: users never see a gas prompt. Each provider handles sponsorship differently.

Biconomy's MEE infrastructure uses a single gas tank that covers every supported chain. Developers fund one balance in the dashboard, set sponsorship policies per project, and the MEE paymaster draws from that pool regardless of which chain the UserOperation targets. Biconomy also supports ERC-20 token payments, where users pay gas in stablecoins instead of ETH.

Alchemy's Gas Manager offers per-user spend caps and policy-based sponsorship configured in the dashboard. The developer gets a policy ID to pass into the SDK. Alchemy fronts the gas cost and adds it to the monthly bill, with credit card top-ups as usage grows.

ZeroDev includes a verifying paymaster in its managed infrastructure. Sponsorship is bundled into the platform pricing: the free tier covers basic usage, and paid tiers include higher UserOperation limits with paymaster access.

Pimlico offers two paymaster types: a verifying paymaster funded from a dashboard balance, and an ERC-20 paymaster that lets users pay gas in USDC, USDT, DAI, and other tokens on supported chains. Pimlico is account-agnostic, so it works with Safe, Kernel, Modular Account, or any ERC-4337 compliant wallet.

Safe and Stackup do not operate their own paymasters. Safe accounts use third-party paymasters from Pimlico, Alchemy, or ZeroDev. Stackup provides bundler infrastructure and has historically offered a verifying paymaster, though the company pivoted toward enterprise financial operations tooling in early 2025.

Session Keys and Delegated Authorization

Session keys allow a user to pre-authorize specific actions for a limited time or scope without signing each transaction individually. This is critical for gaming, trading bots, and subscription flows where repeated approval prompts would destroy the user experience.

ZeroDev's Kernel account was the first to ship native ERC-7579 session key support. The module separates validation from execution, so a single account can combine an ECDSA signer for high-value operations with a scoped session key for a specific dapp contract. Permissions can restrict which contracts, functions, and value limits the session key may access.

Biconomy co-developed the SmartSessions module with Rhinestone for ERC-7579 accounts. It supports action-specific policies and integrates with the ERC-7715 permission standard, allowing apps to request granular session key permissions from the user in a structured format.

Safe implements session-style delegation through its module system. Developers can install spending-limit modules, contract allowlist modules, and role-based access via Zodiac (by Gnosis Guild). These are not labeled "session keys" in Safe's terminology, but they achieve equivalent scoped authorization.

Alchemy's ERC-6900 framework supports session keys through its plugin architecture. Plugins can enforce time-bound permissions, function selectors, and spending caps through the Modular Account's pre-execution validation hooks.

Social Recovery Options

Social recovery lets account owners designate trusted guardians who can collectively restore access if the primary key is lost. This eliminates the single-point-of-failure problem inherent in seed phrases.

Safe's M-of-N multisig architecture is the most battle-tested recovery mechanism in the ecosystem, securing over $100 billion in assets across 44 million deployed accounts. Recovery works by rotating the owner set: guardians submit threshold-signed transactions to replace a lost signer with a new key.

ZeroDev and Biconomy both support recovery through ERC-7579 modules. The Rhinestone module registry includes recovery modules that can be installed on any ERC-7579 compatible account. ZK Email recovery, which lets guardians approve recovery via email without exposing their on-chain address, is an emerging option in the ERC-7579 module ecosystem.

Alchemy's Modular Account supports recovery through ERC-6900 plugins. The multi-owner plugin allows guardian-style configurations where multiple signers can collectively rotate the account owner.

For Bitcoin-native approaches to keyless recovery that differ from ERC-4337, see our research on seedless wallet recovery design.

Chain Support

Chain coverage varies dramatically. Infrastructure-only providers like Pimlico tend to support the most networks because they only need to run bundler and paymaster services, not deploy smart account factories. Full-stack SDKs must deploy and verify contracts on each chain.

ProviderChainsKey Networks
Biconomy50+ EVMEthereum, Arbitrum, Base, Optimism, Polygon, BSC, Avalanche
Safe15+ EVMEthereum, Arbitrum, Optimism, Base, Polygon, BSC, Gnosis, zkSync Era
ZeroDev30+ EVMEthereum, Arbitrum, Base, Optimism, Polygon, BSC, Avalanche
Alchemy Account Kit30+ EVMEthereum, Arbitrum, Optimism, Base, Polygon, BSC, Berachain
Pimlico100+ EVMBroadest coverage: all major L1s and L2s, plus emerging chains
Stackup15+ EVMEthereum, Arbitrum, Optimism, Polygon, Base

None of these providers natively support Bitcoin or Bitcoin L2s that use the UTXO model. EVM-compatible Bitcoin L2s (such as those using Particle Network's BTC Connect) can run ERC-4337 infrastructure, but native Bitcoin smart wallets use different primitives: Taproot spending conditions, FROST threshold signatures, and protocols like Spark that encode wallet logic at the protocol level rather than through on-chain smart contracts.

Deployment Cost Benchmarks

Unlike EOAs, smart contract accounts require an on-chain deployment before they can execute transactions. Most providers handle this transparently: the account is deployed in the first UserOperation, and the deployment cost can be sponsored by a paymaster so the user pays nothing.

The following gas figures come from Alchemy's open-source aa-benchmarks repository, measured on EVM testnets. Actual costs depend on the target chain's gas price.

Smart AccountDeployment GasNative Transfer GasNotes
Alchemy Modular Account v2~233,000~100,000Most gas-efficient deployment
Simple Account (reference)~297,000~100,000ERC-4337 reference implementation
Safe v1.4.1~435,000~100,000Heavier due to multisig + module system

For comparison, a standard EOA transfer costs 21,000 gas. Smart accounts add overhead from the EntryPoint contract validation, bundler submission, and paymaster verification. On L2s like Arbitrum and Base, this overhead translates to fractions of a cent. On Ethereum mainnet during congestion, it can cost several dollars.

EIP-7702 vs ERC-4337

EIP-7702, activated in Ethereum's Pectra upgrade in May 2025, introduced an alternative path to account abstraction. It allows an existing EOA to temporarily delegate to a smart contract implementation, gaining capabilities like batched calls, gas sponsorship, and session keys while keeping its original address.

The key difference: ERC-4337 creates a new smart contract account with a new address. EIP-7702 upgrades an existing EOA in place. For users with assets already distributed across EOAs, EIP-7702 avoids a migration step. For new applications building embedded wallets from scratch, ERC-4337 offers richer programmability and a more mature toolchain.

A critical caveat: with EIP-7702, the original private key retains full authority and can override smart contract rules including social recovery and spending limits. Pure ERC-4337 accounts do not have this bypass. For a detailed analysis, see our research on EIP-7702 code delegation wallets.

How to Choose a Provider

The right provider depends on what you are building and where your team sits on the build-vs-buy spectrum.

If you want a full-stack SDK with minimal infrastructure management: Biconomy, ZeroDev, or Alchemy Account Kit each bundle smart accounts, bundlers, and paymasters into a single SDK. Biconomy's MEE infrastructure and cross-chain gas tank suit high-volume consumer apps. ZeroDev's Kernel account and native session keys are well-suited for gaming and trading applications. Alchemy Account Kit integrates tightly with Alchemy's broader node and indexer platform.

If you need a battle-tested multisig for treasury management or DAO governance: Safe is the clear choice. With over 44 million deployed accounts and $100 billion in secured assets, it has the longest track record. The tradeoff is higher deployment gas and more complex module configuration.

If you want maximum chain coverage and flexibility to mix providers: Pimlico's account-agnostic bundler and paymaster services run on 100+ EVM chains and work with any ERC-4337 compatible account. Pair Pimlico with Safe, Kernel, or any other smart account to get infrastructure without vendor lock-in.

If you are building on Bitcoin: ERC-4337 providers do not natively support Bitcoin's UTXO model. For Bitcoin-native wallet abstraction with features like social recovery and gasless transactions, explore protocols like Spark, which implements similar UX improvements through FROST threshold signatures and protocol-level transaction sponsorship rather than on-chain smart contracts.

Frequently Asked Questions

Do I need to deploy a contract to use account abstraction?

Yes. ERC-4337 smart accounts are smart contracts that must be deployed on-chain before they can process transactions. However, most providers handle this automatically: the account factory deploys your contract in the first UserOperation. Paymasters can sponsor the deployment gas, so users never pay for or even see the deployment step. Deployment gas ranges from roughly 233,000 to 435,000 gas units depending on the account implementation.

Which account abstraction wallet works on Bitcoin L2s?

None of the major ERC-4337 providers (Biconomy, Safe, ZeroDev, Alchemy, Pimlico, Stackup) natively support Bitcoin or its UTXO-based Layer 2s. EVM-compatible Bitcoin L2s can run ERC-4337 through adapters like Particle Network's BTC Connect, which maps a Bitcoin wallet as the signer for an EVM smart account. For native Bitcoin Layer 2s, Spark achieves comparable UX improvements (gasless transfers, key recovery) through protocol-native mechanisms rather than smart contracts.

What is the difference between ERC-4337 and EIP-7702?

ERC-4337 creates a new smart contract account with its own address and uses an off-chain mempool of UserOperations processed by bundlers. EIP-7702 (live since May 2025) lets an existing EOA temporarily adopt smart contract logic while keeping its original address. ERC-4337 offers richer programmability and mature tooling. EIP-7702 avoids address migration but lets the original private key override smart contract rules.

How much does gas sponsorship cost with a paymaster?

Paymaster costs equal the actual gas consumed by the UserOperation plus any provider markup. On L2s like Arbitrum and Base, a sponsored transaction typically costs fractions of a cent. On Ethereum mainnet, costs range from $0.50 to several dollars depending on congestion. Providers like Alchemy bill monthly based on actual gas consumed. ZeroDev bundles sponsorship into tiered plans starting at $69/month for 10,000 UserOperations. Pimlico charges per-UserOp with a percentage markup on gas cost.

Can I use session keys to authorize recurring payments?

Yes. Session keys can be scoped to allow a specific contract call (such as a subscription payment) up to a defined value limit and time window. ZeroDev, Biconomy (via SmartSessions), and Alchemy (via ERC-6900 plugins) all support this pattern. The session key acts as a limited delegate: it can execute the authorized action without user intervention, but cannot perform actions outside its defined scope.

What is ERC-7579 and why does it matter?

ERC-7579 is a standard interface for modular smart account extensions. It defines how validators, executors, hooks, and fallback handlers attach to a smart account. Accounts that follow ERC-7579 (Kernel, Nexus, Safe via Safe7579) can install modules from a shared registry, meaning a session key module built for Kernel also works on Nexus. This interoperability reduces vendor lock-in and lets developers compose features from multiple module authors.

Is Safe still relevant for new projects?

Safe remains the most widely deployed smart account with over 44 million accounts and deep integration across the Ethereum ecosystem. It is particularly strong for multisig treasury management, DAO governance, and institutional custody where battle-tested security matters more than gas optimization. For consumer-facing embedded wallets, newer providers like Biconomy, ZeroDev, and Alchemy offer lighter-weight accounts and more streamlined developer experiences.

This tool is for informational purposes only and does not constitute financial or technical advice. Provider features, pricing, and chain support change frequently. Always verify current capabilities on each provider's official documentation before making integration decisions.

Build with Spark

Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.

Read the docs →