Re-enable Kusama Hub network when RPC becomes available

Summary

Re-enable Kusama Hub (Asset Hub) network support in the Polkadot adapter once the official EVM RPC endpoint becomes publicly available.

Background

The Kusama Hub network was temporarily disabled in PR #313 and #314 because the official RPC endpoint DNS (kusama-asset-hub-eth-rpc.polkadot.io) does not resolve as of January 2026.

Chain Details:

• Chain ID: 420420418
• Currency: KSM
• Explorer: Blockscout (https://blockscout.kusama.network)

What needs to be done

When the Kusama Hub EVM RPC service becomes publicly available:

1. Verify RPC endpoint - Test that the DNS resolves and the RPC responds correctly:

   curl -X POST https://kusama-asset-hub-eth-rpc.polkadot.io \
     -H "Content-Type: application/json" \
     -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
   

2. Uncomment configurations in the following files:

   • packages/adapter-polkadot/src/networks/chains.ts - kusamaHub chain definition
   • packages/adapter-polkadot/src/networks/mainnet.ts - kusamaHubMainnet config
   • packages/adapter-polkadot/src/networks/index.ts - exports
   • packages/adapter-polkadot/src/index.ts - package exports
   • packages/adapter-polkadot/src/wallet/chains.ts - polkadotChains array

3. Re-enable tests in:

   • packages/adapter-polkadot/src/__tests__/networks.test.ts
   • packages/adapter-polkadot/src/__tests__/adapter.test.ts

References

• Kusama Smart Contracts: https://kusama.network/smart-contracts
• Polkadot Hub EVM Docs: https://docs.polkadot.com/develop/smart-contracts/

Labels

• enhancement
• polkadot

This work is blocked until the Kusama Hub RPC endpoint resolves and responds to the documented curl request. Then inspect the listed files under packages/adapter-polkadot, uncomment the chain, network, export, wallet, and test configurations, and run networks.test.ts and adapter.test.ts to confirm support is restored.