You can also take a look at this GCSA analysis: It perfectly corroborates Binance's investigation update released this afternoon: The initial suspicion of a single point of attack on DevOps laptops was incomplete; subsequent investigations uncovered other possible entry points, classifying it as a complex attack. The root cause is still under investigation. The current stance is: 1️⃣ SAFU + company funds cover all losses; user funds are safe. 2️⃣ Withdrawals are proceeding as planned and will resume within approximately 45 hours; deposits are unaffected. 3️⃣ Funds flowed out after the withdrawal suspension. I've reviewed the full GCSA investigation report: It independently reviewed the relevant on-chain transactions on Binance 14/50 EIP-7702 authorized signatures. I think the most valuable aspect is that it provides a perspective: 50 valid EIP-7702 signatures ≠ guaranteed private key leakage, and ≠ all 50 transactions were executed. Security cannot focus solely on private keys; it must also consider who can initiate signing, how permissions are approved, and whether the system can be promptly shut down if the terminal is compromised.