Binance ZK Proof of Reserves is a verification system that uses Merkle trees and zk-SNARK technology to let users confirm that their account balances were included in a reserve snapshot. It gives cryptographic evidence that covered assets are backed at least 1:1, without revealing individual balances. It doesn’t establish the exchange’s complete financial health.
The topic is drawing attention because Binance reported a security incident on October 29, 2026, widely searched as the Binance hack. According to Binance’s own statements, the affected assets were worth about $6.34 billion, and the exchange replaced them with company funds. Readers following Binance news today mostly want to know how much of that coverage can be checked independently.
The latest Binance-reported step came on November 12, 2026, when a snapshot covering 198 tokens was announced. Binance said the full proof for that snapshot would take roughly 40 to 50 hours to generate, so readers should confirm on the official page that it has been published. This guide explains Binance ZK Proof of Reserves, the ten-asset snapshot from October 31, the verification steps, and the limits.
The table below sets out how Binance ZK proof of reserves developed after the incident, as Binance reported it. Every figure in it is company-reported.
Date | Binance-reported development |
October 29, 2026 | Security incident reported |
October 31, 2026 | Reserve snapshot at 00:00 UTC covering ten assets |
November 2, 2026 | Zero-knowledge proof for the October 31 snapshot completed; about 95% of affected assets reported as replenished |
November 4, 2026 | Wider snapshot planned; about 98% of affected assets reported as replenished |
November 12, 2026 | Snapshot at 00:00 UTC covering 198 tokens; replenishment reported as complete |
Two details deserve attention. Completed replenishment means Binance replaced the affected assets from its own resources, and it doesn’t mean the stolen crypto was recovered. Reports on the announcement also note that withdrawals were reopening in phases, so finished replenishment and fully restored services are separate milestones.
The ten-asset table is accurate for the Binance October 2026 PoR snapshot, taken at 00:00 UTC on October 31. It shouldn’t be treated as the latest reserve report, because the November 12 snapshot is far wider. Binance reported all ten assets as backed at a minimum 1:1 ratio.
Cryptocurrency | Symbol | Short description |
Bitcoin | BTC | The first and largest cryptocurrency, mostly held as a store of value. |
Ethereum | ETH | A major smart contract network, also used to pay network fees. |
Tether | USDT | A stablecoin made to track the US dollar. |
Binance Coin | BNB | The native token of the Binance ecosystem, used for fees and BNB Chain activity. |
Solana | SOL | The token of a fast blockchain used for payments and apps. |
USD Coin | USDC | A dollar-linked stablecoin used widely in trading and payments. |
XRP | XRP | A digital asset built for fast, low-cost cross-border transfers. |
World Liberty Financial USD | USD1 | A newer dollar-linked stablecoin from the World Liberty Financial brand. |
Ripple USD | RLUSD | A dollar-linked stablecoin tied to the Ripple ecosystem. |
Zcash | ZEC | A privacy-focused coin that supports shielded transactions. |
Four of the ten assets are stablecoins, which shows how much of an exchange’s balance sheet can sit in dollar-linked tokens. Binance Coin raises a separate point. BNB is tied to the exchange’s own ecosystem, so reserves held in that token could lose value at the same moment confidence in the platform falls, a correlation risk that a 1:1 count alone doesn’t capture.
Per-asset ratios, customer liabilities, and matching reserve holdings belong on Binance’s official reserve page, and readers should check those figures there rather than rely on any summary.
A Merkle tree is a structure that turns many records into a single fingerprint. Under Binance ZK Proof of Reserves, Binance hashes each user’s balance data into a leaf, pairs the leaves, and keeps hashing upward until one value remains, called the Merkle root. Changing any record would change the root, which makes tampering visible.
Each leaf carries an account index, which marks its position in the tree, and a record ID, a hash that identifies the account. Binance’s verification guide names these fields AccountIndex and AccountIdHash. Together they let a user trace a personal record up to the root without exposing balances to anyone else.
The zk-SNARK adds the reserve check. It’s a compact proof that the customer balances in the tree are covered by reserves of at least 1:1, produced without revealing any single account. Binance's zk-SNARK technology therefore answers two questions at once: whether a balance was counted and whether the counted totals are backed.
Wallet ownership needs separate attention. A reserve proof still depends on the exchange identifying which addresses it controls, so the address list and the method used to show control remain points worth checking on the official page.
Binance’s official verification guide describes how Binance ZK Proof of Reserves can be checked locally on the user’s own computer. The steps below follow that guide and should be matched against its latest version.
Download the verifier from the official Binance GitHub repository, using its releases page.
Log in at Binance.com and open Profile, then Wallet, then Verification.
Expand the verification data, choose the snapshot, and confirm the verification type reads Merkle Tree + Zksnarks.
Download the Merkle tree file for that snapshot.
Place the config, proof, and verification key files in the verifier’s config folder, then run the verifier for the operating system to check the root hash.
Place the user_config.json file from the download in the same folder, then run the verifier with the user option to check the account.
Compare the AccountIndex and AccountIdHash fields with the Merkle leaf and Record ID shown on the Verification page.
Snapshots in the guide are timed at 00:00 UTC, so a result reflects the balance at that moment and may not match the current balance. Files should come only from the official Binance site and repository, since fake verifier downloads are a known phishing route.
A successful check establishes specific claims about a covered snapshot and a user’s inclusion in it. It doesn’t establish complete exchange-wide solvency, and five limits apply.
A snapshot can’t guarantee solvency at every moment, since balances and reserves move between snapshot dates.
Controlling wallets doesn’t necessarily show the assets are free of encumbrances, such as borrowed funds moved in temporarily to pass a check.
The proof doesn’t show undisclosed liabilities or off-chain obligations that sit outside the customer balance tree.
Cybersecurity and custody risks remain, and the October 29 incident is a reminder that reserves can be exposed to theft.
A passed check doesn’t guarantee uninterrupted withdrawals, because services can pause for security reasons.
For that reason, Binance 1:1 reserve backing is best read as one data point. It answers whether covered customer balances had matching reserves on the snapshot date, and little beyond that.
Each exchange publishes its own method, and the differences matter more than the labels.
Exchange | Verification approach | Comparison point |
Binance | Merkle tree with zk-SNARK | Privacy-preserving user verification: Binance says the open-source verifier code was independently audited. |
Kraken | Merkle tree with independent accountant review | The accountant builds the tree and checks proof of address control; Kraken publishes its own list of limitations. |
OKX | Merkle tree with zk-STARK | A different zero-knowledge architecture; scope and third-party involvement should be checked on its official page. |
No system here is universally safer. Scope, third-party involvement, and what each method leaves unproven are the fairer points of comparison, and a crypto exchange reserve audit by an outside firm answers different questions than a cryptographic check run by users.
A financial audit is carried out by an accounting firm that reviews records, liabilities, and internal controls under professional standards. Binance ZK Proof of Reserves, by contrast, tests a defined claim about a snapshot, and any user can rerun it. Third-party assurance and cryptographic verification are different forms of evidence, and neither alone shows complete solvency.
Binance’s announcements are a primary source for what Binance reported, and they aren’t independent confirmation of every financial claim. Binance says its verifier code was independently audited, but that statement concerns the software, not the exchange’s accounts. The reports reviewed for this article don’t name an independent accounting firm for these snapshots.
The stronger signal in Binance ZK Proof of Reserves is scope. The jump from ten assets on October 31 to 198 tokens on November 12 gives a much wider view of reserve coverage than the first report. The main concern is that key figures, including the replenishment figures, still come from Binance’s own reporting.
The biggest unknown is whether an independent accounting firm reviewed any of these snapshots. Readers should verify the snapshot date, confirm the 198-token proof is published, check per-asset ratios on the official page, and watch how much of the reserve sits in Binance Coin.
Binance ZK Proof of Reserves lets users check that their balances were counted and gives cryptographic evidence of at least 1:1 backing for covered assets. The October 31 ten-asset snapshot was followed by a 198-token snapshot on November 12, and Binance reports replenishment as complete.
Independent accounting review, undisclosed liabilities, and full-service restoration remain uncertain, so the sensible next step is to run the verifier locally and read the per-asset ratios on the official page.
Disclaimer
This article is for informational purposes only and doesn’t constitute financial, investment, or legal advice. Crypto assets are volatile and carry a high risk of loss, and a proof of reserves doesn’t guarantee safety. Readers should research independently and consult a licensed advisor before making decisions.