Proof of Reserves

Overview

Proof of Reserves is a method intended to provide evidence that a custodian, exchange, issuer, or platform controls specified reserve assets at a particular time. Custody must be evaluated through technical control, legal responsibility, account structure, operational capability, and customer rights. Possession of keys is important, but it is not the only measure of ownership or asset protection.

It is not automatically a financial-statement audit and may omit liabilities, asset encumbrances, legal ownership, control weaknesses, or events after the measurement time. It should be distinguished from Proof of Control, Custodian, and Total Balance. These concepts may interact in one workflow, but they identify different control points, records, or security assumptions.

Operationally, a credible process identifies addresses or custodial statements, verifies control, defines included assets and liabilities, explains methodology, and supports independent testing. A production implementation should preserve the applicable blockchain network, asset or contract identifier, source and destination ownership, policy version, responsible roles, timestamps, transaction identifiers, and evidence used to authorize or reconcile the action. Exceptions should be visible in an operational queue rather than silently corrected.

The principal risk is that borrowed assets, incomplete liabilities, hidden liens, selective timing, or weak assurance procedures can overstate the protection available to customers. Teams should test normal and exceptional paths, including delayed confirmations, reorgs, unavailable custodians, signing-device failure, stale permissions, incorrect network selection, fee spikes, duplicate requests, compromised user interfaces, and incomplete recovery data. High-value actions should be independently reviewed before execution.

For governance and audit, document the exact meaning of Proof of Reserves in the relevant wallet, custody platform, smart contract, or internal ledger. Confirm who can create, change, approve, pause, reverse, or recover the associated configuration. Monitoring should cover privileged access, policy changes, address and key lifecycle events, balance movements, failed transactions, reconciliation differences, and unresolved customer claims. This converts the term from a product label into a testable operational control.