Account

An account is a blockchain record that can hold digital assets, maintain a balance, and interact with smart contracts. Depending on the network, it may be controlled directly by cryptographic keys or by programmable code. An account is not the same as a wallet: the account exists on the blockchain, while wallet software helps a person view and control it.

On Ethereum and similar networks, the two traditional types are externally owned accounts and contract accounts. An externally owned account, often called an EOA, is controlled by one or more private keys. It can sign messages and start transactions, such as sending ETH or swapping tokens. A contract account contains smart contract code. It follows programmed rules when another account calls it and may manage assets for a protocol, multisig treasury, or smart contract wallet.

Every account has an address that other users and applications can reference. Its on-chain state may include a native currency balance, a transaction count called a nonce, and code or storage for a contract. Token balances are usually recorded inside separate token contracts rather than stored directly in the account. This detail matters when developers build portfolio tools or investigate why a block explorer shows several kinds of balances.

For example, a job candidate might use one account to receive contributor payments and another to test a new decentralized application. A company may use a multisig contract account for its treasury so no single employee can move funds alone. Account abstraction extends this model by letting programmable wallets support passkeys, sponsored gas, transaction batching, and recovery policies.

Account security matters because blockchain transactions are normally irreversible. Anyone who obtains the keys or satisfies a weak contract rule may be able to transfer the assets. Users should never share a seed phrase or private key, even with supposed support staff. Before signing, check the destination, network, amount, token approvals, and requested permissions. Using separate accounts for savings and routine app activity limits the damage from a malicious site or unsafe approval.

An account can be pseudonymous, but it is not automatically private. Balances and transactions on public chains can usually be inspected, and repeated activity may reveal links between addresses. Good account management combines secure backups, careful signing, limited permissions, accurate records, and a recovery process tested before it is needed.