Logo
RPC Assistant

Asset Hub Kusama RPC Endpoint: How to Connect and Use It

Summary

Asset Hub Kusama (formerly Statemine) is a system parachain on Kusama for low-cost asset creation and transfers. This article provides the chain settings, available RPC methods, and practical connection guidance for developers seeking reliable infrastructure. For production workloads, evaluate latency, archive node support, and WebSocket availability to ensure consistent access.

Asset Hub Kusama Decision Checklist

Before integrating with Asset Hub Kusama, consider the following criteria to choose the right RPC infrastructure:

CriterionWhat to checkWhy it matters
Endpoint typePublic vs. private RPC endpointsPublic endpoints have rate limits; private endpoints offer higher throughput for production dApps.
Archive node supportDoes the provider offer archive data?Required for historical queries and indexing.
WebSocket availabilityIs WebSocket supported for subscriptions?Essential for real-time features like transaction subscriptions.
Network latencyCheck your geographic proximity to nodesHigh latency increases response times.
Rate limitsWhat are the requests per second (RPS) limits?Limits affect your application's ability to scale.
Failover and redundancyDoes the provider have multiple nodes?Ensures uptime during node failures.

Asset Hub Kusama Overview

Asset Hub Kusama is a system parachain on the Kusama network designed for low-cost asset creation, transfer, and NFT management. It replaces the earlier Statemine parachain and serves as the primary hub for holding and transacting both fungible and non-fungible assets on Kusama. As a common-good parachain, it leverages Kusama's security and provides seamless XCM (Cross-Consensus Messaging) integration with other parachains.


Chain Settings and Configuration

When connecting to Asset Hub Kusama, you need the following network parameters:

ParameterValue
Network nameAsset Hub Kusama
Chain ID420420418
Native tokenKusama (KSM)
RPC endpoint (public)https://asset-hub-kusama-rpc.publicnode.com (example)
WebSocket endpoint (public)wss://asset-hub-kusama-rpc.publicnode.com (example)
ExplorerSubscan
Para ID1000

Note: Public endpoints are rate-limited. For production applications, consider using a dedicated RPC provider like OnFinality to get higher throughput and reliable access.


Available RPC Methods

Asset Hub Kusama uses Substrate-based JSON-RPC. Key method groups include:

  • Chain: chain_getBlock, chain_getHeader, chain_getBlockHash
  • State: state_getStorage, state_getMetadata, state_getRuntimeVersion
  • System: system_chain, system_name, system_version
  • Author: author_submitExtrinsic, author_pendingExtrinsics (for transactions)

A full list is available in the Substrate JSON-RPC specification.


Connecting to Asset Hub Kusama

You can interact with Asset Hub Kusama using any JSON-RPC client. Below are examples using curl and WebSocket.

curl Example

curl -X POST https://api.onfinality.io/rpc?apikey=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "chain_getBlock",
    "params": []
  }'

Replace YOUR_API_KEY with a valid API key from OnFinality. For WebSocket, use a library like ws in Node.js:

const WebSocket = require('ws');
const ws = new WebSocket('wss://api.onfinality.io/public-ws/asset-hub-kusama?apikey=YOUR_API_KEY');

ws.on('open', () => {
  ws.send(JSON.stringify({
    jsonrpc: '2.0',
    id: 2,
    method: 'chain_subscribeNewHeads',
    params: []
  }));
});

ws.on('message', (data) => {
  console.log('New head:', data);
});

Common Pitfalls and Troubleshooting

IssuePossible CauseSolution
"Block not found"Using a pruned nodeUse an archive node provider.
Rate limit errorsExceeding public endpoint limitsSwitch to a private RPC provider with higher limits.
WebSocket disconnectionUnstable network or node restartImplement reconnection logic in your client.
Wrong chain IDWallet configuration mismatchDouble-check that the Chain ID is 420420418.

Key Takeaways

  • Asset Hub Kusama is a system parachain for low-cost asset and NFT operations on Kusama.
  • Use the chain ID 420420418 and para ID 1000 for configuration.
  • Public RPC endpoints are available but have rate limits; for production, use a reliable provider like OnFinality with dedicated nodes.
  • Archive node support is essential for historical data queries.
  • WebSocket subscriptions enable real-time updates but require proper reconnection handling.

Frequently Asked Questions

What is the difference between Asset Hub Kusama and Statemine? Statemine was the previous name; Asset Hub Kusama is the updated version with enhanced asset and NFT functionality.

Can I deploy smart contracts on Asset Hub Kusama? Yes, Asset Hub Kusama supports EVM smart contracts via the EVM pallet. Check the network's runtime version for specific capabilities.

How do I get KSM for gas fees? KSM can be transferred from the Kusama relay chain via XCM or acquired on centralized exchanges. Ensure you have at least 0.001 KSM for basic operations.

What RPC provider do you recommend? Evaluate providers based on uptime, archive support, and rate limits. OnFinality offers scalable dedicated nodes; see RPC pricing and supported networks for details.


For more details on RPC provider selection, read our guide on how to choose an RPC provider.

RPC Knowledge Base

Related RPC details

Never Worry about Infrastructure Again

OnFinality takes away the heavy lifting of DevOps so you can build smarter and faster.

Get Started