Binance @cz_binance @heyibinance defended the situation well. But I think they can also do many things better. In my opinion, the team isn't ready for major problems. Here's why: 1/ In a multi-billion-dollar exploit, every second counts. The fact that the attacker triggered roughly 50 unauthorized transactions means the automated system failed to detect anomalous volume and instantly freeze the network. 2/ During the initial hours of a major exploit, a lack of clear, immediate communication creates panic. When users see funds moving on the blockchain before an official statement or withdrawal freeze is implemented, it creates the impression that the team is scrambling without a plan. 3/ A large portion of the "success" in containing this hack relied on external stablecoin issuers (like Tether and Circle) stepping in to freeze the assets on-chain, rather than Binance's own internal circuit breakers stopping the outflow at the source. 4/ Instead of stopping withdrawals first, they should stop deposits. Doing so during an active exploit presents severe trade-offs. If Binance's system had frozen everything automatically at 4:30 AM HKT instead of forcing their team to execute a delayed manual intervention at 6:00 AM, they could have salvaged nearly the entire multi-billion dollar sum internally. I could be wrong on this. This should be weighed properly 5/ Official statement only came out 10.30 AM. This should be done more timely, honestly. 6/ A multi-billion-dollar financial pipeline should never have a single point of failure where a single employee's machine can act as an unrestricted master key. The internal operations need to make changes. As much as I love Binance, I do not blindly follow. This is my 2 cents' worth. This is also a suggestion, food for thought.