What does account abstraction enable?

Five core capabilities not available with EOAs: (1) gas sponsorship — a paymaster pays gas on behalf of the user, enabling gasless onboarding. (2) Batched transactions — multiple operations in one user signature. (3) Social recovery — a guardian set can rotate the wallet's signing key without seed phrase. (4) Custom signature schemes — passkeys, multi-sig, multi-factor. (5) Session keys — time-limited keys that can sign specific operations without re-prompting.

What's a UserOperation?

A UserOperation (UserOp) is the AA equivalent of an Ethereum transaction. Instead of signing a transaction directly, the user signs a UserOp — a bundle containing the target contract, calldata, gas parameters, and signature. UserOps are submitted to a bundler, which packages them into a single bundle transaction that executes via the EntryPoint contract. The UserOp model is what enables paymasters, batched calls, and custom signature schemes.

What's a bundler? A paymaster?

A bundler is a node operator (often run by Alchemy, Pimlico, Stackup, Biconomy) that collects UserOps from users, packages them into a single bundle transaction, and submits it to the EntryPoint contract. Bundlers earn gas refunds. A paymaster is a smart contract that pays gas on the user's behalf — sponsored gas (the dApp pays), or fee-token paymasters (the user pays in ERC-20). Together, bundlers and paymasters enable gasless and stable-coin-paid onboarding.

Why do AI agents use AA?

AA wallets are a common primitive for AI agents because (1) session keys let an agent sign limited operations without escrowing user keys, (2) batched UserOps let an agent execute multi-step strategies atomically, (3) paymasters let the agent operate without needing the user to manually fund gas, and (4) social recovery lets the user revoke agent access if compromised.

Account Abstraction (ERC-4337) Definition for Agents

Account abstraction (ERC-4337) is the Ethereum standard that replaces externally-owned accounts (EOAs) with programmable smart-contract wallets.

In a traditional EOA model, the user's private key directly controls the address — same key signs every transaction, and there's no way to add a guardian, rotate the key without losing assets, or have someone else pay gas. AA changes this by routing every operation through a smart contract that the user owns. The contract decides what counts as a valid signature.

Five new capabilities AA enables:

Gas sponsorship — a paymaster pays gas on behalf of the user (dApp-funded onboarding, ERC-20-as-gas)
Batched transactions — multiple calls in one user signature, atomically
Social recovery — a set of guardians can rotate the signing key without seed phrase
Custom signature schemes — passkeys (Touch ID/Face ID), multi-sig, MPC, FROST
Session keys — time-limited or scope-limited keys for specific operations

Alchemy cites nearly 20 million ERC-4337 native smart accounts deployed in 2024, while third-party ecosystem reporting has cited 40 million-plus smart-account deployments across Ethereum and major L2s. Treat these as ecosystem snapshots rather than Hive runtime facts.

Why agents care

AA wallets are a common primitive for AI agents because they enable safer delegation. Instead of trusting an agent with the user's full seed phrase, the user grants the agent a session key with a tight scope (e.g., "swap up to $1000 USDC into stablecoin pairs over the next 24 hours, on Base only"). When the wallet and policy are implemented correctly, the session key can be constrained so it cannot exceed the approved scope, cannot perform privileged wallet actions, and expires automatically.

This is why account-abstraction infrastructure commonly appears in agent-wallet designs. Hive's MCP tool surface includes wallet and account-abstraction queries via Moralis + Alchemy upstreams — get_userop_history, get_smart_wallet_owners, etc.

Why agents care

Related terms