According to official announcements from IoTeX, the IoTeX mainnet has fully resumed operations as of February 24 at 06:06 UTC. Prior to this, the IoTeX team, in collaboration with node representatives, deployed the Mainnet v2.3.4 security upgrade, permanently freezing approximately 45 million IOTX across 29 attacker wallets. Although the attackers minted 410 million CIOTX, 99.5% of these assets have been frozen or locked. The actual financial loss amounts to approximately $4.4 million, with the attackers converting these assets into 66.78 BTC, currently held across four Bitcoin addresses. The IoTeX Foundation commits to providing 100% compensation to all affected users from the Foundation’s treasury and has formally reported the incident to U.S. law enforcement authorities.
IoTeX Mainnet Fully Restored After Hack, 100% Compensation Promised
TechFlowShare
Summary
IoTeX mainnet fully restored after a crypto hack, with operations resuming on February 24 at 06:06 UTC. The team deployed Mainnet v2.3.4 to freeze 29 attacker wallets containing approximately 45 million IOTX. Over 99.5% of the 410 million CIOTX minted in the exchange hack have been locked, with estimated losses of $4.4 million. The attacker transferred assets to 66.78 BTC across four Bitcoin addresses. The IoTeX Foundation has pledged full compensation from its treasury and has reported the incident to U.S. authorities.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.