Worried about how the hackers assets got freezed on @SuiNetwork from today’s hack?
This post explains it from a non technical perspective so do well to RT for frens.
Let’s break it down 🧵
Some folks are asking: “If assets can be locked, is Sui really decentralized?”
Here’s how it actually works 👇
1. In rare, large-scale exploits like today’s @CetusProtocol incident, Sui validators can come together and reach consensus to deny transactions from specific malicious wallets.
This prevents the attacker from moving stolen funds.
2. ⚠️ This isn’t automatic and isn’t centralized control.
Two key things make it decentralized:
•It only happens in extreme cases (like major hacks)
•It requires broad validator consensus to take effect
3. Think of it as an emergency brake — only pulled when a lot of independent actors agree it’s necessary (as the case was today).
This protects users and LPs, while still preserving decentralization.
4. 🔧 For developers who want to dive deeper, here’s the relevant code in Sui’s repo:
https://t.co/xKFAhfwKqa
5. In summary:
✅ Sui is decentralized
✅ The network is secure
✅ Asset recovery tools exist — used with caution and consensus.
@SuiNetwork@EmanAbio how can I make sure the various Protocols using $SUI's zkLogin make use of the same wallet address?
SuiWallet
0x...60
Bluefin
0x...e9
Tusky
0x...07
Any way to control which address is used when connecting to a protocol?