Did you know? A crypto platform can demonstrate control over a large blockchain wallet without proving that it has enough assets to repay every customer or creditor. A photograph of a full vault is not the same as the complete balance sheet of the organisation that controls the vault.
Imagine a fictional school science club called Greenhouse Bank. Its officers proudly show a shared ledger containing 1,000 classroom credits under their control. Alicia is impressed until Tricia asks how many credits the club owes students. Kai Kai discovers that students have claims for 900, but the club also owes a separate 300-credit supplier invoice. The asset proof may be genuine. The conclusion that the organisation can meet every obligation would be wrong without additional information.
This is why proof of reserves and proof of solvency answer different questions. Reserve evidence can demonstrate selected assets, addresses or control at a specified time under a particular method. Solvency depends on whether the relevant entity’s assets and liabilities, valued and classified appropriately, support its obligations.
Quick answer: a proof-of-reserves report is not necessarily a financial-statement audit, a complete liability reconciliation or a legal guarantee of customer withdrawal. The scope may establish a snapshot of specified crypto assets or compare them with a selected customer-liability list, but it can omit other liabilities, encumbrances, custody relationships, subsequent withdrawals or valuation changes. Full solvency requires much broader and appropriately verified evidence.
This guide explains how blockchain technology works when a website publishes a reserve wallet, a Merkle-tree proof or a third-party attestation. It is conversational, written for parents, students and non-specialist readers, and uses imaginary credits rather than investment recommendations.
Your quick reading route
- A vault, a debt book and a crucial missing question
- What a proof-of-reserves exercise may examine
- A proof of wallet control is not proof of legal ownership
- What a balance sheet adds
- A Merkle tree can help include customers without publishing their names
- A valid inclusion proof can coexist with missing liabilities
- Why the snapshot date is part of the claim
- Frequently asked questions
- Primary sources and related reading
A vault, a debt book and a crucial missing question
Imagine a school treasurer opening the cash box and counting 1,000 classroom dollars. The count is performed correctly and witnessed by another committee member. What has been proved? That the inspected cash box contained 1,000 units at the time of inspection, within the method used.
Has the committee proved that the club can pay all its debts? No. It must also know who legally owns the money, which obligations exist, whether the funds are already pledged for another purpose and what other assets or liabilities belong to the organisation.
Suppose the club owes 900 credits to students and 300 to suppliers. Liabilities total 1,200, assuming all are valid and measured in comparable units. The 1,000-credit box is real, but it does not cover all 1,200 in this simplified model.
Now imagine the treasurer shows a second cupboard holding equipment. Its value and liquidity need to be assessed, and its legal ownership must be verified. A screenshot of the equipment cannot replace that work.
The school example teaches an important financial principle: verification of one asset is not proof of the complete financial condition of the entity that holds it.
A public blockchain makes selected asset movements easier to inspect under network rules. It does not, by itself, list every off-chain obligation or establish every legal right to use the assets.
What a proof-of-reserves exercise may examine
A crypto exchange, custodian or asset issuer may publish reserve-related evidence to reassure customers that it controls certain assets. Depending on the method, it might disclose wallet addresses, sign a message with relevant keys or have a third party inspect specified holdings at an agreed snapshot time.
A blockchain explorer can independently show that particular addresses held specified token balances at an accepted block. A valid signature can support control over the signing authority associated with an address, within the applicable model. Those are real technical facts when properly verified.
But the phrase *proof of reserves* is used for reports with different scopes. Some focus on asset balances, while others compare reported holdings with a selected set of customer entitlements. The details matter more than a marketing label.
The Public Company Accounting Oversight Board’s Investor Advisory on Proof-of-Reserve Reports warns that such reports are inherently limited and are not a substitute for the assurance users may expect from a financial-statement audit.
The proper first question is what did the particular report actually test, at what time, and against what complete population of obligations? If the method only covers a subset of holdings, it should not be advertised as though it settles every solvency question.
A good reading habit is to circle the words “scope,” “cut-off,” “asset types,” “address control,” “liabilities” and “limitations” in any reserves report.
A proof of wallet control is not proof of legal ownership
A person with a private key may be able to sign a challenge proving cryptographic control over a relevant address. That can be a useful part of verifying custody. It does not necessarily establish that the signer is the beneficial owner of every asset associated with the address.
A service could manage pooled funds for customers, operate a wallet on behalf of another company or hold collateral subject to an agreement. The public ledger may show which account can authorise certain actions without showing the legal ownership relationships among all interested parties.
Suppose Greenhouse Bank controls the key for a wallet containing 1,000 classroom credits. Half the credits could belong to customers, while another portion is collateral pledged for a supplier. A valid signature can still verify control of the address, but it cannot independently establish that all 1,000 are free for use to repay every depositor.
Custody structures can be more complex than one address and one owner. Multisignature accounts, smart contracts, restricted tokens and custodial arrangements introduce different technical and legal authority models.
A responsible report therefore distinguishes address control, legal entitlement, asset availability and liability coverage. Each requires evidence appropriate to the claim.
For the general identity boundary, see Why a Blockchain Address Is Not a Verified Identity.
What a balance sheet adds
A simplified balance sheet considers assets, liabilities and the residual equity or net asset position under a defined accounting basis. The basic identity is assets = liabilities + equity, with appropriate recognition and valuation rules.
In the fictional school example, assets of 1,000 and liabilities of 1,200 yield negative 200 equity when no other resources are counted. A genuine reserve count does not repair that shortfall.
Real organisations have more complicated statements. Their liabilities may include customer claims, loans, payables, contingent obligations or other amounts under applicable rules. Assets may include cash, securities, receivables and digital assets, each with valuation and availability considerations.
A snapshot of crypto wallets covers only some possible assets and none of the off-chain liabilities by itself. Customers need to understand whether the issuer is being evaluated as a complete financial entity or merely as a set of blockchain-controlled addresses.
A company also needs to distinguish solvency from liquidity. An entity may have positive total net assets but insufficient immediately accessible cash to meet a rush of withdrawals. Conversely, it could pay some customers today while facing a serious long-term shortfall.
Financial statements, audit evidence, legal rights and operating controls help address those distinct questions. A token contract’s balanceOf field cannot replace a consolidated view of financial obligations.
A Merkle tree can help include customers without publishing their names
Some reserve programmes use Merkle trees to commit to a collection of customer balance records. The operator constructs a commitment to the dataset, and individual customers receive proofs that their account’s record is included under the published root.
This can improve transparency compared with a mere unverified claim. A customer may check their own inclusion without seeing every other customer’s personal financial information. The underlying cryptographic data structure is useful for integrity and membership verification.
But a Merkle inclusion proof answers a narrow question: does this selected record belong to the dataset committed by this root under the defined algorithm? It does not prove that the complete population of customer liabilities was included, that every entry represents a legitimate balance or that other hidden obligations do not exist.
A user can have a correct inclusion proof for their own balance while the overall reported liability total is incomplete. The root alone cannot discover an omitted customer or an off-chain loan absent from the dataset.
A trustworthy approach therefore specifies how completeness was established, how total obligations were calculated and what independent assurance supports the data collection. Cryptographic checks complement, rather than replace, accounting procedures.
See Why a Merkle Proof Cannot Prove the Original Claim Is True for the wider distinction between proof of data inclusion and truth of the source claim.
A valid inclusion proof can coexist with missing liabilities
Let’s build a fictional liability list. Alicia is owed 300 classroom credits, Kai Kai 200 and Tricia 400. Together their claims total 900. The club publishes a Merkle commitment to all three records, and each student verifies that their amount is present.
That is encouraging. But now a supplier presents a legitimate invoice for 300 more credits. It was never included in the customer-liability list because it was not a customer balance. The original inclusion proofs remain mathematically correct while the larger entity’s total liabilities are 1,200.
A different problem arises if an eligible customer is omitted from a supposedly complete customer register. A proof that three known records are present cannot demonstrate that a fourth eligible record does not exist.
The mathematical commitment and the accounting population are different questions. The former is often well-defined and checkable; the latter requires evidence about how records were gathered, classified and reconciled.
Readers should therefore not interpret “every participating user can verify their inclusion” as equivalent to “there are no unreported debts.” The system needs a complete and appropriately controlled process for establishing the total obligation.
For students, the exercise makes a general data-literacy point: a perfectly accurate calculation over an incomplete list can still produce an incomplete conclusion.
Why the snapshot date is part of the claim
A reserve report often refers to a particular observation time or blockchain block. At that time, designated addresses may hold the reported assets. Customers may understandably want to know whether the same condition continues afterwards.
Assets can move, market prices can change and new liabilities can arise. A signed snapshot does not freeze the organisation’s future balance sheet or guarantee that withdrawals will be honoured next week.
For a fictional example, the science club counts 1,000 credits on Friday at noon. It pays 600 to a supplier at 15:00. The noon count can remain historically correct, but it is no longer a current available-balance statement.
The report’s date, method and intended period should be displayed clearly. A screenshot circulating on social media may omit these details and present historical evidence as if it had been observed moments ago.
Monitoring and repeated reports can improve visibility, but frequency alone does not solve every completeness, legal and valuation problem. A daily snapshot still needs reliable scope and accurate classification.
The important distinction is historical reserves at an identified point versus ongoing financial capacity to meet obligations. These are separate assertions with different evidence requirements.
Why encumbered assets complicate the picture
An asset can be under a company’s control while subject to a pledge, collateral arrangement, restriction or other claim that affects how freely it can be used. The term *encumbered* refers broadly to assets with such constraints.
Suppose the school club reports 500 credits in a wallet but has pledged them to secure a loan. The same balance cannot automatically be counted as fully available to satisfy unrelated customer withdrawals without assessing the lender’s rights and the relevant agreement.
An external blockchain observer may see the address balance but not every off-chain contract affecting the asset. Some on-chain collateral arrangements can be inspected, yet a complete legal analysis may require more than the chain’s own history.
A report that aggregates assets without explaining their availability can therefore create false confidence. The number can be accurate while the implied ability to redeem is not.
A responsible solvency assessment investigates legal ownership, custody, restrictions, competing claims and which creditors have priority under the applicable framework.
This is why unencumbered available assets can be a more meaningful concept than a generic wallet total when judging redemption capacity. What matters is what the entity is genuinely free and obligated to use.
Borrowed assets do not erase the corresponding debt
Imagine Greenhouse Bank borrows 400 classroom credits for one day. Its wallet now shows 1,400 rather than 1,000. An observer who only sees the asset balance may be impressed by the larger amount.
But the loan also creates an obligation to repay 400. Under the simplified accounting model, borrowing increases assets and liabilities together; it does not automatically improve the organisation’s net financial position.
The issue is not that every temporary transfer is improper. Ordinary financial institutions borrow and lend for legitimate reasons. The problem is using a gross asset snapshot as if it represented free surplus without accounting for the associated liabilities.
A credible proof-of-reserves programme should not make it easy for readers to confuse a brief increase in wallet balance with sustainable capacity to meet customer obligations. The verification scope and financial reporting method should address relevant timing and obligations.
The principle is simple enough for school maths: adding 400 to the cash box while adding a 400 repayment obligation does not create 400 of new equity.
This is another reason solvency cannot be inferred from wallet balances alone, regardless of how faithfully the network records the transfers.
Reserve quality and value both matter
Two reserve portfolios with the same headline currency value can carry different risks. One may consist of readily accessible cash under credible custody arrangements; another may include illiquid or volatile assets with uncertain market values.
A crypto exchange could report a large quantity of a thinly traded token. Multiplying that quantity by the latest small-trade price may produce an impressive total. But the organisation might not be able to sell its entire position for that price without substantially moving the market.
Valuation therefore depends on methodology, market access, concentration and the economic rights attached to the asset. A blockchain balance is a quantity of units, not a guarantee of cash proceeds.
For a school example, the club may own equipment advertised as worth 500 credits. If no other class wants to buy the equipment at that valuation, its immediate usefulness for repaying cash-like student claims is limited.
This is also why asset quality, liquidity and legal availability can matter as much as the existence of a reserve. A stablecoin issuer’s reserve design has particular challenges when token holders expect prompt cash redemption.
Read Why a Stablecoin Can Lose Its Peg for the connection between reserve confidence, market price and redemptions.
Solvent is not the same as able to pay immediately
A company can have assets exceeding liabilities and still experience difficulty converting the right assets into cash at the right time. That is a liquidity problem. The distinction is important when users can request immediate withdrawal.
Suppose the science club holds a building valued at 2,000 credits and owes 1,000 to students. It might be solvent under a simplified balance-sheet view if the building genuinely belongs to the club and can be counted at that value. Yet it cannot pay a student five credits immediately with a brick from the wall.
A platform that promises cash-like liquidity must therefore demonstrate more than long-term asset value. Withdrawal operations, settlement channels, available reserves and legal rights to access those funds all matter.
When many users ask to withdraw simultaneously, queues and processing bottlenecks can create further strain. Customers may sell platform-related tokens or claims at a discount, even if the issuer maintains that it has sufficient resources in the long run.
The exact financial definitions and remedies vary by jurisdiction and institution. A blog cannot diagnose the solvency of an unnamed current company from one generic example.
The educational rule remains useful: solvency concerns the relationship between assets and obligations; liquidity concerns meeting payments when they are due.
A third-party report is not automatically a full audit
A company may ask an independent professional to examine selected reserve balances, verify signatures or reconcile a specified customer list. These engagements can be useful and may provide defined assurance within their actual scope.
But the terms *attestation*, *agreed-upon procedures*, *proof of reserves* and *financial-statement audit* should not be used interchangeably. Each involves a different purpose, subject matter and level or type of assurance.
The US Securities and Exchange Commission’s Investor Bulletin cautions that proof-of-reserves and similar reports are not the same as financial-statement audits. Among its concerns is the absence of a complete picture of the entity’s liabilities.
The PCAOB’s investor advisory likewise warns that reports can be limited in timing, scope and information about liabilities. A report performed by a known accounting firm is not automatically an audit under every applicable professional standard.
Readers should inspect the actual signed report rather than a marketing graphic. Who prepared it? What procedures were done? Which assets and liabilities were included? Which dates were tested? What limitations did the report explicitly state?
These questions do not make independent verification worthless. They make its genuine value visible without claiming broader conclusions than the examiner tested.
What on-chain transparency can genuinely improve
Blockchain records can strengthen certain parts of asset verification. Public addresses and transactions can allow independent observers to inspect selected balances under the network’s accepted state without relying entirely on one company’s private database.
Cryptographic signatures can also help a custodian demonstrate control over the signing authority for specified addresses. Merkle commitments can make selected liability records tamper-evident and let customers verify that their entry is part of a declared dataset.
These are meaningful improvements when implemented and explained correctly. They can make hidden assumptions more visible, strengthen reconciliation and support independent comparison with a stated snapshot.
But the same system must account for external assets, liabilities, contracts, custody arrangements, valuation and the completeness of reports. These cannot all be solved by reading the public blockchain alone.
A strong design treats chain evidence as one layer of a financial control framework. It does not describe cryptographic proofs as substitutes for legal rights or accounting assurance.
The appropriate conclusion is neither “proof of reserves is useless” nor “proof of reserves proves everything.” It is some things can be verified more directly, while other essential solvency claims still require different evidence.
A classroom worksheet: what did the proof actually establish?
Create five columns on paper: asset balance, legal control, customer liabilities, other liabilities and accessible value. Begin with Greenhouse Bank’s reported reserve wallet containing 1,000 credits.
Under legal control, mark which credits the club owns or holds on behalf of others. Under customer liabilities, record Alice 300, Kai Kai 200 and Tricia 400, totalling 900. Under other liabilities, add the supplier’s 300-credit invoice. Under accessible value, note which assets can actually be used to meet the claims.
Now give each student a fictional Merkle inclusion proof for their own balance. The proofs can all be correct. Do the other liabilities disappear? No.
Add a fictional temporary 400-credit borrowing arrangement. Increase both the asset balance and the corresponding borrowing obligation by 400. Ask whether net position improved. Under this simplified model it did not.
Finally change the observation date. The wallet balance at noon differs from its value after an afternoon payment. Students should identify which claim still belongs to the earlier snapshot and which needs current evidence.
The exercise uses no live exchange or financial accounts. It teaches a general research discipline: match every impressive number to its denominator, legal meaning, time and missing obligations.
Eight claims that deserve careful wording
“The company showed a billion-dollar wallet, so it is solvent.” Selected assets do not establish the complete set of liabilities or accessible net value.
“A signed address proves the company owns everything there.” Signatures can support key control but do not settle legal beneficial ownership or competing claims.
“Every customer can verify a Merkle proof, so nobody was omitted.” Individual inclusion does not automatically prove dataset completeness or the absence of other liabilities.
“The reserve was full last month, so it must be full today.” A snapshot is historical and does not guarantee future financial capacity.
“A proof-of-reserves report is a full financial audit.” Engagements vary, and regulators explicitly warn against equating them.
“A large quantity of a token equals immediate cash of the quoted value.” Liquidity, valuation and restrictions affect realisable amounts.
“A positive balance sheet means every withdrawal can be paid instantly.” Liquidity and solvency are different conditions.
“An exchange’s on-chain assets automatically belong to its customers.” Legal custody, account terms and creditor rights require separate evidence.
The core correction is to use narrow, supportable conclusions. A valid proof should be celebrated for what it establishes—not stretched into what it never examined.
Frequently asked questions
What is proof of reserves?
It is a term for methods or reports aimed at verifying specified reserve holdings and sometimes comparing them with selected customer claims. The precise scope and assurance vary.
Does proof of reserves prove solvency?
Not by itself. Solvency requires a sufficiently complete understanding of assets, liabilities and applicable valuation and legal rights.
Can a wallet signature prove an exchange owns the funds?
It may support evidence of signing-key control over an address. It does not independently establish legal ownership or absence of encumbrances.
What is a Merkle-tree proof of liabilities?
It is a cryptographic method for proving a record is included in a committed customer-balance dataset. Additional evidence is needed to establish the dataset’s completeness and correctness.
Can a company show assets and omit liabilities?
An asset snapshot may omit obligations outside the reported population, intentionally or because of scope limitations. A reader should not infer that the list includes every liability.
Does a proof-of-reserves report equal an audit?
No universal equivalence exists. The PCAOB and SEC caution that these reports often differ substantially from financial-statement audits in scope and assurance.
Does being solvent mean all customers can withdraw immediately?
Not necessarily. Solvency and liquidity are distinct, and access to funds can depend on custody, banking and operational conditions.
Why does the date of a reserves report matter?
It identifies the period or snapshot examined. Holdings and obligations can change afterwards.
What if the reserves are in a volatile token?
The number of tokens may be visible on-chain, but their economic value and liquidity can change. Valuation requires separate analysis.
Can borrowed funds appear in a reserve wallet?
Borrowing can increase assets while creating a repayment liability. The complete financial position requires accounting for both.
Do positive reserve metrics guarantee customer legal protection?
No. Redemption rights, custody, creditor priority and relevant legal arrangements need independent verification.
What is the most important question?
Which assets and which liabilities were actually tested, at what time, under what method, and what major obligations could remain outside that proof?
Primary sources and related reading
The PCAOB Investor Advisory on Proof-of-Reserve Reports cautions against using limited reserve evidence to conclude that customer liabilities are fully covered. The SEC investor bulletin on alternatives to financial-statement audits explains the important differences between proof-of-reserves engagements and audits.
For eduKateSG follow-on reading, see Stablecoin Reserves and Redemption: Reconcile the Claims, Cash and Queue, Why a Stablecoin Can Lose Its Peg, Why a Merkle Proof Cannot Prove the Original Claim Is True and Why a Blockchain Address Is Not a Verified Identity.
The lasting lesson: proving that reserves exist is useful; proving that an organisation can meet all its obligations is a wider financial and legal task. A trustworthy explanation makes both parts visible.