Skip to content

Guide · Protocol

Account abstraction and smart accounts (ERC-4337) explained

How ERC-4337 account abstraction actually works: UserOperations, bundlers, the EntryPoint contract, paymasters, and how EIP-7702 bridges ordinary EOAs into this model. Not financial advice.

By Etherelysium Editorial TeamUpdated 18 November 20267 min read

Account abstraction and smart accounts (ERC-4337) explained
Share X LinkedIn

A standard Ethereum account — an externally owned account, or EOA — can only be secured one way: a single private key, checked against a fixed, simple rule the protocol itself enforces. ERC-4337 lets an account be a smart contract instead, so its owner can define any validation logic they want — multiple signers, spending limits, social recovery, someone else paying the gas — without Ethereum’s own consensus rules needing to change at all.

The problem EOAs can’t solve on their own

An EOA’s rules are fixed by the protocol: one ECDSA signature, a strictly sequential nonce, and the account must hold enough ETH to pay for its own gas before anything else can happen. Every improvement people actually want — recovering access if a key is lost, requiring two approvals for a large transfer, letting an app sponsor a user’s first transaction so a new user doesn’t need to already own ETH just to get started — either requires a wrapper contract bolted awkwardly on top of an EOA, or a protocol-level hard fork. ERC-4337 was built specifically to make this a smart-contract-level problem instead of a protocol-level one, so it could ship and evolve without needing network-wide consensus changes.

The moving parts

UserOperation

Rather than sending an ordinary transaction, a smart account user signs a UserOperation — a pseudo-transaction object carrying the sender address, a nonce, the intended calldata, gas limits, fee fields, and a signature whose exact format the account contract itself defines, rather than a fixed ECDSA signature the protocol expects from an EOA. UserOperations go to a dedicated mempool, separate from ordinary transactions.

Bundler

A bundler collects pending UserOperations, checks them, and packages a batch of them into a single ordinary Ethereum transaction calling a shared EntryPoint contract. Bundlers can build L1 blocks themselves or work alongside the regular block-building pipeline described in the companion guide on MEV and proposer-builder separation.

EntryPoint contract

A single, shared on-chain contract that processes the bundle: it runs a verification pass calling each account’s own validation function and confirming fees are covered, then an execution pass running the requested calls, and finally pays the collected fees to the bundler.

The account itself

The smart contract wallet implements its own validateUserOp function — the part that decides what counts as valid authorization for that specific account, whether that’s one signature, multiple signatures, a time-locked recovery path, or something else entirely — then executes the requested calls once validation passes.

Paymaster (optional)

A separate contract that can cover gas on a user’s behalf, which is what makes sponsored transactions possible — a new user interacting with an app for the first time without needing to already hold ETH, or paying gas in a token other than ETH, with the paymaster settling the actual ETH cost itself.

Factory (optional)

Deploys a smart account the first time it’s actually used, which also lets an account have a predictable address before it has ever been deployed on-chain.

How this differs from an EOA in practice

An EOA must personally hold ETH to pay its own gas and is secured by exactly one private key with no built-in recovery path if that key is lost. A smart account under ERC-4337 can have someone else pay its gas through a paymaster, can require multiple approvals or add spending limits through its own contract logic, and can support recovery mechanisms an EOA has no way to implement on its own. The nonce is also no longer strictly sequential by default — it can be split so an account runs several independent nonce channels, letting multiple pending operations coexist without blocking each other the way a single sequential EOA nonce would.

Because validation now depends on arbitrary contract code and on-chain state rather than a single fixed check, bundlers rely on simulation and reputation rules to avoid processing UserOperations that would fail or that are designed to waste resources — a tradeoff for the flexibility smart accounts gain.

EIP-7702: the bridge from EOAs

ERC-4337’s own specification names EIP-7702 as a related mechanism: it lets an existing EOA temporarily take on contract-like behavior through a delegation, so an account that started life as a plain EOA can gain smart-account-style validation logic without first migrating to an entirely new address. The standard marks accounts using this path distinctly, since they still ultimately depend on an underlying EOA, whereas ERC-4337’s own broader goal is removing the need for EOAs to be the root of an account’s authority at all.

What this means for everyday users

In practice, account abstraction is why some newer wallets can offer passkey-based logins instead of a seed phrase, let an app cover gas on a user’s first transaction, or support recovering access without a single lost key being catastrophic. None of that requires the user to understand bundlers or EntryPoint contracts directly — those are the plumbing underneath a smart account, not something a user interacts with themselves.

Aggregators, and why bundlers need reputation rules

An optional aggregator contract can let multiple UserOperations share a single combined signature check, which helps bundlers process large batches more cheaply by avoiding a separate signature verification for every single operation. Because a smart account’s validation can call out to arbitrary on-chain state rather than a protocol-fixed check, a bundler including a UserOperation that later fails validation wastes its own resources with no fee to show for it — which is why bundlers apply simulation (running the operation against current state before including it) and reputation tracking (treating accounts or paymasters with a history of failed operations more cautiously) rather than accepting every submitted UserOperation at face value.

Why this took a standard, not a protocol fork

Changing how transaction validation works at the protocol level would require every node on the network to upgrade in a coordinated hard fork, with all the risk and lead time that implies. By building account abstraction entirely out of existing smart contracts — the EntryPoint, paymasters, the account logic itself — plus a separate mempool that infrastructure providers could choose to support, ERC-4337 let wallets and apps ship smart-account features incrementally, without needing the entire Ethereum network to agree on a consensus change first.

That same bottom-up path is part of why adoption has been gradual rather than instant: each wallet, bundler, and paymaster had to be built and tested independently, rather than switching on everywhere at once the moment the standard was finalized.

For most users, that gradual rollout means checking a specific wallet’s own documentation is still the most reliable way to know exactly which account-abstraction features it actually supports today, rather than assuming the whole standard is uniformly available everywhere.

Risk note

Smart accounts move the attack surface from a single private key to whatever validation logic the account’s contract implements. A well-audited smart account can genuinely reduce certain risks (lost-key catastrophe, phishing a single signature); a poorly reviewed one introduces new ones. The account type itself is not a guarantee of safety either way.

Not financial advice. Nothing on this page is a recommendation to buy, sell, stake, bridge, or avoid any asset or protocol.

FAQ

Do I need to understand bundlers to use a smart account wallet?

No. Bundlers, the EntryPoint contract, and UserOperations are the underlying plumbing; a smart account wallet’s interface handles all of that for you.

Can someone else pay my gas fees with account abstraction?

Yes, through a paymaster contract, which can sponsor a transaction outright or let you pay gas in a different token while it settles the actual ETH cost itself.

Is a smart account automatically safer than a regular wallet?

Not automatically. It changes the attack surface from a single private key to whatever validation logic the account’s contract implements — that logic needs to be well-built and reviewed to actually be safer in practice.

What’s the difference between ERC-4337 and EIP-7702?

ERC-4337 defines a full account-abstraction system built for dedicated smart contract accounts. EIP-7702 lets an existing EOA temporarily adopt contract-like behavior without migrating to a new address; ERC-4337’s own spec treats it as a bridge path, not a replacement for either.

Frequently asked questions

Do I need to understand bundlers to use a smart account wallet?
No. Bundlers, the EntryPoint contract, and UserOperations are the underlying plumbing; a smart account wallet's interface handles all of that for you.
Can someone else pay my gas fees with account abstraction?
Yes, through a paymaster contract, which can sponsor a transaction outright or let you pay gas in a different token while it settles the actual ETH cost itself.
Is a smart account automatically safer than a regular wallet?
Not automatically. It changes the attack surface from a single private key to whatever validation logic the account's contract implements -- that logic needs to be well-built and reviewed to actually be safer in practice.
What's the difference between ERC-4337 and EIP-7702?
ERC-4337 defines a full account-abstraction system built for dedicated smart contract accounts. EIP-7702 lets an existing EOA temporarily adopt contract-like behavior without migrating to a new address; ERC-4337's own spec treats it as a bridge path, not a replacement for either.

Educational content, human-edited and possibly AI-assisted. It describes how systems work and is not financial, legal or tax advice. Report an error via our corrections page.

More in Protocol

Related articles

See all