# Asset Hub Migration
## Parachains AMA

Dónal Murray / `seadanda`

---

## Overview and aims

- tl;dr: The main goal is to migrate all the staking, governance and balances functionality from the Relay Chain to Asset Hub at minimal cost and risk to our integrated partners.
- Average end users should interact only with AH, and be unaware of anything else behind the scenes
- Migration will not require end user intervention

---

## Motivation

- Core objective of Polkadot: do everything on parachains.
- Originally things were done on relay as we didn't have parachains yet.
- [RFC-32](https://polkadot-fellows.github.io/RFCs/approved/0032-minimal-relay.html) maps out path to a minimal relay
- Minimal relay: move everything to parachains
- Iteration on this: move everything to the Asset Hub parachain

---

## Motivation
- Simplifies end-user tasks and also UX/DX
- Lower ED, fees and deposits
- Paired with contracts on AH unlocks great interoperability

---

## Motivation

- Great overview in [this doc](https://docs.google.com/document/d/1SCT2WB6P8HzlLFZx4eEMPtb3GZkE4Ve7yTo8EsYkvVI/edit?tab=t.0)

---

## What's actually moving?
- Governance (incl treasury)
- Staking
- Misc functionality with Balances dependency (except parachain registration)*

---

## How? (high level)
- Add functionality to AH
- Special supervisor pallet to handle migration of state via XCM during one special session
- Balances: Account by account, unlock, transfer, re-lock
- Pallet states: chunked basically 1to1 replication
- Referenda calls: converted where possible
- Extrinsics to recalculate deposits/locks (decreasing) called by bots

---

## Implications specific to parachains
- From parachain perspective: not many
- Reserve Location of DOT moving to AH*
- Governance done on AH instead of RC, but the same API
- Staking also being upgraded to multi-block since it now runs on a parachain - slightly different internals, largely same API
- Timings will be done based on Relay Chain Block Number - also allows 6s blocks with async backing
- The [FAQ](https://docs.google.com/document/d/1XR3vL2p4QV0wC7FrlC8eN-q62BqNFTFElbj21wEmMGg/edit?tab=t.0) will be updated as we go
- We'd love to hear from you about any edge cases

---

## Implications for gov proposals
- At the point of the migration ongoing refs will of course be affected.
- Three groups:
- Easily mapped calls, like treasury payments
- Calls that can be wrapped in an XCM transact and sent back to the relay chain to execute as originally intended
- More complex cases (dropped)
- We'll publish a full list of supported calls in advance of the launch

---

## Timeline
- All pallets being moved at once
- End of year: clarity on starred items throughout this pres
- Deployment driven largely by release cadence
- Q1 Westend (and Paseo?*)
- Q2 Kusama (and Paseo?*)
- Q3 Polkadot

---

## Impact Mitigations
- Exploring Reserve Location remapping in XCM executor. Will let you know within the next couple of weeks on outcome of this.
- Good testing in ecosystem tests
- Chopsticks/zombienet guides
- Early deployment on Paseo
- Good comms!

---

## AMA

---

## Further reading
- [AHM overview](https://docs.google.com/document/d/1SCT2WB6P8HzlLFZx4eEMPtb3GZkE4Ve7yTo8EsYkvVI/edit?tab=t.0)
- [AHM FAQ](https://docs.google.com/document/d/1XR3vL2p4QV0wC7FrlC8eN-q62BqNFTFElbj21wEmMGg/edit?tab=t.0)
- [Joe's blog about the Plaza upgrade](https://www.parity.io/blog/polkadot-smartcontract-platform)