What a wallet actually stores

Understanding the wallet metaphor

A digital-asset wallet is an application, device, service, or combination of components that helps a person or organization access digital assets on a blockchain network. The familiar word “wallet” can be misleading. A physical wallet contains banknotes, but a blockchain wallet generally does not hold units of cryptocurrency as local files. The authoritative record of balances, unspent outputs, or account state exists in the network’s distributed ledger. A wallet holds or accesses information needed to interact with that record, particularly signing credentials and the information required to find relevant entries.

Consider a person who loses a phone that ran a self-custodial wallet application. If suitable recovery material still exists and the blockchain remains accessible, the person may be able to install a compatible wallet elsewhere and regain the ability to transact. This would not be possible if the coins had literally been stored only inside the lost phone. The distinction between the ledger and the tools used to control it is the central idea of this lesson.

Three questions to ask

For any wallet, distinguish three questions: Where does the ledger record exist? Where is the signing authority held? What system shows the balance to the user? In a simple arrangement these seem like one service, but they can be completely separate. A wallet interface can display holdings derived from a remote node while a disconnected signer holds the private key, and an independent network confirms transactions.

The information a wallet may contain

A self-custodial wallet commonly manages one or more private keys or references to a protected signing component. A private key is secret cryptographic material used to authorize specified operations. The public keys and addresses associated with those keys are generally not secret. A wallet may also store labels, account names, transaction history caches, contacts, preferred network settings, and estimates of transaction fees. Those conveniences can disappear without changing what the blockchain records. Whether recovery also restores them depends on the product and its backup design.

Some wallets are watch-only. They can recognize addresses, read blockchain information, and prepare transaction details but lack the private key required to sign. Other wallets connect to a separate hardware signer. Custodial wallet interfaces may contain no customer-controlled blockchain private key at all; instead, they authenticate the user to a provider’s internal records and withdrawal system. These are operationally different arrangements even when their screens look similar.

Key material versus application data

The most important distinction is between material that can authorize movement of assets and material that merely helps display or organize information. An exported transaction list is useful for reconciliation, but it does not normally grant spending capability. A private key or a usable recovery secret may grant such capability. An extended public key can facilitate monitoring many derived addresses, but may create significant privacy exposure. A password that only unlocks an app on one device must not be assumed to be a backup of the wallet’s underlying signing keys.

Wallets view ledger state differently

A wallet needs a way to learn what has happened on the network. It may query a node operated by its owner, connect to an external node, or rely on an indexing service that converts raw blockchain data into convenient balances and history. These information sources are not equivalent to the blockchain’s consensus process. A display can be out of date or incomplete without the asset itself disappearing. Conversely, a wallet showing a pending transfer does not make that transfer settled or irreversible.

Blockchain accounting models affect what the interface needs to track. In a transaction-output model, a wallet identifies unspent outputs it can potentially spend and selects suitable outputs to fund a new transfer. In an account model, it reads account state and transaction-related records. The details were introduced earlier in the course; here the practical point is that the software interprets network data rather than storing the economic record as a local balance file.

A balance is a computed view

A displayed balance may exclude locked or reserved positions, include pending receipts, or express a view at a particular block height. Two applications can temporarily disagree because of indexing delays, network selection, or differences in what they count. For an investigation or audit, record the network, address or account identifier, observation time, and relevant block reference. A screenshot without those details may be hard to reproduce.

What the wallet does during a transfer

When a user requests a transfer, the wallet typically assembles the intended transaction, presents important details, obtains authorization, and submits the signed transaction to the network. These functions can take place within a single app or across distinct systems. Preparing a transaction means selecting the relevant network, recipient, amount, and applicable fee or resource parameters. Signing means applying the appropriate key material to the transaction data according to the network’s rules. Broadcasting means distributing the signed transaction for network processing. Validation and inclusion are performed by the network, not guaranteed by the wallet interface.

The phrase “connect a wallet” also needs care. A website connection might initially disclose only a public address or request access to account information, but a later request could ask the user to sign a transaction or message. A successful interface connection is not, by itself, a grant of unlimited authority; what matters is the exact permissions, signatures, and network operations involved. More advanced application permissions belong in a later module, but the separation of viewing, signing, and execution applies immediately.

Recovery and failure scenarios

If a wallet app is deleted, asset control may be recoverable from an appropriate backup. If a signing key is irretrievably lost and no alternative authorized signing path exists, blockchain validators generally cannot restore that key. If an application is compromised while a user signs, an attacker may try to substitute transaction details or exploit weak authorization checks. If an external indexing service fails, the correct response is to distinguish loss of visibility from loss of control. None of these outcomes should be inferred from the screen alone.

For management and public-sector purposes, a useful inventory identifies the network, the wallet’s role, who controls the signing material, what records are backed up, and whether an independent party can reconstruct the displayed state. A device inventory alone is not a custody inventory. The difference matters in incident reporting, legal preservation, business continuity, and vendor risk reviews.

Standards and professional context

NIST Special Publication 800-57 Part 1 Revision 5, Recommendation for Key Management: General, describes key-management concerns such as protection, compromise, recovery, and lifecycle. It is a general cryptographic standard, not a product-specific wallet endorsement. ISO/IEC 27001:2022, Information Security Management Systems — Requirements, offers an organizational framework for managing information-security risks. These references do not turn a user interface into a custody arrangement; they help teams document responsibilities and controls.

Exam focus: A wallet usually manages access and transaction authorization, while the blockchain records the asset state. Distinguish secret signing material, public monitoring data, app-only preferences, and remote ledger information; understand that visibility, signature, submission, and settlement are separate functions.