# XCM issue affecting Asset Hub

**URL:** <https://forum.polkadot.network/t/xcm-issue-affecting-asset-hub/19126>\
**Category:** Ecosystem\
**Created:** [October 26, 2026, 9:44pm UTC](https://forum.polkadot.network/t/xcm-issue-affecting-asset-hub/19126 "2026-10-26T21:44:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bkchr](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/bkchr/32/27_2.png) [@bkchr](https://forum.polkadot.network/u/bkchr)\
**Post date:** [October 26, 2026, 9:44pm UTC](https://forum.polkadot.network/t/xcm-issue-affecting-asset-hub/19126/1 "2026-10-26T21:44:59Z")

</div>

Over the weekend, the Polkadot Technical Fellowship discovered an XCM issue and executed a whitelisted caller referendum to resolve it.

The underlying bug has been fixed, and the impacted assets were moved to a controlled account to prevent further extraction.

It did not affect user wallets or funds. No action is required.

The XCM error on Polkadot Asset Hub caused a supply accounting discrepancy, creating a pricing imbalance in the liquidity pool and resulting in losses to the Polkadot Treasury’s liquidity provisioning position.

The bug affected XCM messaging and caused approximately 4.06 million dotUSD to be incorrectly removed from the recorded token supply. Although the recorded supply decreased, the corresponding dotUSD tokens remained in the DOT/dotUSD liquidity pool.

Arbitrage traders targeted this pricing imbalance, which resulted in an estimated $1.3 million reduction to the Polkadot Treasury’s liquidity position.

An OpenGov referendum proposing the necessary corrective actions will follow shortly, alongside a full technical post-mortem.

---

<div class="post-metadata">

**Author:** ![bkchr](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/bkchr/32/27_2.png) [@bkchr](https://forum.polkadot.network/u/bkchr)\
**Post date:** [October 27, 2026, 10:18pm UTC](https://forum.polkadot.network/t/xcm-issue-affecting-asset-hub/19126/8 "2026-10-27T22:18:46Z")

</div>

Following yesterday’s update on the XCM issue affecting Asset Hub, [Referendum #1961](https://polkadot.subsquare.io/referenda/1961) has now been submitted.

The referendum proposes two changes:  
Restore dotUSD’s recorded supply to match existing balances, without changing individual holdings.  
Restore Snowbridge functionality by reverting inaccurate execution weights introduced in the latest Bridge Hub runtime upgrade.

We will continue to share updates as the process progresses.  
A full post-mortem will follow.