Bridge Hub Kusama RPC Endpoints & Dedicated Nodes | OnFinality

Parity

The development of bridges to connect other networks

Connect to Bridge Hub Kusama in seconds with OnFinality RPC endpoints, request analytics, scalable rate limits, and 99.99% uptime for production Web3 apps. Deploy full, collator, and archive Bridge Hub Kusama nodes quickly and easily on our globally distributed, multi-cloud, one-click node solution. Use OnFinality's Lightning Restore to fully-sync your nodes in seconds instead of days!

The development of bridges to connect other networks

Create RPC Endpoint Deploy Dedicated Node

Bridge Hub Kusama RPC Endpoint

The below example uses the public API endpoint*. This endpoint is only suitable for testing. To avoid rate limiting and service interruption, sign up now to get your own API key.

Open In Polkadot JS

* The public endpoint is rate limited

RPC API Service

RPC API Features

ArchiveTrace

RPC Regions

N.Virginia

Dedicated Nodes

Node Type

FullArchiveCollatorArchive Norelay

Lightning Restore

N.Virginia

Node Endpoints

JSON-RPCWebSocketsMetrics

Bridge Hub Kusama is a system parachain on the Kusama network that enables trustless cross-chain communication between Kusama, Polkadot, Ethereum, and other blockchains. As a common good parachain, it provides a secure and scalable hub for bridging assets and messages across different networks. Developers building cross-chain applications, relayers, or infrastructure services need reliable RPC access to interact with Bridge Hub Kusama.

What is Bridge Hub Kusama?

Bridge Hub Kusama (also referred to as BridgeHub Kusama) is a foundational parachain designed to house trustless bridges. It leverages on-chain light clients, BEEFY and GRANDPA consensus protocols, and a suite of specialized pallets to enable secure cross-chain state verification and message passing. The Polkadot-Kusama bridge, which went live in 2024, uses Bridge Hub Kusama and Bridge Hub Polkadot to facilitate XCM transfers between the two ecosystems.

Why Use Bridge Hub Kusama RPC?

Applications that interact with Bridge Hub Kusama require RPC endpoints to read chain state, submit transactions, and monitor bridge operations. Common use cases include:

Cross-chain dApps: Query bridge status and relay messages between chains.
Relayers: Submit bridge transactions and verify light client updates.
Indexers & analytics: Retrieve historical bridge activity and asset transfer data.
Wallets: Display balances and facilitate asset transfers across the bridge.

Bridge Hub Kusama RPC Endpoints on OnFinality

OnFinality provides managed API endpoints for Bridge Hub Kusama, supporting both HTTP and WebSocket transports. Developers can choose from shared public endpoints for testing or authenticated endpoints for production workloads. Key features include:

Substrate JSON-RPC protocol – standard methods for chain interaction.
Archive node support – access to full historical state for deep queries.
Trace API support – detailed transaction tracing for debugging and analysis.
Dedicated nodes – isolated infrastructure for high-throughput or latency-sensitive applications.

Public vs. Private RPC for Bridge Hub Kusama

Public RPC endpoints are convenient for quick experiments, but they often lack reliability guarantees and rate-limit visibility. OnFinality’s authenticated endpoints offer:

Stable access with clearer usage limits.
Request analytics to monitor traffic and errors.
A scaling path from shared APIs to dedicated nodes as your project grows.

Getting Started with Bridge Hub Kusama RPC

Create a free OnFinality account.
Select Bridge Hub Kusama from the supported networks list.
Generate an API endpoint or deploy a dedicated node.
Test connectivity using chain_getBlock or similar methods.
Monitor usage and adjust plan as needed.

Bridge Hub Kusama is a critical piece of the Polkadot-Kusama interoperability stack. With OnFinality, you get reliable, production-ready RPC infrastructure to build and scale your cross-chain applications.