A Routine for Reading Exchange Proof and Reserve Disclosures

Proof-of-reserves pages are easy to open and hard to read. Exchanges publish different things under similar names: a snapshot of assets, a list of wallet addresses, a Merkle-tree entry for your own balance, or a short blog post with a few totals. The words look reassuring, but they rarely tell you on their own which coins are included, whether customer liabilities are shown next to the assets, or what date the numbers describe. This guide sets out a routine you can repeat every quarter across Binance, OKX, Bybit and Bitget, using only each exchange's own help centre and disclosure pages. The goal is not to judge whether an exchange is safe. The goal is to know exactly what you read, what it did not cover, and what to check again next time.

Start by naming what kind of disclosure you are looking at

Before reading any number, decide which of the common formats you have in front of you. The first is an asset-only snapshot: totals of coins held in wallets the exchange labels as belonging to it, usually with addresses attached. The second is a reserve-and-liability comparison, where the exchange also publishes what it owes customers and shows a ratio between the two. The third is a personal inclusion check, where you log in, enter or look up an identifier, and see your own balance inside a tree of hashed entries. These are different documents with different limits, and a single exchange may publish one, two or all three at different times.

Write the format down in your own notes before you read further, because the rest of your reading depends on it. An asset-only snapshot cannot tell you whether reserves cover what customers are owed, no matter how large the totals look. A liability comparison can, but only for the coins and the moment it covers. A personal inclusion check only confirms that your balance was counted in one specific snapshot; it says nothing about the rest of the exchange's book. If a page mixes formats, separate them in your notes rather than treating the whole page as one claim.

Use the help centre search on each venue to find the current disclosure article rather than relying on a link you saved months ago. Articles get renamed, moved and retired, and an old link may open a page that no longer describes the present arrangement.

Read the scope: which coins, which accounts, which date

Every disclosure covers a scope, and the scope is where most misreadings happen. Look for the list of assets included and check whether it is complete or a selection. A page that covers the largest few coins by customer holdings is not the same as one that covers everything listed on the platform. Then look for the account types in scope: spot balances are usually the easiest to include, while balances held in futures, margin, earn products, or sub-accounts may sit outside the snapshot. If the article does not say, treat that as unknown rather than assuming inclusion.

The date matters as much as the list. A snapshot describes one moment, and customer balances move constantly afterwards. Note the exact timestamp and the time zone, because a figure dated to one day can be quoted for weeks afterwards. Also note how often the exchange says it repeats the exercise, if it says anything at all, and whether the page you are reading is the latest one or an archive entry.

Keep the source page open while you write, and copy the article title and the date it was last updated into your notes. If the article links to a methodology page, read that too; it usually explains how wallets were selected and how liabilities were calculated, and it often contains the caveats that the summary page leaves out.

Check the method claims one by one

Method descriptions are where you can separate a strong disclosure from a weak one. Look for how addresses were attributed to the exchange, whether they are signed by the exchange's keys, and whether the signing process is described in enough detail that a third party could repeat the check. Look for how the liability side was produced: whether it comes from an internal database query, from a third-party audit, or from a cryptographic commitment that customers can verify individually. Each of these has different strengths, and a page that simply states a ratio without describing either side leaves you with little to record.

For the personal inclusion check, the useful question is what you are verifying. If you can confirm that your own balance appears in the tree, you have verified inclusion for your account at that moment. You have not verified that the tree contains every customer, and you have not verified that the wallets hold enough to cover the total. Those are separate claims, and only the liability comparison addresses the second one.

If a term is unclear, search the help centre for that term rather than guessing. Exchanges often maintain glossary entries and methodology notes that explain their own vocabulary, and reading those before you draw conclusions will save you from repeating a misunderstanding in your own records.

Record the gaps and set a re-check date

After each reading, write a short entry with four parts: what was published, the date it describes, what it did not cover, and what you want to see next time. The gaps are the most valuable part, because they are what you will compare against in three months. Typical gaps include coins missing from the asset list, account types outside the scope, an absent liability figure, a ratio with no method behind it, or a snapshot that has not been refreshed since a much earlier date than the page suggests.

Set a re-check date and put it in your calendar rather than trusting memory. When that date arrives, open the same help centre section, find the current article, and compare it against your previous entry line by line. Did the scope widen or narrow? Did a liability figure appear or disappear? Did the update frequency change? A disclosure that quietly stops being updated is a more useful signal than any single number inside it.

Keep fees and trading costs in a separate part of your notes. Reserve disclosures say nothing about what you pay to trade, so check the official fee schedule on the exchange you use when you want that information, and record it separately so the two topics do not get mixed together.

Stop the routine for that session once you have your four-part entry. The point is a consistent, comparable record, not a verdict on any platform.

Risk boundary: Russia Crypto Guide

Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat. A referral link only records attribution; it does not guarantee access, pricing, rewards, approval or investment results. Availability can differ by residence, legal entity and product, so no regional access is assumed from language or branding alone.

Scenario checkpoint

• Identify which format you are reading: asset-only snapshot, reserve-and-liability comparison, or personal inclusion check, and note it before looking at any totals.
• Copy the article title, its stated snapshot timestamp and time zone, and the date the page was last updated into your notes.
• List the coins and account types the disclosure covers, and write down explicitly what falls outside that scope.
• Read the methodology or glossary page linked from the article and note how addresses were attributed and how liabilities were calculated.
• Run the personal inclusion check if one is offered, and record only what it confirms: your own balance at that snapshot.
• Set a re-check date and compare the next disclosure against your previous entry to see whether scope or update frequency changed.