Binance says it has replenished the funds: Don’t just read the announcement—check for yourself in 3 steps whether your assets are backed 1:1
When it comes to “fund security,” hearing someone say it a hundred times is no substitute for checking it yourself once.
In the early hours of November 13 Beijing time, Binance’s official X account and Binance Chinese posted the key points:
- The funds for assets affected by this security incident have been replenished;
- A new snapshot of its Proof of Reserves (PoR) has been published;
- Once the zero-knowledge proof (ZK Proof) has been generated, users will be able to independently verify that their assets have at least 1:1 reserve backing.
Pay attention to the phrase “once it has been generated”: the snapshot is available, but the proof file you can check personally is still pending. If you don’t see the date of this incident on the verification page, that means it hasn’t been published yet—not that there’s a problem with your account.
How to check (following the steps listed on Binance’s Proof of Reserves page):
1. Log in to Binance on the web → click “Wallet” → click “Verification.”
2. Select a verification date: choose the latest snapshot. The page will show the verification type, your Record ID (different for every account and each verification), the assets covered, and your balance at the time of the snapshot.
3. Compare the numbers: check the snapshot balance shown on the page against your holdings at that point in time. If they match, your balance has been included in the total liabilities.
What exactly does this proof prove? Binance’s page lists three things, guaranteed by zk-SNARK circuits:
① Your balance is included in the sum of all users’ net balances;
② Every account’s net balance is ≥ 0 (preventing negative-balance accounts from making total liabilities appear “smaller”);
③ The Merkle tree root was updated correctly, without using fake data.
On the reserves side, Binance proves that the cold and hot wallet addresses belong to Binance.
It’s also important to understand what the proof cannot show: it’s a snapshot at a specific point in time, not real-time; it proves that “reserves ≥ liabilities,” but says nothing about whether something might go wrong in the future. So don’t treat a single 1:1 check as permanent insurance. Each time a new snapshot comes out, take a minute to check again.
Finally, watch out for follow-up scams: after a security incident, fake messages about “claiming compensation” or “migrating assets” are especially likely to appear. On November 11, Binance introduced Binance Verify: open it and enter the other party’s account, website, or message source to check whether it’s official. Treat any message asking you to click a link to “claim compensation,” or requesting a verification code or seed phrase, as a scam.
When exchanges or wallets post announcements, I break them down into steps you can follow. Follow me—every post is practical.
This article does not constitute investment advice.
#币安 #储备金证明 #安全 #SelfCheck
When it comes to “fund security,” hearing someone say it a hundred times is no substitute for checking it yourself once.
In the early hours of November 13 Beijing time, Binance’s official X account and Binance Chinese posted the key points:
- The funds for assets affected by this security incident have been replenished;
- A new snapshot of its Proof of Reserves (PoR) has been published;
- Once the zero-knowledge proof (ZK Proof) has been generated, users will be able to independently verify that their assets have at least 1:1 reserve backing.
Pay attention to the phrase “once it has been generated”: the snapshot is available, but the proof file you can check personally is still pending. If you don’t see the date of this incident on the verification page, that means it hasn’t been published yet—not that there’s a problem with your account.
How to check (following the steps listed on Binance’s Proof of Reserves page):
1. Log in to Binance on the web → click “Wallet” → click “Verification.”
2. Select a verification date: choose the latest snapshot. The page will show the verification type, your Record ID (different for every account and each verification), the assets covered, and your balance at the time of the snapshot.
3. Compare the numbers: check the snapshot balance shown on the page against your holdings at that point in time. If they match, your balance has been included in the total liabilities.
What exactly does this proof prove? Binance’s page lists three things, guaranteed by zk-SNARK circuits:
① Your balance is included in the sum of all users’ net balances;
② Every account’s net balance is ≥ 0 (preventing negative-balance accounts from making total liabilities appear “smaller”);
③ The Merkle tree root was updated correctly, without using fake data.
On the reserves side, Binance proves that the cold and hot wallet addresses belong to Binance.
It’s also important to understand what the proof cannot show: it’s a snapshot at a specific point in time, not real-time; it proves that “reserves ≥ liabilities,” but says nothing about whether something might go wrong in the future. So don’t treat a single 1:1 check as permanent insurance. Each time a new snapshot comes out, take a minute to check again.
Finally, watch out for follow-up scams: after a security incident, fake messages about “claiming compensation” or “migrating assets” are especially likely to appear. On November 11, Binance introduced Binance Verify: open it and enter the other party’s account, website, or message source to check whether it’s official. Treat any message asking you to click a link to “claim compensation,” or requesting a verification code or seed phrase, as a scam.
When exchanges or wallets post announcements, I break them down into steps you can follow. Follow me—every post is practical.
This article does not constitute investment advice.
#币安 #储备金证明 #安全 #SelfCheck
