Asset Hub Migration - Staking FAQ

Resources & FAQs
1

Asset Hub Migration - Staking FAQ

The Asset Hub Migration of both, Kusama & Polkadot networks is currently planned for later this year. If you’re unsure of what the AHM is or why the team is planning this, then check out this thread here.

What is this topic for?

This topic will be for all AHM FAQ’s relating to Staking. We’ve pre-filled some FAQ’s below, however if your questions is not answered by any of these, please feel free to comment below and ask away.

FAQ’s

If a proxy/staking account pair already exists, will I still be able to use the proxy to perform actions such as nominate, bond, and other staking operations on behalf of the staking account? Will accounts that acted as proxies for staking on the relay chain will maintain this relationship on AssetHub?

  • Yes, all proxy relations will be migrated.

Should users nominate validators on the Relay Chain or on Asset Hub?

  • All functionality will move to Asset Hub, so in the future you will do your validator nominations on Asset Hub.

Will rewards be distributed separately for block production on each of these chains?

  • The staking rewards will be paid out on AssetHub, and they relate to the authoring points of relay chain validators.

Will the rewards for staking will also be part of Asset Hub? Will staking rewards show up also in the Asset Hub chain?

  • Yes. Post-AHM you must claim your staking rewards from Asset Hub.

  • This is the most immediate operational change for existing validators. Ensure your internal tools or processes are updated to interact with Asset Hub for reward payouts.

  • To help with this transition, Parity will be running a backend bot themselves to claim rewards for all existing validators for 30 days after migration so you don’t miss any rewards.

What is the main change for existing validators?

  • The primary difference for an existing Polkadot validator post-AHM is the split location for managing your validator session key vs. your staking operations.

  • You continue to set and rotate your session keys exclusively on the on your validator node synced to the Relay Chain, as you did before. Two notable differences for session keys post AHM are:

    • Setting session keys now requires a deposit
    • Session keys must be set by the stash account, and not the controller.

  • All staking-related transactions (for example, setting your commission preference via staking::validate) remain unchanged, but they are now executed on Asset Hub.

  • Other than that, your existing Relay Chain validator node (polkadot client) continues to run and function as before. More details can be found here.

Post-migration Validator Update

  • Please, find here a short guide to changes on your validator setup post migration.

Fast-Unstake Is Decommissioned

  • Fast-unstake was a mechanism added to Polkadot staking in 2022, allowing those who have bonded tokens, but are not actively nominating/validating in the last 28 days, to unbond quickly, without needing to wait 28 days. This feature is computationally too expensive to be hosted on a parachain, namely AssetHub, and is therefore decommissioned and will not be moved to AssetHub.

Will users need to re-stake again after the migration?

  • We’re looking into some kind of atomic migration, where everything happens at once. For example, for a single account we this could look like this:
  1. We unlock all assets that are currently held by any kind of utilisation on the relay chain,
  2. Teleport the assets from the relay chain to Asset Hub,
  3. And finally, lock and hold the same amounts and utilisation as before.

Will the staking rewards be interrupted in some kind of way?

  • No, your staking rewards should not be affected by the AHM in any way.

How will staking positions be displayed when funds exist on both chains?

  • Staking funds will not exist on both chains for a given account. However the migration will cause inconsistencies in the state, which will result in UIs displaying incorrect information.

  • Until the staking stage is complete, UIs should either maintain the previous display or show a loading screen or a link to information regarding the migration. Wallets will not be able to see the in-flight migration messages, and anything they display during the migration could be inaccurate. Therefore, the most sensible solution is to pause the display and show the old state.

How will nominator pools & validator transitions be managed?

  • They will be migrated along with everything else, since they’re nothing more but just another account.
5 Likes