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
What you'll learn
- The Account You Did Not Choose
- 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.
Read the full lesson in the CryptoBipto app.
Open lessonEducational only — not financial advice.
