EOA (Externally Owned Account)
Account controlled by a private key; initiates transactions.
An EOA, or externally owned account, is an Ethereum account controlled by one or more cryptographic private keys rather than smart contract code. It can sign messages and originate transactions, including ETH transfers and contract calls. The account exists on-chain, while wallet software or hardware helps the owner control it.
An EOA's state includes its ETH balance and nonce, which counts confirmed outgoing transactions and prevents replay within the account. ERC-20 token and NFT balances are generally recorded in separate smart contracts. The EOA has no deployed code of its own, although its address uses the same visible format as a contract address.
EOAs matter because they are the traditional starting point for Ethereum activity. A user needs an account to pay gas, send assets, approve tokens, or interact with a dapp. Validators see a signed transaction, verify the sender and nonce, and execute it under EVM rules. Losing the controlling key means losing the ability to authorize future actions.
Single-key control is simple but rigid. Anyone who obtains the private key or seed phrase can normally take the assets, and no protocol help desk can reset access. A lost key has the opposite effect: assets may become permanently unreachable. Hardware wallets, offline backups, limited approvals, separate accounts, and careful signing reduce these risks.
Contract wallets and account abstraction offer alternatives with multisig approval, spending limits, passkeys, recovery guardians, batched actions, or gas sponsorship. These features add smart contract and upgrade dependencies. An EOA can also be one signer controlling a contract wallet, so protecting the underlying key remains important.
Users should never type seed words into websites or ordinary dapps. Verify the network, destination, amount, allowance, and contract call on a trusted screen. Teams should not keep treasury control in one employee's EOA. EOAs provide direct, permissionless control and broad compatibility, but their security depends heavily on private-key management and the owner's ability to recover without exposing the account.
Public activity also links an EOA's transactions and balances, so using several accounts can improve organization but does not guarantee privacy. Funding patterns and repeated interactions may still connect them.
Frequently asked questions
- An EOA is controlled through cryptographic keys and can originate standard Ethereum transactions. A contract account contains code and traditionally executes only when called by a transaction or another contract. Smart contract wallets add programmable validation, recovery, and multiple signers. Both account types have addresses and can hold assets, but their authorization and execution rules differ.
- Use a reputable hardware wallet for valuable assets, store the seed phrase and any passphrase offline, and test recovery before significant funding. Verify transaction details on the trusted device, separate savings from dapp activity, and limit token approvals. Never share recovery words with support. For teams, avoid a single EOA and use a reviewed multisig or contract wallet.
- Yes. Deploy or create a compatible smart contract wallet, secure its signers and recovery rules, then transfer native assets, tokens, and NFTs carefully. Contract permissions, governance delegation, identity records, and app-specific positions may need separate updates. Test with small amounts and keep the old EOA secure until every asset and authority has been verified after migration.