EOAs vs Smart Accounts

What is wrong with private keys as accounts, how smart-contract wallets fix the model, and the tradeoffs that have kept EOAs dominant despite their flaws.

25 min · expert · part of Account Abstraction & Wallet Engineering

The Account You Did Not Choose

When you open a wallet on Ethereum, Bitcoin, Solana, or almost any other major chain, the system hands you an account whose definition is fixed forever. That account is a single private key. The key signs transactions using a single, predetermined algorithm (ECDSA over secp256k1 for Bitcoin and Ethereum, Ed25519 for Solana). If you lose the key, the account is gone. If someone else gets the key, the account is theirs. There is no recovery, no daily spending limit, no multi-signature, no automatic blocking after a suspicious transfer, no way to upgrade the signature scheme to something quantum-resistant later. The account is a key, and the key is the account. This is called an Externally Owned Account, or EOA. The name was coined by Ethereum to distinguish it from the other thing on Ethereum, the Contract Account — a smart contract with code that runs when called. Bitcoin has the same concept under different names. The crucial fact is that on most chains today, the only kind of account that can initiate a transaction is an EOA. Smart contracts cannot pay their own gas, cannot start their own transactions, and cannot exist without an EOA somewhere to call them first. This design has held since Ethereum launched in 2015. It is the source of more user pain than any other single decision in crypto. Account abstraction is the broad term for the work to replace it with a model where every account is a programmable smart contract — where the rules of "who can spend this account, and how" are code that users can write, audit, and change. This lesson explains what is broken with the EOA model, what smart accounts look like in practice, and what the tradeoffs are that have kept EOAs dominant despite a decade of complaints.

Also in this lesson

Why Private Keys Are a Terrible UX
Smart Accounts: The Alternative Model
A Decade of Smart Wallets
What Smart Accounts Cost You
Where This Leaves Us

Key terms

EOA (Externally Owned Account): The default account type on Ethereum and most EVM chains, controlled by a single ECDSA private key over secp256k1. Has no recovery, no custom logic, and cannot pay its own gas without an EOA initiating the transaction.
Smart account (smart-contract wallet): An account whose access rules are defined by a smart contract rather than a single private key. Enables multi-sig, social recovery, session keys, sponsored gas, custom signature schemes, and policy enforcement.
Account abstraction (AA): The broad term for replacing the fixed EOA model with programmable smart-contract accounts, so that signature verification, gas payment, and access control are user-defined code rather than protocol-hardcoded rules.
Safe (formerly Gnosis Safe): The dominant institutional smart-account contract, in production since 2017-2018, supporting m-of-n multi-signature and modular extensions. Secures over $50 billion across 200+ chains as of 2024-2025.
Argent: The first consumer-facing smart-account wallet, launched 2018, which introduced social recovery, daily limits, and no-seed-phrase onboarding to a mainstream audience.
Social recovery: A recovery model where the user designates a "guardian set" of trusted parties (friends, hardware wallets, institutional services) who can collectively replace the active signing key if it is lost, without any central authority.
Session key: A temporary signing key authorized by the smart account with scoped permissions (specific contracts, dollar caps, time windows). Used to sign repetitive actions without prompting the user for every transaction.
Paymaster: An ERC-4337 contract that agrees to pay gas on behalf of a user. Enables sponsored transactions (apps cover gas), pay-in-token UX (gas paid in USDC instead of ETH), and earn-the-right-to-gasless models.
Counterfactual deployment: A technique using CREATE2 where a smart account address is computed in advance and only actually deployed on-chain when the first transaction is sent. Avoids paying deployment gas until needed.
Modular smart account: A smart-account architecture (Safe Modules, ZeroDev Kernel, ERC-7579) that separates the core account from pluggable validation, hook, and execution modules so that features can be added without redeploying the whole account.

Continue this lesson — 5 more sections in the CryptoBipto app.

Open lesson

Educational only — not financial advice.