1. Responsibility is on me. I didn't implement multisig bridge ifra 5 years ago. I understood the risk, but delayed bridge restructuring due to not unimportant reasons
2. This incident has nothing to do with the main business. Our experts are the best in the field
3. The most significant damage is to reputation. However, our solo chain CEX infra prevented bigger harm, and I recommend other token founders to follow it
4. We have a snapshot of BSC and ETH $HAI. All BSC and ETH tokens bought after the hack will not be supported in the new tokenomics
5. Our goal was always to convert $HAI into a security token that represents Hacken equity and has crypto flexibility. Now is the time to accelerate the idea implementation
6. What doesn't kill makes stronger. My wife told me I have quite a few grey hairs overnight. I have more bad news for her - no vacation, but very hard work to recover reputation
@hackenclub@buda_kyiv We should turn HAI on BSC into a MEME coin to commemorate the attack on Hai, which will also give HAI holders a satisfactory response.
The recent $HAI security incident was not a hack, but a human error during architectural changes.
A recap of the AMA with @buda_kyiv clarifying the details, what we know now, and how we’re moving forward 👇
Its bridge private key compromise. Worst day
$HAI solo chain design at CEXs allows us to make a snapshot of other chains and make fair compensation
Price drop is the biggest hit in the short term
Not an issue long term
@DEGA_org We're thrilled #eduardodcerrato has emerged victorious in the DEGA MATCH. Battle-6 - 69. Join the movement for decentralized creativity by following @DEGA_org now!
@DEGA_org We're thrilled #IssaFunez has emerged victorious in the DEGA MATCH. Battle-8 - 27. Join the movement for decentralized creativity by following @DEGA_org now!
@DEGA_org We're thrilled #FIRESDA has emerged victorious in the DEGA MATCH. Battle-5 - 56. Join the movement for decentralized creativity by following @DEGA_org now!