Crypto exchanges are moving beyond periodic wallet snapshots as customers, regulators and institutional partners demand evidence that platforms can cover liabilities, control collateral and process withdrawals under stress. The next generation of proof of reserves could turn solvency into a continuously measured product feature, but only if exchanges solve the harder problem of proving what they owe without exposing customer data or creating new security risks.
For years, proof of reserves was presented as a relatively simple transparency exercise. An exchange disclosed a list of blockchain addresses, showed the balances held in those wallets and hired an accounting firm or blockchain analytics provider to confirm that the assets existed at a particular moment. The result offered customers a degree of reassurance, but it answered only one part of the solvency question.
A platform can control substantial cryptocurrency reserves and still be unable to meet customer withdrawals. It may have borrowed against those assets, pledged them to another lender, counted funds belonging to an affiliated company or carried liabilities that were not included in the review. A snapshot can also become outdated quickly in a market that operates around the clock and moves billions of dollars across borders within minutes.
That gap is driving a new phase of infrastructure development. Exchanges and custodians are experimenting with cryptographic proofs of customer balances, live reserve dashboards, segregated wallets, independent liability reviews and systems that track collateral movements. The goal is not simply to publish a larger balance sheet. It is to make financial claims verifiable often enough that customers can identify deterioration before a withdrawal freeze becomes necessary.
Reserves are only half of solvency
The basic accounting formula is straightforward: an exchange is solvent when its assets exceed its liabilities. In practice, verifying either side can be difficult.
Blockchain networks make assets unusually visible. Anyone can inspect a public address and see its balance, although proving that an address belongs to a particular exchange may require a signed message, a custodian statement or another form of evidence. This transparency is one of the strongest advantages of crypto infrastructure over traditional banking.
Customer liabilities are more complicated. An exchange may serve millions of users across several legal entities and jurisdictions. Some customers may hold spot assets, while others have margin positions, derivatives contracts, lending claims or balances denominated in stablecoins. The platform may also owe money to market makers, banks, employees, vendors and lenders. A reserve report that compares visible wallets with only a subset of customer balances provides an incomplete picture.
The collapse of FTX demonstrated why the distinction matters. The exchange had an extensive public profile and controlled valuable digital assets, but the central failure involved the relationship between customer funds, affiliated entities and obligations that were not transparently reported. The lesson for the industry was not that a wallet address has no value as evidence. It was that wallet evidence must be connected to a complete and independently reviewed liability framework.
A useful proof-of-reserves system therefore needs to answer several questions. Which assets are controlled by the exchange? Are they unencumbered, or have they been pledged elsewhere? Which customers are included in the liability calculation? Are all legal entities covered? Can the platform process withdrawals without relying on new deposits, emergency financing or the sale of illiquid collateral?
The more sophisticated systems now being developed are designed around those questions rather than around a single monthly announcement.
From snapshots to cryptographic balance proofs
One important innovation is the use of Merkle trees to prove that customer balances were included in a liability calculation without publishing every account balance publicly.
In a typical implementation, the exchange takes a snapshot of customer balances and converts account information into cryptographic values. Those values are organized into a Merkle tree, a data structure that allows each customer to receive a proof showing that their balance was included in the total. A customer can then verify the result independently without learning the balances of other users.
This approach is more meaningful than publishing an aggregate number because it gives customers a role in checking the claim. If a user is omitted from the data set, or if the reported balance does not match the exchange's records, the discrepancy can potentially be identified.
However, Merkle tree systems do not automatically prove that the reported liability total is complete. An exchange could exclude an account, omit a category of obligation or prepare the snapshot using a flawed internal ledger. Users can verify inclusion, but they cannot always determine whether the list includes every person and product the platform serves.
That limitation has encouraged research into zero-knowledge proofs. These systems allow one party to prove that a statement is true without revealing the underlying information. An exchange could, for example, prove that the sum of customer liabilities is below a specified reserve amount while keeping individual balances private. It could also prove that a set of accounts follows defined rules, such as showing that no user balance was altered after a reporting period.
Zero-knowledge technology could eventually support more frequent reporting. Instead of asking an accounting firm to inspect a database once a month, an exchange might generate a proof whenever its ledger changes or at regular intervals throughout the day. Independent observers could verify the mathematics using public software.
The business challenge is performance and governance. Large exchanges process complex products, internal transfers and transactions across several chains. Generating and verifying proofs at scale requires specialized infrastructure. The rules embedded in a proof also matter. A mathematically correct statement can still be too narrow if it excludes derivatives liabilities or treats a disputed claim as nonexistent.
Cryptography can make a defined claim harder to falsify. It cannot decide whether the claim itself covers the risks customers care about.
Live reserves require more than a dashboard
Real-time reserve reporting is another area attracting investment. Exchanges can connect blockchain data to public dashboards that show wallet balances, asset composition and recent movements. Some platforms already publish addresses for major cryptocurrencies and stablecoins, allowing customers and analysts to monitor balances continuously.
That visibility can improve accountability, but it creates difficult questions about interpretation. A large wallet balance may include assets held for a customer, collateral posted by a market maker or funds temporarily transferred from an affiliated company. A sudden increase in reserves may reflect a deposit that is offset by a new liability. A decline may result from routine wallet management rather than financial stress.
Live reporting also introduces operational risks. Publishing wallet addresses can make an exchange easier to monitor, but it can also help attackers map valuable targets. If the dashboard identifies hot wallets, cold storage movements or custody arrangements in excessive detail, transparency may expose the very systems designed to protect customer funds.
A more useful model would separate public reserve data into several layers. The first layer could provide verified asset balances by blockchain and asset type. The second could disclose whether those assets are held directly, through a qualified custodian or in an affiliated entity. The third could show encumbrances, borrowing arrangements and collateral obligations. A fourth layer could offer a cryptographic or independently audited estimate of customer liabilities.
This structure would help users distinguish between assets that are immediately available and assets that may be difficult to liquidate. It would also bring the quality of reserves into the discussion. Bitcoin held in a segregated wallet is not equivalent to a volatile token issued by an affiliated company, even if both appear at the same dollar value on a balance sheet.
Collateral movement is the missing signal
One of the most important developments will be the ability to track how reserves move after they are reported.
An exchange may show full reserves on the day of an attestation and then use those assets as collateral shortly afterward. If the borrowing arrangement is undisclosed, customers may continue to believe that their funds are unencumbered. A platform could also move assets between related entities, place them in decentralized finance protocols or send them to a lender in exchange for short-term liquidity.
Monitoring these movements requires more than watching public addresses. Analysts need entity attribution, labels for known custodians and lending venues, and information about the legal status of each wallet. The same blockchain transaction can represent routine internal custody management or a material change in the exchange's risk profile.
Some exchanges are responding by creating segregated wallet structures for customer assets. Under this model, customer funds are held separately from corporate treasury assets and cannot be used for proprietary trading or unsecured lending. Segregation does not eliminate every risk, particularly if records are incomplete or a custodian fails, but it narrows the range of ways customer funds can be misused.
The idea also aligns with regulatory changes in several major markets. Rules for digital asset firms increasingly focus on custody, client asset protection, capital requirements and governance. In Europe, the Markets in Crypto-Assets framework has intensified attention on reserve management and the treatment of customer funds. Other jurisdictions are developing their own standards, often with different definitions of custody and solvency.
This fragmentation makes consolidated reporting difficult. An international exchange may have separate subsidiaries, banking relationships and custody providers in each region. A customer might interact with a global brand while contracting with a local legal entity. Proof of reserves that covers only one subsidiary could create a misleading impression of safety for the broader group.
Independent audits still matter
Cryptographic systems can improve precision, but they are not a substitute for independent financial review.
An auditor can examine internal controls, legal agreements, bank accounts, custody contracts and liabilities that do not appear on a public blockchain. It can ask whether an exchange has accurately identified related parties and whether its accounting treatment reflects the economic reality of a transaction. It can also assess how the platform handles customer claims during bankruptcy or a technology failure.
The problem is that many early proof-of-reserves reports were structured as limited attestations rather than full audits. They often confirmed that a company appeared to control certain assets at a specified time, without offering an opinion on its entire financial condition. Some reports also excluded liabilities, which made them easy to misunderstand.
A stronger reporting model would combine three forms of evidence. Blockchain data would show the existence and movement of assets. Cryptographic user proofs would show that customer liabilities were included in a defined calculation. An independent audit would examine the exchange's books, controls, legal entities and off-chain obligations.
The timing of that review is important. A quarterly audit can provide valuable assurance, but it may not detect rapid deterioration between reporting dates. Continuous systems can provide earlier warnings, while audits can test whether the continuous system is operating as designed.
This creates a new market for assurance providers. Accounting firms, blockchain analytics companies, custody platforms and specialized cryptography developers are competing to provide different pieces of the verification stack. The strongest providers will need expertise in financial reporting, smart contracts, cybersecurity and regulatory compliance rather than relying on any one discipline.
Transparency versus privacy
The industry's push toward verifiable liabilities faces a fundamental privacy challenge. Customer balances can reveal wealth, trading activity and institutional strategy. Even a system that does not publish names may expose identities through transaction patterns, account sizes or repeated proof requests.
Exchanges need to prove enough information to establish solvency while minimizing the amount of data that becomes visible. Zero-knowledge proofs offer one possible solution, but privacy also depends on system design, access controls and governance. A cryptographic proof may hide a balance while a public dashboard reveals the wallet that funded it.
Institutional customers face additional concerns. Asset managers and corporate treasuries may not want competitors to see their positions or infer when they are moving funds. Market makers may regard wallet attribution as commercially sensitive. A reporting system that is acceptable to retail customers may be too revealing for professional participants.
A tiered disclosure model could address some of these needs. Retail users might receive individual inclusion proofs and a general solvency statement. Regulators and approved auditors could access more detailed records under confidentiality agreements. Institutional customers could receive tailored reports covering the assets and liabilities relevant to their accounts.
The objective should not be maximum disclosure at any cost. It should be verifiable disclosure that gives each audience the information needed to assess risk.
Trust becomes a product feature
For exchanges, better proof systems are becoming a competitive tool. Platforms that can demonstrate segregated custody, rapid liability verification and disciplined collateral management may attract customers who previously treated all venues as interchangeable.
This is especially important for institutional adoption. Banks, asset managers and payment companies need evidence that a digital asset partner can meet operational, legal and risk standards. A polished interface and deep liquidity are no longer enough. Procurement teams increasingly ask where assets are held, who controls the keys, how withdrawals are prioritized and what happens if an affiliated company fails.
Continuous proof systems could also support new financial products. A stablecoin issuer might publish reserve and liability evidence that updates throughout the day. A tokenized fund could demonstrate that the underlying assets exist and that the number of tokens in circulation matches investor claims. A lending protocol could use verified collateral data to adjust borrowing limits automatically.
In each case, the product value comes from reducing uncertainty. Customers do not need to trust an institution blindly if they can verify specific claims through independent data and cryptography. That does not remove the need for governance, legal recourse or human judgment, but it changes the balance between trust and verification.
Competition may eventually shift from who publishes the largest reserve figure to who provides the clearest risk picture. Exchanges could be ranked by withdrawal coverage, concentration of assets, percentage of funds held in segregated custody, quality of liability proofs and speed of disclosure after major wallet movements.
Such metrics would be imperfect, but they would be more useful than a simple claim that a platform is fully backed.
The standard is still being built
The biggest obstacle is the absence of a universal standard. Exchanges differ in how they define customer liabilities, treat locked balances, value illiquid tokens and account for margin positions. Custodians use different wallet structures, while regulators impose different reporting obligations.
Without common definitions, customers may compare reports that measure different things. One platform might include only spot balances, while another includes derivatives and lending claims. One might value collateral at market prices, while another applies a conservative discount. One might disclose affiliated assets separately, while another combines them with the exchange's own reserves.
Industry groups, regulators and technical developers will need to establish minimum reporting principles. Those principles could define required asset categories, liability coverage, treatment of encumbered reserves, frequency of updates and procedures for correcting errors. They could also require exchanges to publish the assumptions and code used to generate cryptographic proofs.
The standard should be demanding but practical. If reporting requirements are so complex that only the largest exchanges can comply, they may reinforce concentration in the market. If the rules are too weak, they will become another form of marketing.
The most credible systems will likely evolve in stages. First, exchanges will improve wallet identification and publish reserve data more consistently. Next, they will add customer inclusion proofs and disclosures about collateral. Later, zero-knowledge systems and continuous audits may allow near real-time verification across multiple chains and legal entities.
That progression reflects a broader shift in crypto infrastructure. Public blockchains made asset movements visible, but visibility alone did not guarantee solvency. The next generation of tools is designed to connect those movements to customer claims, corporate obligations and control systems.
If exchanges can make that connection reliably, proof of reserves will become more than a monthly snapshot. It will function as an ongoing layer of financial infrastructure, one that lets customers, regulators and business partners measure the health of a platform before confidence disappears.
