SAFU

"SAFU" came from this video: youtube.com/watch?v=DelF6zEH…

It's a feature everyone (who have assets on a platform) will need once. Self custody requires quite a bit more setup to get this right. I talked about it in "Keep Your Crypto #SAFU (CZ's Tips)" blog post.

Another crypto KOL kidnapped in France. Stay SAFU. Don't share your location. cointelegraph.com/news/kidna…

Not a competition. Keep building! (Deleted the previous retweet as I didn't notice it contained a CA, which our security team flagged as super high risk, lack ownership transparency, etc. Can't be too careful these days. Stay SAFU.🙏)

Spent the Sunday updating this security tips article from 5 years ago. Shrunk it from 5500 to 4300 words. If you haven't read it before, I recommend reading it. It might just save you from a hack (that you never know because you avoided it). Stay SAFU! binance.com/en/square/post/2…

Some thoughts on the recent hack(s). There is a pattern where hackers were able to steal large amounts of crypto from multi-sig “cold storage” solutions, as with ByBit, Phemex, WazirX and potentially others. In the most recent ByBit case, the hackers were able to make the front-end user interface show a legitimate transaction while the actual signing was for a different transaction. I am less familiar with the other cases, but they sound similar based on limited available info. What’s more scary is that the affected exchanges used different multi-sig solution providers. The hackers, the Lazarus Group, are highly advanced and broad in their abilities to penetrate. It is still unclear whether the hackers were able to penetrate multiple signing devices, or the server side, or both in each of these cases. Some people questioned my suggestion of halting all withdrawals as a standard security precaution (in a tweet I posted from a shuttle bus to the plane). My intention was to share a practical approach based on my experiences and observations, yet there is no absolute right or wrong in either approach. My guiding principle is always to lean on the safer side. After any security incident, pause everything, make sure we fully understand what happened, how hackers penetrated the systems, which devices were compromised, triple-check all is safe, and then resume operations. Pausing withdrawals could cause more panic, of course. In 2019, we paused withdrawals for a week after a massive $40 million hack. When we resumed withdrawals (and deposits), we saw more deposits than withdrawals. Not saying this is a better approach. Every situation is different. It’s a judgment call. My tweet was to share what might work and my intention was to show support in a timely manner. I am sure Ben made the best decision based on the info he had. Ben did a good job maintaining transparent communication and calmness in dealing with a challenging situation. That shows a sharp contrast to other less transparent CEOs, like WazirX, FTX, etc. The cases mentioned here are all different. FTX was fraud. WazirX, I will refrain from commenting as there is an ongoing lawsuit. Most importantly, we should never take security for granted. It is important to learn about security yourself so that you can choose the right tools for your needs. For this, I will share an article I wrote a few years ago. It’s a little outdated, but the fundamental concepts still apply. Stay SAFU! binance.com/en/blog/from-our…