Public blockchain records, while transparent about fund movements, cannot definitively reveal the effectiveness of an exchange’s internal security controls, a critical point highlighted by the recent Binance security incident involving approximately $6.3 billion in assets. Experts emphasize that these on-chain records are insufficient to assess the internal signing controls or transaction limits that could have mitigated losses.
Binance reported that attackers accessed an internal wallet-signing service to move funds from its hot wallet, bypassing normal withdrawal processes. The incident affected assets across 10 blockchains, with attackers repeatedly draining a hot wallet on Ethereum as new deposits arrived. The total value of affected assets is reported to be $6.3 billion. While Binance co-CEO Richard Teng reported on October 30 that the attack affected the exchange’s own hot wallet, many technical details remain confidential to prevent further attacks, and the exchange did not respond to questions about its wallet balances and safeguards.
The Limits of On-Chain Transparency
Blockchain records can show funds moving, but they cannot establish an exchange’s internal signing controls or transaction limits, according to analyst Jonathan Riss, who spoke with Cointelegraph. When attackers can obtain valid signatures, their potential access depends on what the signing system allows them to transfer over time. A wallet’s balance at a single moment does not capture its full exposure. Transaction limits enforced by the application requesting a signature can be bypassed if that application is compromised, Riss explained, though limits enforced independently by the signing system may still restrict transfers.
Internal Controls: The Unseen Safeguards
Most customer assets are held in offline cold storage and are moved to hot wallets only when users request withdrawals. Exchanges typically keep enough funds in hot wallets to cover a few days of expected withdrawals, often representing a low single-digit percentage of assets under management. Hot wallets generally process withdrawals automatically, but replenishing them from cold storage should require a separate treasury decision and manual approval. Controls applied before signing, including transaction limits, approved withdrawal addresses, and additional authorization requirements, can help contain losses when a system is compromised, according to Eugene Hahr, chief product officer at BitGo.
Industry Context and External Verification
However, assessing these internal controls from the outside is challenging. “A comparison with other exchanges isn’t really possible from the outside,” Riss added. “Public information on internal signing architecture is limited everywhere, and reserve distribution and proof-of-reserves attestations show what sits where, not how a withdrawal is authorized.” The notable move of custody arrangements is a question Binance is best placed to answer, said Idan Ofrat, co-founder and chief product officer at Fireblocks.
While rivals including Coinbase, Gate, and Upbit have disclosed their cold-storage ratios following the incident, this information does not provide insight into the internal signing mechanisms or transaction limits that govern fund movements. The $6.3 billion figure represents the cumulative value of assets affected across 10 blockchains, with attackers repeatedly draining a hot wallet on Ethereum as new deposits arrived. The exact amount of funds attackers could access and the specific technical details of the attack remain among the uncertainties surrounding the incident.
Why This Matters
The materials describe a narrow update: Attackers accessed an internal wallet-signing service to move funds from Binance’s hot wallet, bypassing normal withdrawal processes. Binance’s internal signing controls.
