технология

Acala Network USD стабилкоининде 2.7B күйүп кеткенден кийин ишин улантат

09/27/2022
Bitcoin Ethereum Маалымат

After the mining failure involving its stablecoin, aUSD, the Acala Network announced on Monday that it had resumed its operations following a referendum allowing liquidity pools (LPs) to withdraw liquidity from pools or unstake LP tokens.

In August, a misconfiguration of the iBTC (IBTC)/aUSD liquidity pool led to a 3.022 billion aUSD to be erroneously minted, taking its price to less than $0.01 from its United States dollar peg. Acala is a борборлоштурулган каржылоо (DeFi) platform built on the Polkadot ecosystem.

Image

The wallet addresses that had received the minted aUSD have been identified via on-chain tracing, allowing the recovery of 2.97 billion aUSD mistake mints from 16 addresses. Other thirty-five accounts were identified as having acquired 12.38 million erroneously minted aUSD.

боюнча to the incident report, 16 IBTC/aUSD LP contributors received the error mints, and some of them repeatedly added more liquidity to the pool, claiming more aUSD error mints and resulting in more aUSD being erroneously minted. It noted:

"Бул колдонуучулардын кээ бирлери бассейндердин дисбаланс өскөн сайын бир доллар катасы менен бир нече жолу алмаштырышты. Андан кийин алар бир USD катасынын олуттуу көлөмүн башка XCM менен байланышкан чынжырларга жана CEXтерге өткөрүп беришти.

The cause of the incident “was a vulnerability in the DEX saving code that is part of the incentives pallet,” said the company, which also announced a security roadmap to strengthen the security of the Acala network. 

The report revealed the full extent of the event. Reportedly a total of 3.022B aUSD errors were minted, 2.97 billion aUSD were found in the addresses of the 16 identified LP contributors and 12.38 million aUSD error mints were found on the top 35 accounts that acquired a significant amount of aUSD error mints or were linked to the accounts that acquired it. A remaining 52.068 million aUSD error mints, error mint-swapped tokens and addresses involved in the incident were identified.