Acala aUSD Depeg: What Happened and Where Recovery Stands

In August 2022, the Acala Network, a DeFi hub on Polkadot, suffered an exploit that involved its aUSD stablecoin. An attacker found a flaw that let them mint aUSD without the collateral the system was supposed to require. Reports from the time describe roughly 1.2 billion aUSD minted this way.

The key point is that aUSD did not fall because of a simple market shock or a bank problem. Its supply grew because the minting logic was abused. A stablecoin's peg depends on two things holding at once: the supply must be backed by real value, and the market must trust that backing. When unbacked tokens enter circulation, the peg has nothing to support it.

Coverage in public reporting describes a depeg of more than 99 percent over a weekend. A token meant to track one US dollar traded at a small fraction of that value. Tokens minted by the exploit could be sold into the market, which added downward pressure on the price.

The event also reached the wider Polkadot ecosystem. aUSD was used in other applications on the network, so holders who had aUSD in pools, lending markets or trading pairs faced losses or positions that could not be settled normally while the chain was disrupted.

The short version is this: an exploit created far more aUSD than the system could back, the price collapsed, and the Acala team responded by stopping activity on the network. The sections below explain what the team did, what remains unresolved, and how to judge the situation now.

A stablecoin is designed to hold a fixed value, usually one US dollar. Different designs try to achieve this in different ways, and each has failure points.

• Collateral-backed stablecoins hold reserves, such as cash, treasuries or crypto assets, that can cover outstanding tokens.
• Over-collateralized DeFi stablecoins lock more value than they issue, so a price drop in the collateral does not immediately break the peg.
• Algorithmic designs rely on supply changes and market incentives instead of full reserves, which makes them more fragile under stress.

All designs depend on the minting rules. If anyone can mint tokens without matching backing, the peg is at risk regardless of the design. Smart contract bugs, incorrect price feeds, weak access controls and thin liquidity can each turn a small error into a large supply problem.

When a depeg starts, confidence drops quickly. Holders try to exit, liquidity providers may be left with the wrong asset mix, and lending markets that accept the token as collateral can face bad debt. The price can then fall far below the target, as happened with aUSD.

For readers, the lesson is not that every stablecoin will fail. It is that the stablecoin's safety depends on its minting controls, its backing and its monitoring, not on its name or its past price history.

After the exploit became clear, the Acala team took several defensive steps described in public reporting and in community reports.

• The team halted or limited network activity so that further damage could be contained.
• Erroneously minted aUSD was frozen, so the bad tokens could not be moved or used in the same way.
• Investigators began tracing the transactions that created the excess supply, to separate valid balances from exploit-created ones.
• The team communicated with the community about the incident and the response.

Freezing is a blunt tool. It protects the network from further harm but also limits what holders can do with their balances. This is a trade-off that protocol teams face when a live exploit is in progress. Stopping activity can prevent additional mints, but it also delays normal use of the chain.

Tracing matters because the number of bad mints determines how much of the supply has no backing. Without a complete trace, a team cannot be certain which balances are legitimate. That is why the response was not a single action but a sequence of steps, with more work needed after the immediate freeze.

If you want to judge a similar incident, look for these signals: how quickly the team paused risky functions, whether frozen balances were clearly identified, and whether the team published a detailed account of the cause.

Public reporting shows that the freeze stopped the known erroneous mints, but they also show the work was not finished. The team stated that it was still working on a full trace to identify all remaining aUSD error mints. The community could then formulate proposals to resolve the issue.

This means several questions were open at the time of those reports:

• How many error mints existed in total, beyond the initial batch?
• How would frozen balances be treated, and who would bear the loss?
• Would aUSD be reissued with backing, or replaced by a different asset?
• What controls would prevent a repeat of the minting flaw?

A stablecoin is not saved by a freeze alone. A peg is restored only when the remaining supply is matched with backing that the market can verify, and when the rules that caused the problem have been fixed and tested. Restoring the price without restoring the backing would be a weak outcome, because the next confidence shock could reverse it.

So the honest answer to the headline question is that public reporting support a partial story: the network was halted, known bad mints were frozen, and a recovery process began through governance. They do not confirm that aUSD returned to its target value or that every remaining issue was closed. Readers should treat any claim of full recovery as something to verify directly.

Because prices and supply change constantly, this guide does not state a current aUSD price. Instead, use a structured check that you can repeat.

1. Confirm the official status from Acala's own communication channels, including any statement about the aUSD mint history and the recovery plan.
2. Look at governance records to see which proposals were submitted, which passed, and which were rejected.
3. Use a Polkadot block explorer to check total aUSD supply and recent mint and burn activity.
4. Compare the supply on chain with any published backing figures. If the team has not published backing, treat that as a warning sign.
5. Check price trackers for market value, but remember that a market price alone does not show whether tokens are backed.
6. Review whether any aUSD balances are still frozen and what the process is for releasing them.

When you review these sources, note the dates of each update. A statement from 2022 does not describe the state of the system in 2026, and a recent price chart does not explain the reasons behind it. Combine the sources before forming a view.

If you hold any aUSD or Acala-related tokens, avoid making decisions based only on social media posts or price moves. Verify public sources first, and be cautious about any offer that promises a guaranteed return on the token.

Community sentiment about Acala's recovery is mixed. Public discussion threads ask whether the network has recovered or whether the project is effectively finished. Those questions are common after a major failure, and they do not settle the matter either way.

The main reasons for doubt are straightforward. The aUSD incident was serious, the minting flaw was a basic design failure, and public reporting shows that the full accounting was still in progress for some time after the freeze. Holders who lost value have a reasonable basis for skepticism, and new users should weigh that history carefully.

The main reasons for continued interest are also straightforward. Acala remains a Polkadot-based DeFi network, and the team's response included a public trace effort and a governance process. Some community members argue that a transparent recovery can rebuild trust over time, if the backing and the controls are verified.

For a balanced view, separate three questions:

• Is the network operating and can users interact with it safely?
• Is any stablecoin on the network fully backed and verifiable?
• Has the minting flaw been fixed and tested in a way that outside reviewers can confirm?

Answering each question separately is more useful than a single yes or no about whether Acala is recovering or dead.

In September 2025, coverage in public reporting reported that Polkadot developers were weighing a new stablecoin proposal called pUSD. It was described as DOT-backed and algorithmic, and the same reports noted community doubts about Acala's history with aUSD.

A DOT-backed design would tie the stablecoin's value to DOT, the native token of Polkadot. Algorithmic elements would adjust supply to keep the price near one dollar. Both features raise questions that a reader should understand before judging any proposal.

• Collateral risk: DOT's price can fall sharply, which can weaken the backing and force liquidations.
• Peg mechanics: algorithmic supply changes can lag behind market moves, especially during stress.
• Governance control: the parameters that set collateral ratios and minting limits determine how safe the system is.
• Audit history: independent reviews of the code and the economic design are essential.
• Track record: a team that has had a serious exploit should show clear evidence of changes that prevent a repeat.

A proposal is not a product. Before using any new stablecoin, check whether the proposal passed governance, whether the contracts are live, how the collateral is held, and what the minting rules are. Be cautious of any claim that a new design will eliminate the risks seen in the past.

The aUSD case shows what can go wrong, but the same checks apply to any stablecoin. Use this list before depositing, trading or lending a stablecoin.

• Identify the backing: find out whether the token is backed by reserves, over-collateralized assets or an algorithmic mechanism, and where those assets are held.
• Find the minting controls: check who can mint new tokens, whether there are supply caps, and whether minting requires matching collateral.
• Read the audit reports: look for independent reviews and check whether the issues found were fixed.
• Watch the governance: see who can change parameters, how quickly changes take effect and whether there is a public record.
• Monitor supply on chain: a sudden jump in supply without matching deposits is a warning sign.
• Check liquidity: thin markets can turn a small sell into a large price move.
• Plan for exit: know how you would redeem or sell the token if the peg breaks.

For DeFi lending, also check how the protocol treats the stablecoin as collateral. A depeg can create liquidation risk for borrowers and bad debt for lenders. Diversifying across issuers and designs reduces concentration, though it does not remove risk.

This guide is general education, not financial advice. Stablecoins can lose their peg, and losses can be permanent. Only use money you can afford to lose, and check the rules and risks that apply in your jurisdiction before taking any position.