Externally Owned Account (EOA)

Overview

Ethereum distinguishes externally owned accounts from contract accounts. An EOA has an address, balance, and nonce but no deployed bytecode. It initiates transactions by signing them with its private key. Contract accounts execute only when called by an EOA or another contract, although account-abstraction designs can make smart accounts behave more like user accounts.

The nonce orders outgoing transactions and prevents replay. A transaction includes the destination, value, data, gas parameters, chain identifier, and signature. Nodes verify that the signature corresponds to the EOA and that the account can pay the required cost.

EOAs are simple and widely supported, but recovery is difficult. Losing the private key can make assets inaccessible, while theft grants direct authority. Hardware wallets, multisignature smart accounts, and secure backup practices can reduce risk.

An EOA address does not prove a human identity. One person can control many EOAs, and a custodian can control an EOA holding assets for many customers.

Developers should also account for network context. The same EOA address can exist on multiple Ethereum-compatible chains with unrelated balances and transactions. Correct chain selection remains essential.

EOAs can authorize token allowances and contract permissions that remain active after the original transaction. Key protection alone does not remove risk if the account has already granted broad spending authority to a malicious or compromised contract. Wallets should help users review and revoke allowances. Migrating from an EOA to a smart account can add recovery and policy controls, but the migration itself must be carefully verified.

Network-aware wallet prompts help prevent signatures intended for one chain from being reused elsewhere.