Account State

Overview

Account state represents what the blockchain currently knows about an account. The exact fields vary by protocol. An Ethereum account can include a balance, nonce, code hash, and storage root. Other networks may store resources, objects, staking information, permissions, or program-specific data under an account address.

State changes when valid transactions are executed. Sending funds decreases one balance and increases another. Calling a smart contract may alter contract storage, create new objects, emit events, or update several accounts. Nodes independently execute the same ordered transactions so they can agree on the resulting state.

Account state is usually authenticated through cryptographic commitments. Rather than placing every account record directly inside a block header, the protocol commits to the overall state through a root hash. This allows nodes and light clients to verify that a particular account record belongs to a recognized blockchain state when an appropriate proof is available.

A balance shown by a wallet is therefore a view of account state at a particular block or commitment. It may differ between a pending view, the latest block, and a finalized block. Payment systems should distinguish unconfirmed observations from state considered sufficiently settled.

State is usually too large to place directly in a block header, so blockchains commit to it with cryptographic roots. Nodes execute transactions in the agreed order and calculate the resulting state independently. If their state commitment differs, the block is invalid under the protocol rules.

Applications should distinguish authoritative protocol state from cached or indexed representations. A block explorer may show a token balance derived from contract events, while a node query reads current contract storage. These can temporarily disagree because of indexing delay, failed event decoding, or a chain reorganization. Critical decisions should rely on validated state at an appropriate confirmation level.