Binance Completes zk-SNARK Proof for 10 Tokens After $6.3B Hack

Binance Completes zk-SNARK Proof for 10 Tokens After $6.3B Hack


Crypto exchange Binance has completed the zero-knowledge proof for its October 31 Proof of Reserves (PoR) snapshot, allowing users to independently verify that their balances in 10 listed tokens were backed at a minimum of 1:1. The exchange announced the completion on November 2, following a security breach it estimates caused an impact of approximately $6.3 billion.

In a detailed X update on Monday, the exchange said the completed proof covers Bitcoin (BTC), Ether (ETH), Tether (USDT), BNB, Solana (SOL), USD Coin (USDC), XRP, USD1, Ripple USD (RLUSD) and Zcash (ZEC). Binance said users can run the verification through a tool available on its PoR website. The snapshot was taken at 00:00 UTC on October 31.

Binance completed a zk‑SNARK proof confirming 1:1 backing for ten tokens in its October 31 reserves snapshot.

Users can independently verify their balances using Binance’s open‑source verifier tool hosted on the PoR website.

TRM Labs traced roughly $6.3 billion in stolen funds across ten networks, linking the breach to a compromised DevOps engineer’s laptop.

The update establishes that the listed assets met the exchange’s stated reserve coverage threshold at the snapshot time. It does not establish that the stolen funds have been recovered or independently verify the exchange’s complete financial position.

Binance says users can verify 10 tokens through zk-SNARK proof

Binance uses a combination of Merkle Trees and zero-knowledge succinct non-interactive arguments of knowledge, or zk-SNARKs, in its PoR system. According to the exchange, the Merkle Tree structure allows users to check whether their account balances are included in the published snapshot, while the zk-SNARK proof verifies that the covered reserves meet the minimum 1:1 backing requirement without disclosing individual account balances.

Users must log in to their Binance accounts and download the verifier tool from the exchange’s PoR website to perform the check on their own computers. Binance said the verifier is open source and available through a public GitHub repository.

The exchange also said the latest proof was completed within its previously estimated 40-to-50-hour processing window. It plans to take another reserve snapshot on November 4, covering additional tokens, and then generate a new proof. Binance has not specified which additional assets will be included.

Binance says 95% of affected assets have been replenished

The proof update follows Binance’s disclosure that it had replenished approximately 95% of the assets affected by the October 29 incident. The exchange said the remaining 5% consists of tokens outside the 10 listed assets, which are less liquid and take longer to source at the required scale.

Binance has said it is using its own funds to cover the shortfall, drawing on its Secure Asset Fund for Users (SAFU), part of its Futures Insurance Fund and its corporate treasury. It has also been acquiring the remaining tokens through market purchases and over-the-counter transactions.

The 95% figure refers to the replenishment of affected customer assets, not the recovery of 95% of the funds taken by the attacker. Binance has said it will absorb the financial impact rather than pass the loss on to users.

Withdrawals resume in stages after security review

The exchange has also begun restoring withdrawals across supported networks following the suspension imposed after the breach. Bitcoin withdrawals reopened first on November 1, followed by selected assets on Ethereum and BNB Smart Chain. Binance’s first phase also covered assets across networks including Tron, Solana, the XRP Ledger, Zcash, Dogecoin, TON, Polygon, Avalanche, Arbitrum, Base, Optimism and Sui.

Binance said the rollout would proceed network by network after security and stability checks. It has not provided a date for restoring withdrawals across every remaining asset and warned that high demand could delay or prevent some transactions during the initial stages.

The phased reopening followed the exchange’s October 29 suspension of deposits and withdrawals. Deposits were restored on October 30, while withdrawals remained restricted pending further checks.

How the $6.3 billion Binance incident unfolded

Binance disclosed unauthorized withdrawals from its hot wallets on October 29. The exchange estimated the incident’s impact at approximately $6.3 billion. Blockchain intelligence firm TRM Labs separately estimated that about $6.36 billion had moved from Binance wallets across 10 networks, including Ethereum, Bitcoin, Tron, the XRP Ledger, Solana, Arbitrum, Avalanche, Optimism, Base and Polygon.

On Ethereum, TRM Labs said the attacker used the EIP-7702 authorization mechanism to gain control over a Binance hot wallet and execute transfers. EIP-7702, introduced as part of Ethereum’s Pectra upgrade, allows externally owned accounts to delegate execution to smart contract code.

Binance initially identified a potentially compromised DevOps engineer’s laptop as a point of entry. It later said investigators had found additional points of compromise. The exchange has stated that it found no evidence that wallet private keys were leaked.

Binance has not published a complete technical account of the incident or publicly identified the attacker. The completion of the PoR proof provides a way for users to check the backing of the 10 listed tokens at the October 31 snapshot, while the investigation and replenishment of the remaining affected assets continue.

Also Read: Binance Co-CEO Yi He Pushes Back on FTX Comparisons, Puts Security First


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *