system_chain | Kusama RPC Docs

Get the chain name on Kusama. Essential for network identification, multi-chain applications, and verifying the correct network connection.

Returns the chain name of the Kusama network. This identifies the specific chain or network the node is connected to (e.g., "Polkadot", "Kusama", "Westend").

Why Kusama? Build on Polkadot's canary network for real-world testing with live economic conditions with 7-day governance cycles (vs 1 month on Polkadot), lower bonding requirements, live KSM token economy, and first-to-market feature testing.

When to Use This Method

system_chain is essential for experimental dApp developers, parachain teams, and early adopters validating new features:

Network Verification -- Confirm your application is connected to the correct Kusama network before processing transactions
Multi-Chain Applications -- Dynamically identify which Substrate chain you are interacting with in cross-chain or multi-network dApps
UI Display -- Show the connected network name in wallet interfaces and dashboards for parachain experimentation, early feature deployment, and production-grade testing with real value
Configuration Validation -- Verify endpoint configuration matches the expected chain during deployment

Code Examples

Common Use Cases

1. Network Connection Verification

Validate that your application connects to the correct chain before processing any transactions:

JavaScript

import { ApiPromise, WsProvider } from '@polkadot/api';

async function connectAndVerify(endpoint, expectedChain) {
  const provider = new WsProvider(endpoint);
  const api = await ApiPromise.create({ provider });

  const chain = await api.rpc.system.chain();
  const chainName = chain.toString();

  if (chainName !== expectedChain) {
    await api.disconnect();
    throw new Error(
      `Expected "${expectedChain}" but connected to "${chainName}"`
    );
  }

  console.log(`Verified connection to ${chainName}`);
  return api;
}

// Usage
const api = await connectAndVerify('https://kusama-rpc.n.dwellir.com', 'Kusama');

2. Multi-Chain Router

Route operations based on detected chain identity:

JavaScript

async function getChainConfig(api) {
  const [chain, properties] = await Promise.all([
    api.rpc.system.chain(),
    api.rpc.system.properties()
  ]);

  const chainName = chain.toString();
  const configs = {
    Polkadot: { explorer: 'https://polkadot.subscan.io', confirmations: 1 },
    Kusama: { explorer: 'https://kusama.subscan.io', confirmations: 1 },
  };

  const config = configs[chainName] || { explorer: null, confirmations: 1 };

  return {
    name: chainName,
    tokenSymbol: properties.tokenSymbol.toString(),
    tokenDecimals: properties.tokenDecimals.toJSON(),
    ...config
  };
}

3. Health Check with Chain Identity

Include chain identity in health-check monitoring:

JavaScript

async function healthCheck(api) {
  const [chain, name, version] = await Promise.all([
    api.rpc.system.chain(),
    api.rpc.system.name(),
    api.rpc.system.version()
  ]);

  return {
    status: 'healthy',
    chain: chain.toString(),
    nodeImplementation: name.toString(),
    nodeVersion: version.toString(),
    timestamp: new Date().toISOString()
  };
}

Error Handling

Common errors and solutions:

Error Code	Description	Solution
-32603	Internal error	Node may be starting up -- retry after delay
-32005	Rate limit exceeded	Reduce request frequency or implement client-side rate limiting
Connection refused	Node unreachable	Verify the RPC endpoint URL and that the node is running

system_name -- Get the node implementation name
system_version -- Get the node implementation version
system_properties -- Get chain properties (token symbol, decimals, SS58 format)
state_getRuntimeVersion -- Get the on-chain runtime version
rpc_methods -- List all available RPC methods

system_chain - Kusama RPC Method

When to Use This Method

Code Examples

Common Use Cases

1. Network Connection Verification

2. Multi-Chain Router

3. Health Check with Chain Identity

Error Handling

On this page