There are several partial mitigations, but nothing would be perfectly seemless. I’m unsure if anybody started work towards any of the mitigations either.
This is just how Vault works, yes. It has always been a pain to use it with parachains.
Thank you, development team, for all your hard work.
I’m truly glad that the AHM date has been set.
However, I still don’t have enough information to proceed with preparations for AHM.
I would appreciate it if you could answer a few questions:
- What time on November 4 will AHM begin? If the time hasn’t been finalized yet, when do you expect to confirm it?
- When will the final release notes for the Polkadot SDK and polkadot-api for AHM be published? Will they be available before the Kusama run on October 7?
- At what time will the vote to execute AHM start, and when will the final decision be made?
- I understand that the following dashboard is used to track AHM’s progress. Will it also notify us when AHM has successfully completed?
https://migration.paritytech.io/ - Since the original date of September 15 was postponed to November 4, we’re worried there might be another delay. Rescheduling is common in system development, but could you tell us how likely another postponement is and by when such a decision would be made if it happens?
- My understanding is that AHM will be released in three phases. After November 4, have the concrete dates been finalized for phase two (migration of balances) and phase three (removal of the Balances pallet)?
What time on November 4 will AHM begin? If the time hasn’t been finalized yet, when do you expect to confirm it?
We will announce this as soon as the block number for the migration is confirmed. This will be determined by the Polkadot Fellowship via a referendum, and the date will be finalized when it has been opened for voting.
When will the final release notes for the Polkadot SDK and polkadot-api for AHM be published? Will they be available before the Kusama run on October 7?
Yes, the release notes for the polkadot-sdk unstable2507 will be published, as well as the fellowship runtimes notes with the release of v1.8.0, which will be the Asset Hub Migration release.
At what time will the vote to execute AHM start, and when will the final decision be made?
We will share the link to the referendum as soon as it is created. For Kusama, the referendum must be submitted 14 days in advance for the runtime upgrade. This will update to the code that is needed about a week before, then the migration is triggered by a separate Fellowship referendum.
I understand that the following dashboard is used to track AHM’s progress. Will it also notify us when AHM has successfully completed?
https://migration.paritytech.io/
You will be able to see when the migration has finished, as well as being able to follow key metrics and progress along the way.
Since the original date of September 15 was postponed to November 4, we’re worried there might be another delay. Rescheduling is common in system development, but could you tell us how likely another postponement is and by when such a decision would be made if it happens?
The timeline will only be adjusted if critical issues are identified following the Kusama deployment. Any such changes would be communicated promptly after the migration. We do not expect this to happen. The initial delay was made in response to stakeholders who were finding it difficult to make all changes required in time for their compliance windows (letting their customers know sufficiently far in advance).
My understanding is that AHM will be released in three phases. After November 4, have the concrete dates been finalized for phase two (migration of balances) and phase three (removal of the Balances pallet)?
The Asset Hub Migration will be fully executed on November 4th (for Polkadot) in its current scope. Once the migration is complete, we will address remaining technical debt in those following phases. This includes the removal of the final pallets with a balances dependency (HRMP and Parachain registration, as well as proxies and multisigs for those operations). This was previously communicated as the final phase 3 goal. The exact timeline for these final steps will be communicated after we have scoped out the work required and when we have a solid idea of rollout timelines around our bigger commitments: on the successful launch of Smart Contracts and this phase of AHM.
3 Likes
Thank you for your thoughtful response.
Our concerns about AHM have been greatly alleviated!
We look forward to the development team continuing to provide us with information about AHM.
1 Like
In Polkadot Vault 7.1 users will be able to sign operations in any chain from already derived keys. There will be no need to issue separate keys with the same derivations in AH. In other words, they can use the same keys that they have already issued for Polkadot or Kusama.
2 Likes
Migration Dashboard is live
https://migration.paritytech.io/ will give you a live update of the migration.
Is this one for Polkadot or Kusama? Seems can’t select network
Right now the dashboard is not showing neither since the migration hasn’t started yet, but we will add an option to select networks
1 Like
Hi, development Team
I have a question regarding balance handling.
On the Relay Chain, 1 Planck was uniformly set to 10^-10.
On the Asset Hub Chain, 1 Planck has been changed to 10^-8.
I am concerned about the following two points:
- Will quantities in the 10^-10 unit from the Relay Chain era not be migrated to AHM?
- On the Asset Hub Chain, can only quantities of 10^-8 or greater be transferred?
How did you get to that conclusion?
Polkadot Relay and Asset Hub both have 10 decimals. Kusama has 12 decimals on both chains.
Asset Hub Monthly Update
Asset Hub Migration Support Article
We’ve published an article explaining what the Asset Hub Migration is and what it entails on Polkadot Support. This article aims to cover end-users’ doubts and warns them about the migration.
Sidecar update - Tracking Asset Hub state by Relay Chain block number
We’ve introduced a new query parameter in Sidecar (version 20.5.0 and above): useRcBlock. When enabled, it returns all Asset Hub events and transactions that occurred in a given Relay Chain block.
This is particularly useful for anyone who wants a consistent way to track Asset Hub activity in alignment with Relay Chain blocks. Continuing to use Relay Chain blocks as the reference allows you to maintain a single block height reference for the entire Polkadot network.
Looking ahead, once Elastic Scaling is enabled (using multiple cores for a single chain), this parameter will return aggregated transactions and events from all Asset Hub blocks included within the given Relay Chain block (i.e. there could be multiple Asset Hub blocks per Relay Chain block).
Please, find here the updated guide for the usage of useRcBlock.
New Forum Category: Resources & FAQ
To streamline your experience, we’ve added a FAQ category to the forum. You’ll find threads dedicated to specific migration subsystems there. Parity contributors, specialized in each topic, monitor the threads and provide answers directly within them.
Warning if you’re using transfer_assets 
The transfer_assets extrinsic will change behavior with the upcoming Asset Hub Migration. If you don’t update, some cross-chain transfers may start failing. Read more about this here.
Paseo was updated 
We successfully migrated to Asset Hub on August 27th. We are now conducting AMAs and gathering feedback from those affected by the migration. This will help us prepare and fine-tune the upcoming Kusama migration. Let us know if you have anything to report, or if something doesn’t look quite right in a tool that you use.
3 Likes
Asset Hub Monthly Update
Upcoming: Kusama Asset Hub Migration
The Kusama Asset Hub Migration will take place at Block Nr. 30,423,691, which means around 11 AM UTC on Tuesday, Oct 7th. You can see the referendum up for vote here. The migration might take up to 6 hours, you can follow the progress on the Migration Dashboard.
Important for dapps!
Parachains will transition their DOT/KSM reserves from the Relay Chain to Asset Hub at different times, which may temporarily break cross-chain transfers.
Since automatic reserve detection is no longer reliable, dapps must implement a mechanism to dynamically determine the correct reserve or risk failed transfers during the transition. More details can be found in this forum post.
Kusama Asset Hub Migration Report
Migration Overview
Migration Date: October 7, 2025
Duration: 3 hours, 13 minutes, 18 seconds
Block Heights
Relay Chain
- Start Block: #30,423,691
- End Block: #30,425,590
- Block Difference: 1,899 blocks
- Average Block Time: 6.11 seconds
Asset Hub
- Migration Start Block: #11,150,168
- Migration End Block: #11,151,931
Migration Metrics
Pallets
Around 25 pallets have been migrated/removed, including Governance, Staking, and Society modules, as well as Treasury, Bounties, Proxies, and account recoveries.
Accounts
- Total Accounts Migrated: 348,210
Storage
- Total Storage Entries Migrated: 841,219
Staking Data
- Number of Stakers Migrated: 25,784
- Staked KSM Migrated: 8.3492 MKSM
- Raw Amount Migrated: 8,349,228,738,587,204,002
Asset Migration
- Total KSM Migrated: 17,127,445.03 KSM
Technical Metrics
- Total Data Size Migrated: 117.96 MB
- XCM Messages Sent (from Relay Chain): 3,043
- XCM Messages Sent (from Asset Hub): 3,067
17 Likes
My 204 $KSM is currently missing or disappeared from my trust wallet address: HrdSnuQQALvw5R6M7WnZapxy74czm2adko9jVXd3rGVA3YH
Please I need this fixed ASAP. my balance is zero and everything appears zero, no traces of transaction, and I believe this is due to your migration/upgrade. This is my life savings and can’t afford to lose my asset. I’m a poor man trying to build. PLEASE
Perhaps a problem with the wallet not being updated yet? No idea about trust wallet, it might need a change in the configuration or something but your funds are there.
Don’t worry, your assets are safe. The balances were moved from the Relay Chain to Asset Hub and the wallet provider most likely hasn’t changed their endpoints yet. I can see your 205 KSM on Asset Hub: Subscan | AssetHub Kusama Account Details
edit: didn’t see you responded already, @olanod 
We’re in touch with TrustWallet to update their Endpoints, thank you for raising the issue.
Hi Joyce!
Thank you for supporting this long awaited migration. We are working on supporting it in our wallet.
Could you please let me know how exactly does the endpoint update look like? We are experiencing the same issue: can’t switch from Relay to Asset Hub for Kusama, facing zero balances.
Failed to find any exact information related to API update. Would be grateful for sharing.
Thanks in advance.
Hey,
you can see in the Sidecar Asset Hub Migration guide how to connect with Kusama Asset Hub.
If you want to quickly check an endpoint, you can use this public instance:
https://kusama-asset-hub-public-sidecar.parity-chains.parity.io
Important: This endpoint is only for ad-hoc testing and NOT for production use .
In production, you should run your own Sidecar instance (locally, via Docker, or any setup that fits your environment) and configure it correctly.
Configuration
Sidecar uses an .env file for configuration.
- If you only need Kusama Asset Hub (KAH) endpoints:
SAS_SUBSTRATE_URL=wss://kusama-asset-hub-rpc.polkadot.io
- If you also need endpoints related to both KAH and the Relay Chain (as described in the Sidecar Asset Hub Migration Guide):
SAS_SUBSTRATE_URL=wss://kusama-asset-hub-rpc.polkadot.io
SAS_SUBSTRATE_MULTI_CHAIN_URL='[{"url":"wss://kusama-rpc.polkadot.io","type":"relay"}]'
Let me know if that helped, otherwise join our Asset Hub Migration Support Chat where you can get technical support.
2 Likes
1 Like