The post IoTeX commits to 100% compensation plan in hack recovery plan appeared on BitcoinEthereumNews.com.

The IoTeX Foundation has committed to providing full compensation to all users affected by last week’s $4.4 million bridge hack, as they pledged to use treasury funds to restore victims, whether or not IoTeX is able to recover the stolen assets from the attacker. The announcement came from their third incident update, following IoTeX’s mainnet resuming full operations on February 24, after two days of security upgrades that permanently blacklisted 29 hacker addresses and froze around 45 million IOTX tokens. The hack led to an immediate price dump of around 22%, dropping from $0.0054 to around $0.0042. The token has staged multiple attempts to reclaim pre-hack valuations, trading around $0.0048 currently. IOTX price has returned in the green since the project committed to $100% refunds to affected users. Source: CoinMarketCap Treasury-funded compensation regardless of recovery outcome In its latest report, the IoTeX project stated that “The IoTeX Foundation will ensure every affected user receives 100% compensation.”  They also developed a compensation framework dividing users into two tiers.  Tier 1 covers losses up to $10,000, which represents the vast majority of victims. They will receive full compensation immediately in stablecoins or native Ethereum assets. Tier 2 users with losses over $10,000 would receive their first $10,000 immediately, and their balances would be distributed over 12 months. They would also get a 10% bonus in annually staked IOTX, allowing them to receive 110% of their original losses. The compensation process will begin on Friday, February 27, when IoTeX publishes its official Recovery Deposit Address and Claims Portal.  Affected users must withdraw any bridged assets from DeFi protocols, transfer them to the Recovery Deposit Address in single transactions by asset type, and then submit claims with wallet addresses and transaction hashes. The Foundation will then verify each claim against on-chain data before issuing…

---

Filed under: News - @ February 26, 2026 2:41 pm