CoinTurk News EN and Crypto Economy give conflicting counts for how many cryptocurrencies are now included in Binance's expanded Proof of Reserves snapshot.
CoinTurk News EN and Crypto Economy give conflicting counts for how many cryptocurrencies are now included in Binance's expanded Proof of Reserves snapshot.
What all sources agree on
- Binance has announced full coverage of assets affected by the October 29 security breach, amounting to approximately $6.3 billion / $6.34 billion.
- The replenishment of funds used corporate resources, the Secure Asset Fund for Users (SAFU), and futures insurance funds.
- The verification architecture uses Merkle trees and zero-knowledge cryptography (zk-SNARKs) to allow users to independently verify their balances.
- The initial post-attack Proof of Reserves report included ten main tokens.
- The new snapshot was taken at 00:00 UTC.
Where the reports disagree
1Number of cryptocurrencies now included in the expanded Proof of Reserves snapshot
Binance expanded its Proof of Reserves (PoR) snapshot to cover 44 cryptocurrencies, up from ten in the previous assessment.
the new proof of reserves snapshot was taken at 00:00 UTC, significantly expanding the scope of the internal audit by incorporating 198 digital assets, compared to the ten main tokens included in the initial post-attack report.
What would settle it: Binance's official Proof of Reserves publication or statement listing the exact assets included in the November 4, 2026 snapshot.
What to make of it
Treat the core narrative of full coverage via corporate/SAFU/futures insurance funds and zk-SNARK verification as established, but do not rely on either the 44 or 198 figure for the number of cryptocurrencies covered until Binance's own Proof of Reserves documentation is checked.
Treat the core narrative of full coverage via corporate/SAFU/futures insurance funds and zk-SNARK verification as established, but do not rely on either the 44 or 198 figure for the number of cryptocurrencies covered until Binance's own Proof of Reserves documentation is checked.
