Polkadot Hub vs Relay Chain and What Changed for DOT

What Hub and the Relay Chain Each Do

Polkadot Hub and the Relay Chain perform different jobs within the same ecosystem. Understanding those jobs helps explain why a wallet, an explorer and an exchange can use different labels around a DOT balance.

Compare the Chain Roles

The Relay Chain provides the coordination and security foundation. Hub brings asset management and application functionality closer to everyday users, including the migrated balance, staking and governance operations.

Match the Provider’s Deposit Support

Parity’s Polkadot Hub overview describes the application platform. A provider’s menu label is still only the start of the deposit check; the instructions must explain what it will credit.

What Changed in the Asset Hub Migration

Polkadot’s account-balance and user-function migration completed on November 4, 2025. The official migration material describes balances moving automatically, with ordinary user activity shifting to Asset Hub.

For a typical holder, that change did not require sending DOT to an address supplied by a third party. The official migration guide explains the moved functions and wallet implications.

If you open an old account view, the selected data source may be the problem. Update the wallet through its official channel and inspect the Hub/Asset Hub balance view for the same account before concluding that funds are gone.

Historical records remain important. A transfer made on the Relay Chain before migration belongs in that chain’s history, while later account activity may be indexed on Hub.

The migration also changed everyday account costs and requirements. For a new transfer, use the wallet’s active network preview rather than copying an old tutorial’s fee or minimum.

Resolve a Provider’s Network Label Before Sending

A hosted service may display “Polkadot,” “DOT” or “Asset Hub” in a network selector. The wording does not give enough evidence by itself to decide whether two endpoints are compatible.

Check the selected deposit page for the asset, chain, accepted address format, minimum and operational status. If the meaning is unclear, ask the recipient which DOT chain its address is monitored on and whether Hub/Asset Hub deposits are credited.

For example, your wallet may show a spendable Hub balance while a provider lists “Polkadot.” Keep that provider’s deposit instructions open and verify its support documentation before sending. Renaming the wallet network or changing an address prefix does not establish compatibility.

A direct ETH to DOT exchange also needs a supported DOT destination. Use the payout instructions for that route and match them to the recipient rather than treating the source Ethereum network as the DOT receiving network.

If you need to choose a receiving account first, the Polkadot wallet setup guide covers custody, backups and address formats.

Check a Missing Balance in the Right Place

A zero in one interface is an observation about that view. Establish the account and chain being queried before attempting recovery actions.

Use this sequence when an older wallet view no longer shows the expected DOT:

1. Check that the selected account is the one you previously funded.
2. Update the wallet and read its migration notices.
3. Select its supported Hub/Asset Hub view.
4. Compare the public account activity in the matching explorer.
5. If the activity is visible but the app total is wrong, contact that wallet’s support with the public address and transaction reference.

Some older signing setups can use different derivation paths for different networks. If the derived account changes, use the signer’s official migration guidance; do not create or import unrelated accounts until you understand which key controlled the original address.

Avoid sharing recovery material with anyone offering to “resynchronize” the balance. Public addresses and transaction evidence are enough to begin a viewing or indexing investigation.

When a Transfer Needs More Than a Network Switch

Selecting a different network in a wallet changes the view or transaction context. It does not, by itself, move a balance between chains.

A normal same-chain payment, a cross-chain asset movement and a service-mediated exchange are different operations. First identify which one your destination requires, then use a route that explicitly supports it.

For a routine supported DOT payment, follow the DOT sending and tracking steps. If the asset is held on a separate parachain or in a wrapped form, inspect the wallet’s supported transfer path and the recipient’s accepted asset before proceeding.

This guide does not prescribe a manual XCM route. Choosing one requires the exact source chain, asset location and destination support, which cannot be inferred from the ticker alone.

Hub and Relay Chain FAQ

These questions concern reading history and account support after the migration. Resolve the specific account and chain before making a new transfer.