Binance Expands Proof of Reserves to 44 Tokens After Hack

Binance Expands Proof of Reserves to 44 Tokens After Hack

N
News Editor
2026-11-04 15:38:12
Binance said it has replenished about 98% of the assets affected by a hack and has expanded its proof-of-reserves coverage to 44 tokens. The exchange, however, said its new cryptographic proof is still not finished. Withdrawals also have not fully reopened. According to The Defiant, the update outlines both the progress Binance says it has made and the limits that remain in place. While most of the affected assets have been restored, the reserve verification work is still incomplete, and users are still waiting for a full reopening of withdrawals. The report centers on Binance’s post-hack recovery status and the exchange’s effort to broaden reserve transparency across more tokens.

Binance said it has replenished about 98% of the assets affected by a hack and expanded its proof-of-reserves coverage to 44 tokens.

The exchange also said its new cryptographic proof is not yet finished, and withdrawals have not fully reopened.

Recovery update after the hack

According to The Defiant, Binance described the replenishment of affected assets as roughly 98% complete. At the same time, it has widened proof-of-reserves coverage to 44 tokens.

That said, the exchange noted that the new cryptographic proof remains unfinished. Withdrawals, meanwhile, have not been fully reopened.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
4800

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.

Binance Expands Proof of Reserves to 44 Tokens After Hack | Bit.Fan