hey, we don’t cover the smart contracts integration part. Please refer to this post or to the Paseo Element Channel with your question.
Timeline Update 
We’ve revised the project timeline based on our recent experience with the previous migration. Please refer to the updated version on this doc.
2 Likes
Will there be two paseo chains that run revive?
The current one Paseo Contracts chain(paraid: 1111)
and soon the paseo assethub?
Yes they will both contain pallet-revive, but not at the same time.
PAsset Hub - Contracts (para id 1111) is a temporary chain with a preview of pallet-revive on it for builders to test until Q4 when pallet-revive will be on Paseo Asset Hub. At that point PAsset Hub (1111) will be decommissioned.
More info in this post
3 Likes
Hy, dev team!
I am aware that balances are transferred by sudo in AHM.
Is a transfer event issued on the blockchain at this time?
I am following the TRANSFER EVENT for balance increases and decreases and am wondering if the AH balance will increase if I monitor the EVENT during the automatic transfer or if I should pre-populate the balance value myself.
I expect this will be a similar discussion during the re-transfer in December.
I’m not on the team doing this, but there is no sudo pallet on the relay chain or Asset Hub.
I don’t know what you mean by the re-transfer in December. I just re-read the document and I don’t see any mention of “re-transfer” or “December”.
The migration already occurred on Westend testnet, so my suggestion would be to check out what happens there to see what will happen during the migration.
Sorry, I must have misunderstood because it didn’t look like anything happened on westend’s explorer.
I understand that the AHM at Westend took place in the following block
From what I can see, no Transfer event occurred indicating a balance transfer.
In other words, I understand that if I am monitoring a TRANSFER event, the balance will not increase.
Please let me know if there is something I am understanding incorrectly.
I mean, you can see the migration occurred, as there are all 0 balances on the relay chain and actual balances on Westend Asset Hub:
Relay chain: Polkadot/Substrate Portal
Asset Hub: Polkadot/Substrate Portal
It’s not actually a transfer (i.e. going from one account to another) so I wouldn’t think a transfer event would be fired. And indeed, it looks like no transfer events were fire
I don’t know if any other event is fired, but you can check through the Westend history and see what happens or maybe someone from the migration team can chime in here.
In fact, the migration took place over several different blocks. It didn’t happen all at once at a particular block.
That is correct, and it’s actually a pretty good point IMO, as many tools and indexers rely on the events of the Balances Pallet (Balances.Transfer, Balances.Withdraw, Balances.Deposit, etc) to check how the balances of the different accounts are changing over time. That way they can just read the System.Events storage entry for each block and compute the diff themselves.
The migration did not trigger those events. Just like a System.set_storage transaction wouldn’t trigger those event, either. (it doesn’t matter if it comes from Sudo, or if it comes from Governance). Conceptually, the migration it’s just setting a state that comes from the relay-chain. The migration did trigger certain events like: MultiBlockMigrations.UpgradeStarted, PolkadotXcm.VersionMigrationFinished and MultiBlockMigrations.UpgradeCompleted (among others). However, I’m afraid that those events won’t be very useful to you.
Events are being emitted; we specifically considered CEXes and indexers in this case.
Check for example block #11716739:
The BatchReceived event indicates that 481 accounts are being integrated. You can see the NewAccount, Endowed and Minted events respectively. We are emitting all necessary events and not using set_storage ever. Please let us know directly where events are missing.
PS: Relay also emits the events, see block #26041706:
1 Like
Oh wow! Thanks for correcting me, I didn’t notice those events when I was following the migration! My most honest apologies 
Also, I was expecting to see these events reflected in my subscan test accounts, but they didn’t show up 
. Although, I guess that’s a subscan “issue”.
1 Like
The following two documents seem to differ in their ED descriptions at 0.1 and 0.01.
Also, I am not sure if the Westend-Assethub’s ED is also correct at 0.0001.
1 Like
The current ED on Asset Hub is 100,000,000 plancks = 0.01 DOT. Parity’s documentation is outdated.
The current ED on Westend Asset Hub is 0.001 WND.
Query const balances.existentialDeposit for both networks to obtain the value in plancks.
Thank you so much! You’ve been a great help.
1 Like
What are some risks that AHMs face and how can they be avoided?
(i) AHM implementation fails
(ii) Some problem occurs in Asset Hub after AHM and the chain stops.
My concern about (i) is if a problem occurs during migration.
If the migration is interrupted in the middle of the process, some addresses will have their assets migrated and others will remain in RelayChain.
Please let me know if the migration is such that all succeed or all fail.
Also, is there any way to know if my ADDRESS succeeded when partial success is possible?
Regarding (ii), am I correct in assuming that even if there is a problem with the Asset Hub after the AHM, it will not cause the balance to be returned to RelayChain?
If that were to happen, I am afraid that it would be difficult to distinguish between the balance that was originally in the Asset Hub and the balance that was transferred from Relay Chain.
It would be best if the AHM succeeds without any problems, but please let me know if there is any possibility of it coming back to RelayChain in the unlikely event that it does.
Asset Hub Migration Monthly Update
Timeline on hold
To accommodate some of our biggest partners we will be delaying the migration. We are currently in talks with them to find dates that will work for most of them. Please bear with us.
Migration Dashboard is live
https://migration.paritytech.io/ will give you a live update of the migration.
New guides
As a preparation for the upcoming migration, you can already set up your Sidecar environment now. Make sure to have the multi-chain configuration and meet the node requirements (as described in the guide) - some endpoints will not work with Asset Hub post-migration without this setup.
After migration, the location for managing your validator session key vs. your staking operations will be split between Asset Hub and the Relay Chain. Please, follow this guide for more information.
7 Likes
Thanks for the update!
I have not accepted Google’s ToS and consequently I do not have an account. I therefore cannot access this Google Docs requiring an account.
Thank you for pointing it out, I’ve updated the link to this one. Please, let me know if that works.
2 Likes
Asset Hub Migration Monthly Update
New timeline confirmed
Thank you all for your patience. After reviewing the timeline with our critical partners and coming to an agreement, we are moving the migration to:
-
Tuesday October 7th for Kusama, and
-
Tuesday November 4th for Polkadot.
Please find attached documents to assist you with the migration.
If you have any further questions, come back to us via our main communication channel or the Asset Hub Migration Support Chat.
6 Likes
Impact on end users during the migration
- During the migration, balances may show incorrectly depending on which wallet you use
- Users can’t teleport to and from the Relay Chain or Asset Hub (or send any XCMs), they can’t make transfers on Relay Chain BUT they can transfer DOT balance and Assets on Asset Hub
- Staking, Governance and some miscellaneous pallets incl proxies, multisigs, vesting and more (see pallets list + further pallets which change the state of the ones listed) will be locked on the Relay Chain for the duration of the migration. Pallets being migrated will be locked on Asset Hub until the migration is complete.
The migration should be seen as downtime on the Relay Chain for end users.
The migration overall will take approx. 8-10 hours, TBC after dry runs and benchmarks.
4 Likes
Dear @joyce,
For Vault users, is this still valid ? AssetHub migration for Parity Vault users