Account Storage
Pronunciation: uh-KOWNT STOR-ij
Definition
Account storage is the persistent blockchain state associated with an account, contract, or program-controlled data record. It can hold balances, configuration, permissions, counters, mappings, and application data that code reads or changes. Storage is usually committed through cryptographic roots or account hashes and may carry fees or size limits.
Overview
Meaning and scope
Account storage is the persistent blockchain state associated with an account, contract, or program-controlled data record. It can hold balances, configuration, permissions, counters, mappings, and application data that code reads or changes. Storage is usually committed through cryptographic roots or account hashes and may carry fees or size limits.
Mechanism and operation
Account storage represents durable state that survives after a transaction finishes. In Ethereum, a contract account has a storage root committing to a key-value structure, while the account’s code hash identifies executable logic. In Solana, mutable application state is commonly kept in separate data accounts owned by a program. Applications must know the contract layout, schema, serialization format, and version to decode them correctly. A proxy upgrade can change how existing slots are interpreted, and an incorrect decoder can show convincing but false values. Account Code and storage should therefore be analyzed together, along with migration rules and any external data that influences the program.
Practical payment example
An application stores state in on-chain accounts whose capacity and rent rules carry costs. Engineers estimate storage growth before deploying high-volume invoice records directly to the chain.
Operational checks
Persistent storage is scarce and often priced because every validating node may need to retain or verify it. Networks can impose rent, minimum balances, gas charges, limits, pruning, or specialized data-availability rules. Developers should avoid storing redundant data and should distinguish state required for consensus from records that can remain off-chain with a verifiable commitment.
Distinctions and limits
These designs differ, but both allow nodes to verify that execution produced the same resulting state. Backups of an application database do not replace the blockchain’s authoritative account storage.
Related reading
Related definitions: Account, Account Code.
Example
An application stores state in on-chain accounts whose capacity and rent rules carry costs. Engineers estimate storage growth before deploying high-volume invoice records directly to the chain.
Comparison
These designs differ, but both allow nodes to verify that execution produced the same resulting state. Backups of an application database do not replace the blockchain’s authoritative account storage.
Key Takeaway
Account storage is persistent protocol state whose meaning depends on the active code, schema, network rules, and cryptographic commitment.
Sources
- Ethereum Accounts — Ethereum Foundation (2026-08-02)
- Ethereum Execution Specifications: Block and Header Fields — Ethereum Foundation (2026-08-02)
- Solana Accounts — Solana Foundation (2026-08-02)