Thread by @cz_binance

A few reflections on this "incident" handling. Different information sufficiency, different choices, different impacts.

A thread: 1/9

https://twitter.com/cz_binance/status/1546624143432433664

2/ I could have waited until I got the private contact info for the Uniswap team. It would have avoided any public "panic". But if this was a real exploit, millions or billions more could have lost during that time.

3/ Speed is of the essence when dealing with security issues, when (3 million users') funds are at stake.

4/ Whenever our security team messages me about an exploit, I go into hyperdrive. It's always better to err on the side of abundance of caution.

This is our internal chat.

5/ I messaged Vitalik, I could wait for him to respond... but

I pulled the trigger (posted the tweet) before our security team even confirmed. I can always delete/apologize if wrong. My image may take a hit, but better than more people losing money.

6/ We have to make decision with incomplete information, and try to strike the right balance.

This was 12:45am (mid night). And I just came home from a gala dinner.

7/ The community responded quickly. Within minutes, I was put in touch with Uniswap teams. By 1:02AM, the issue was confirmed by both teams to be a Phishing attack.

And I realized I needed to "update" my tweet, which I did immediately.

8/ in my defense 😂, I even added the word "potential exploit" to my original tweet just to be cautious.

Message from our team (left). And my tweet (right).

9/ By 1:04AM, it was done. This is how decentralized teams work together. We never spoke before, but still keeping each other #SAFU. 💪