Skip to content
Independent XRP reference
Our standards
← All XRP news

Market Structure

What Binance’s November Reserve Proof Lets XRP Holders Verify

Binance took a snapshot of XRP balances on November 4. Its proof lets a customer check that the exchange counted their XRP at midnight. A holder who wants to move XRP today needs a separate check on the withdrawal route.

By
A pale-gold cheese trier holds a blue-veined sample beside the round hole it left in a cheese wheel on ivory stone.

Which XRP balance did Binance measure?

An XRP holder can now check whether Binance included their balance in its November 4 reserve snapshot. Binance announced on November 6 that the proof was ready for a report covering 44 tokens. The check connects a customer’s account to a dated total. Withdrawal availability and the exchange’s wider financial condition require separate evidence.

The reason to make that check is unusually concrete. In its November 3 incident report, Binance said five of its internet-connected wallets had sent 233.46 million XRP to an attacker on October 29. Reuters also reported those transfers, citing Binance’s investigation. That figure measures XRP that left wallets controlled by the exchange. A customer trying to reconcile their own account needs a different record, one that identifies the XRP Binance owed them after those transfers.

There are two such snapshots in the recovery notices. Binance took the first at midnight UTC on October 31. XRP and Ripple USD (RLUSD) were among the ten assets it covered. On November 2 the exchange released the proof for that snapshot. It then recorded 44 tokens at midnight UTC on November 4. The November 6 announcement made the second set verifiable. The Token Press observed the expanded report on the public site and explicitly distinguished that observation from running the verifier on a customer account.

The distinction between the measurement date and the release date matters even over two days. If you bought XRP on November 5, it belongs in your subsequent trading history. Looking for it in the newly released report would send you searching for a discrepancy that the timing alone explains.

Section sources[1][2][3][4][5][6]

How to check your own XRP entry

Start with your account on Binance. Under Wallet, open Verification and select the November 4 entry. Binance identifies the verification type, covered assets, historical balances and a record ID specific to that account and that snapshot. Find the XRP amount and compare it with the balance you can reconstruct at the cutoff. Keep XRP and RLUSD in separate lines of that reconciliation even if you use the XRP Ledger for both.

Consider a hypothetical customer who held 120 XRP when Binance measured balances, then bought 30 XRP later that day. Their current screen could show 150 XRP while the dated record correctly shows 120. The useful comparison is between the 120 and their own history at midnight UTC. If those amounts disagree, check when each trade, deposit or withdrawal was credited. Retain the dated discrepancy if it persists. A successful mathematical check can establish that Binance included the figure it supplied even when you dispute the figure itself.

For the cryptographic check, Binance’s instructions distinguish verifying the published root from verifying your own entry. A Merkle tree combines account records into one identifying value called the root. Your entry is a leaf. The verification path ties that leaf to the same root as the published report. Binance provides a downloadable account record and specifies which verifier goes with each reporting period. Use the files for the selected snapshot throughout. Mixing a newer root with an older account record breaks the comparison before it can tell you anything about your XRP.

Section sources[7][8][9]

What an outside observer can see on the XRP Ledger

A customer and an outside analyst have access to different evidence. The customer can compare a private account entry with their own transactions. An analyst can examine balances at identified public addresses. Neither can look up an exchange wallet on the XRP Ledger and read off which portion belongs to that particular customer. The division of a pooled balance among customers is part of the exchange’s accounting.

Binance describes two parts of its method. It checks control of the addresses used to demonstrate reserves. For the customer side, its zero-knowledge proof checks relationships among the account entries used to calculate the reported total, without publishing everyone’s balances. One customer checking a leaf can establish something an address-list observer cannot. They can check that their own account figure made it into the published calculation. The result says nothing about an omitted obligation until someone supplies evidence of that obligation.

CryptoKeyhole’s November 9 comparison illustrates the boundary. The service compared Binance’s figures with balances visible to nodes it operates on several networks. It expressly excluded XRP from those node checks. Its page is useful evidence of the scope of its independent work. Quoting its Bitcoin results as confirmation of Binance’s XRP reserves would change both the asset and the question being tested. A separate assessment of XRP would need a dated address set, a method for establishing control and a customer-liability figure measured at the same cutoff.

Verifelse lists XRP in its breakdown of Binance’s November 4 assets. Its chart asks how much of the reported reserve portfolio consists of XRP. To calculate a backing ratio, an analyst would instead divide the quantity of XRP available to meet customer claims by the quantity of XRP owed to customers. A portfolio share could fall while the exchange still held the same quantity of XRP, simply because another asset grew in value.

Section sources[7][8][10][9][14]

Why Binance’s 98% figure answers a different question

In Recovery Update 7 on November 4, Binance said it had replenished approximately 98% of the amount affected by the theft. It also said it was continuing to buy the remaining, less liquid assets. The percentage describes replacement across the incident. Applying it to the 233.46 million XRP sent out of the five wallets would assume the same replacement rate for every token. Binance’s update gives no basis for that calculation.

Replenishment and recovery also leave different records. Suppose an exchange buys replacement XRP with its own funds while investigators continue tracing the original transfer. A purchase can increase the assets available to cover customer balances even if investigators have yet to return any of the transferred XRP. Following an attacker’s wallet would shed light on the investigation. Following the reserve report would help answer whether a holder’s balance was counted. A firm could make progress on one while the other stood still.

Uncertainty remains around the wider financial picture. The Office of the Investor Advocate at the U.S. Public Company Accounting Oversight Board explained in a 2023 advisory that point-in-time reserve reports can leave out liabilities, borrowed assets and the availability of assets after the measurement date. The advisory addresses the limits of such reports generally. For someone assessing counterparty risk, the unanswered questions include what other creditors can claim and what resources would be available under stress. A later snapshot can extend the observation to another date. An assessment of those broader obligations would require financial disclosures with a wider scope.

Section sources[2][5][6][3][11]

Which record matters for an XRP withdrawal?

A holder who needs to send XRP has an operational question. On November 1 Binance listed XRP on the XRP network in the first phase of its withdrawal reopening. The notice said availability would be progressive and directed users to the withdrawal or network-status page for the selected pair. Later that day, Binance reported that native XRP withdrawals had reopened. Checking the route at the time of a transfer answers whether the exchange currently offers it. A reserve report from November 4 cannot answer a question about service at a later hour.

For an operations team paying an XRP invoice, this separates three records that might otherwise get filed together. The November report helps reconcile the historical exchange balance. The withdrawal screen shows the route the team can request. A completed transfer has its own transaction record, which the team can reconcile with what the recipient actually received. A screenshot of a successful reserve check would be a poor receipt for that payment, even if the exchange balance happened to equal the invoice amount.

For the next report, keep the November account entry and compare the two dates using the transactions between them. A change in XRP holdings then has a specific set of trades, credits or withdrawals to investigate. If the exchange changes the tokens or accounts covered, record that change before comparing totals. That simple discipline turns another reserve announcement into a reconciliation an XRP holder can actually perform.

Section sources[12][13][7][8]

What to watch next

  • • The next Binance snapshot’s UTC cutoff, covered assets and downloadable proof. Compare your own XRP entries after accounting for intervening transactions.
  • • A dated, reproducible check of Binance’s XRP addresses and corresponding customer XRP liabilities, with any assets held elsewhere identified.
  • • A recovery update that distinguishes purchases of replacement assets from funds returned to Binance, with XRP quantities separately identified if disclosed.
  • • The current XRP-on-XRP withdrawal status and a completed transaction record when reconciling a specific payment.

Sources and verification

We prioritize primary records and label supporting coverage. Dates reflect each source’s publication record.

  1. [1]Binance | November 4 reserve proof completion noticeprimary
  2. [2]Binance | Recovery Update 7 and expanded snapshotprimary
  3. [3]The Token Press | Expanded reserve proof, updated November 6supporting
  4. [4]Binance | Proof available for the October 31 snapshotprimary
  5. [5]Binance | Initial findings on the October 29 incidentprimary
  6. [6]Reuters | How XRP left five Binance hot walletssupporting
  7. [7]Binance | Proof of reserves and account verificationprimaryUndated reference
  8. [8]Binance | How to verify an account balance using the official verifierprimary
  9. [9]Coin Bureau | Binance security and reserve verification, November 4 updatesupporting
  10. [10]CryptoKeyhole | Binance address coverage, observed November 9, 2026supportingUndated reference
  11. [11]PCAOB Office of the Investor Advocate | Limits of proof-of-reserve reportsprimary
  12. [12]Binance | Phase one withdrawal routes, including native XRPprimary
  13. [13]Exchange.news | Binance confirms native XRP withdrawals reopenedsupporting
  14. [14]Verifelse | November 4 reserve composition, reviewed November 8, 2026supportingUndated reference