Kusama Migration: What Changed and How to Update Your RPC Endpoints

Quick Migration Checkpoints

If you are a developer or infrastructure operator on Kusama, the migration to Asset Hub changes where you send certain RPC calls. Here is a quick checklist to get your endpoints updated:

• Identify which chain your dApp depends on. If you were using Relay Chain RPC for balance transfers, staking, or governance, you likely need to switch to Asset Hub Kusama.
• Update your network configuration. Change the RPC endpoint and chain ID to Asset Hub Kusama. See the Asset Hub Kusama network page for the official endpoint.
• Test with a small transaction. Before going live, send a test transfer to confirm your wallet and backend are using the correct chain.
• Monitor for errors. Watch for InvalidTransaction or UnknownConnection errors that indicate you are still pointing to the old chain.

If you are unsure which chain your use case requires, the next section breaks down the migration and its impact.

What the Kusama Migration Actually Changed

The Kusama migration, executed on October 7, 2025, moved core functionality from the Kusama Relay Chain to Asset Hub Kusama. This is part of a broader roadmap to make the network more scalable and accessible. The migration was completed in about 3 hours and 13 minutes, moving all assets, pallets, accounts, and proxies.

For developers, the key change is that Asset Hub Kusama is now the primary chain for asset transfers and management. The Relay Chain still exists but is no longer the place to send KSM transfers or interact with assets. This means your RPC endpoints must be updated to point to Asset Hub Kusama for these operations.

Why This Matters for Your dApp

If your dApp handles KSM transfers, queries balances, or interacts with assets, it must now talk to Asset Hub Kusama. Using the old Relay Chain endpoint will result in errors or stale data. The migration also brought several improvements:

• Lower minimum balance: reduced from 0.00003 KSM to 0.000003 KSM.
• Lower transaction fees: reduced from 0.00053 KSM to 0.00009 KSM.
• More token support: USDT, USDC, DOT, and other ecosystem tokens.
• Unified access: KSM, assets, staking, and governance in one place.
• Fee payment in any token: pay transaction fees with any supported asset.

These changes are beneficial, but they require you to update your infrastructure to take advantage of them.

Chain Settings at a Glance

Here are the key settings for Asset Hub Kusama. Use these to update your network configuration.

Note: The RPC endpoint is not hardcoded here because it may vary by provider. Use the official OnFinality public endpoint listed on the network page.

Updating Your RPC Endpoint

To update your dApp, you need to change the RPC endpoint in your configuration. Here is an example using a common JavaScript library like polkadot-js:

const { ApiPromise, WsProvider } = require('@polkadot/api');

// Replace with the official Asset Hub Kusama endpoint
const wsProvider = new WsProvider('wss://assethub-kusama-rpc.polkadot.io');

async function main() {
  const api = await ApiPromise.create({ provider: wsProvider });
  console.log(`Connected to chain: ${await api.rpc.system.chain()}`);
}

main().catch(console.error);

If you are using a REST API or a different library, the same principle applies: update the endpoint URL and ensure your chain ID matches.

Common Pitfalls and How to Avoid Them

Here are the most common issues developers face after the migration and how to avoid them:

Migration Checklist for Production Apps

Before you deploy, run through this checklist to ensure a smooth transition:

• Update all RPC endpoints to Asset Hub Kusama.
• Update chain ID in all configurations.
• Test with a small transfer on the new chain.
• Verify balance queries return correct data.
• Monitor logs for errors after deployment.
• Communicate changes to your users if they use your app for KSM transfers.

Choosing the Right RPC Provider

When updating your endpoints, you may also want to evaluate your RPC provider. The migration is a good time to ensure your provider supports Asset Hub Kusama and offers the reliability you need. Consider the following:

• Network coverage: Does the provider support Asset Hub Kusama and other Kusama parachains?
• Transport options: Do you need WebSocket, HTTPS, or both?
• Rate limits: Are there limits that could affect your traffic?
• Support: Is there a dedicated support channel for issues?

OnFinality offers RPC services for Asset Hub Kusama and many other networks. You can check supported RPC networks and RPC pricing to see if it fits your needs. OnFinality also provides dedicated nodes for high-traffic applications.

Key Takeaways

• The Kusama migration moved core functionality to Asset Hub Kusama.
• Update your RPC endpoints to Asset Hub Kusama for asset transfers and balance queries.
• Use the correct chain ID (1000) and test before going live.
• Monitor for common errors like InvalidTransaction.
• Evaluate your RPC provider to ensure it supports the new chain.

Frequently Asked Questions

Do I need to migrate my KSM tokens?

No. The migration was automatic. Your KSM tokens moved to Asset Hub Kusama without any action on your part.

What happens to my old transaction history?

Old transaction history remains on the Kusama Relay Chain. You can still query it, but new transactions will be on Asset Hub Kusama.

Can I still use the Relay Chain for staking?

Staking functionality has moved to Asset Hub Kusama. You should update your staking dApp or wallet to use the new chain.

How do I find the official RPC endpoint?

Check the Asset Hub Kusama network page for the official OnFinality public endpoint.

What if I use a wallet that doesn't support Asset Hub Kusama?

You may need to switch to a wallet that supports the migration. Many wallets have updated, but some like Trust Wallet had issues. Check your wallet's documentation for migration support.