What is Kusama Asset Hub and How Do You Connect to It?

What is Kusama Asset Hub?

Kusama Asset Hub is a common-good parachain on the Kusama network, originally launched as Statemine. It was designed to host and transfer arbitrary assets—both fungible tokens and non-fungible tokens (NFTs)—without burdening the Relay Chain. Over time, it has evolved to include smart contract capabilities and now serves as the primary chain for everyday user activity on Kusama.

The Asset Hub migration (runtime version 2.0.0) moved balances, staking, and governance from the Kusama Relay Chain to Asset Hub. This means that for most operations—sending KSM, staking, voting—users interact directly with Asset Hub rather than the Relay Chain.

• Para ID: 1000 on Kusama
• Native token: KSM
• Supports both native and foreign assets via XCM
• Smart contracts: ink! (Substrate-native) and EVM compatibility via pallet-evm

Key Features of Asset Hub

Asset Hub provides several core functionalities that make it essential for the Kusama ecosystem:

• Asset Issuance: Create and manage fungible assets with configurable properties like supply, decimals, and permissions.
• NFT Management: Mint, transfer, and manage non-fungible tokens using the Uniques and NFTs pallets.
• Smart Contracts: Deploy and interact with ink! smart contracts for custom logic, DeFi, and dApps.
• XCM Integration: Send and receive assets from other parachains via Cross-Consensus Messaging.
• Low Fees: Transaction costs are minimal compared to the Relay Chain, making it ideal for high-frequency operations.

How to Connect to Kusama Asset Hub via RPC

To interact with Asset Hub programmatically, you need an RPC endpoint. OnFinality provides both public and private endpoints for Asset Hub. The public endpoint is suitable for testing but rate-limited; for production use, sign up for a free API key to get higher limits and dedicated support.

Example curl request to get the latest block:

• Public HTTPS endpoint: https://assethub-kusama.api.onfinality.io/public
• Public WebSocket endpoint: wss://assethub-kusama.api.onfinality.io/public-ws
• Private endpoints available after registration with higher rate limits and archive data support.

Using Asset Hub for Asset Issuance and NFTs

Asset Hub makes it straightforward to issue new tokens or create NFT collections. The process involves calling extrinsics on the Assets or Uniques pallets. Below are the key steps:

• Fungible Assets: Use `assets.create` to define a new asset class, then `assets.mint` to issue tokens to an account.
• Sufficient vs Non-Sufficient: Sufficient assets can be held without needing KSM for existential deposit; non-sufficient assets require the account to already hold KSM.
• NFTs: Use `uniques.create` to start a collection, `uniques.mint` to mint individual items, and `uniques.transfer` to send them.
• All operations require KSM for gas fees, which can be obtained via the Relay Chain or from an exchange.

Smart Contracts on Asset Hub

With the introduction of smart contract support, developers can deploy ink! contracts on Asset Hub. This opens up possibilities for DeFi, gaming, and other dApps directly on the Kusama ecosystem. The contract deployment process is similar to other Substrate-based chains: compile your ink! contract, upload the code via a `contracts.instantiate` extrinsic, and interact using `contracts.call`.

For EVM compatibility, Asset Hub also includes the pallet-evm, allowing Solidity contracts to be deployed. This makes it easier for developers from the Ethereum ecosystem to port their applications.

• Supported languages: ink! (Rust) and Solidity (via EVM)
• Gas metering: Contracts pay fees in KSM
• Tooling: Use polkadot.js, Remix IDE, or Hardhat with appropriate adapters

Monitoring and Explorers

To track transactions, asset balances, and contract activity on Asset Hub, you can use block explorers. Subscan provides a dedicated explorer for Asset Hub with detailed views of blocks, extrinsics, assets, and NFTs. Blockscout is also available for EVM-based interactions.

• Subscan: https://assethub-kusama.subscan.io
• Blockscout: https://blockscout-kusama-asset-hub.parity-chains-scw.parity.io
• Parachains.info: https://parachains.info/details/assethub/ for project details and XCM channels

Best Practices for Production RPC Usage

When building applications that depend on Asset Hub, consider the following to ensure reliability and performance:

• Use private endpoints with API keys to avoid rate limiting and get dedicated resources.
• Enable archive data if your application needs historical state queries.
• Implement fallback endpoints to handle temporary outages.
• Monitor your RPC usage and scale up as your user base grows.
• Consider deploying a dedicated node for full control and custom configuration.

Frequently Asked Questions