👨🏾‍💻 Dev corner: how Proof of Reserves works (and what it can't prove)

Binance's latest Proof of Reserves snapshot covers 198 tokens using Nov 12 balances. Here's what that check actually does.

The goal: show the exchange holds at least as much crypto as it owes users.

Step 1, what it owes:
🔹 Each user's balance is hashed into a "leaf"
🔹 Leaves are paired and hashed again and again until one final hash is left: the Merkle root
🔹 The exchange publishes that root. Change any single balance and the root changes

Step 2, you check it yourself:
🔹 You get your leaf plus a short list of hashes, called a Merkle proof
🔹 Hash them together. If you reach the published root, your balance was counted
🔹 Binance adds zk-SNARK proofs, which show no balance is negative and the totals add up, without revealing anyone's data

Step 3, what it holds:
🔹 The exchange shows its on-chain wallet addresses, and reserves are compared with total user balances

What it can't prove:
🔹 It's a snapshot of one moment, not a live view
🔹 It doesn't show every debt the company has outside user balances
🔹 It doesn't prove the keys are safe. A hot wallet can be fully backed and still get hacked

Have you ever checked your own balance in a Proof of Reserves? 👇

📷 Photo: Shubham Dhage / Unsplash