Kaia Public Node: Endpoints, Providers, and Production Considerations

Quick Recommendation: Public Node or Managed RPC?

If you are prototyping or building a small dApp, the official Kaia public endpoints are a reasonable starting point. They are free and require no setup. However, they are shared infrastructure: rate limits can change without notice, and heavy traffic from other users can cause delays. For production applications, you should evaluate a managed RPC provider or a dedicated node to get consistent performance, higher throughput, and support.

Before you commit to a provider, consider your workload:

• Read-heavy dApps (e.g., explorers, analytics) need reliable eth_call and eth_getLogs performance.
• Write-heavy applications (e.g., DeFi protocols) need low-latency eth_sendRawTransaction and WebSocket support for pending transaction notifications.
• Historical data needs may require an archive node, which most public endpoints do not provide.

If you are unsure, start with a managed RPC service that offers a free tier and scales with you. OnFinality provides Kaia RPC endpoints as part of its supported networks, and you can check RPC pricing for plans that fit your usage.

What Is a Kaia Public Node?

A Kaia public node is an endpoint node operated by the Kaia Foundation or a third-party provider that exposes the Kaia network's JSON-RPC API to the public. It allows you to send transactions, query blockchain data, and interact with smart contracts without running your own node.

Kaia is a BFT-based public blockchain formed from the merger of Klaytn and Finschia. It is designed for enterprise-grade reliability and performance, with a focus on high throughput and low latency. The network uses a hybrid consensus mechanism that combines BFT and proof-of-stake, and it supports Ethereum-compatible APIs, making it easy for developers to build with familiar tools like ethers.js and viem.

Running your own Kaia endpoint node is not trivial. It requires technical expertise, monitoring, and computing resources. You need to maintain storage, network bandwidth, and keep the node up to date. Public nodes remove this burden, letting you focus on building your product.

Official Kaia Public Endpoints

The Kaia Foundation provides public JSON-RPC endpoints for both mainnet and testnet. These are the official endpoints you can use to connect to the network.

Mainnet

• Public endpoint: https://public-en.node.kaia.io
• Archive endpoint: https://archive-en.node.kaia.io

Testnet (Kairos)

• Public endpoint: https://public-en-kairos.node.kaia.io
• Archive endpoint: https://archive-en-kairos.node.kaia.io

Note: The old Klaytn endpoints (public-en-cypress.klaytn.net, archive-en.cypress.klaytn.net, public-en-baobab.klaytn.net, archive-en.baobab.klaytn.net) were discontinued in September 2024. Update your configurations to the new URLs to avoid service interruptions.

These endpoints are free but come with caveats. The Kaia Foundation states that node providers are not responsible for damage or losses caused by traffic or interaction with the nodes. If traffic is concentrated on certain nodes, you may experience service delays. Rate limits may apply on a per-node basis and are subject to change without prior notification.

Chain Settings at a Glance

When configuring your wallet or dApp, you need the correct chain parameters. Here are the key settings for Kaia mainnet and Kairos testnet.

How to Connect to Kaia with ethers.js

Here's a simple example of connecting to the Kaia mainnet using ethers.js:

import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider("https://public-en.node.kaia.io");

async function getBlockNumber() {
  const blockNumber = await provider.getBlockNumber();
  console.log("Current block number:", blockNumber);
}

getBlockNumber();

For the Kairos testnet, replace the URL with https://public-en-kairos.node.kaia.io.

Using a Managed RPC Provider for Kaia

While the official public endpoints are fine for testing, production applications often need more. Managed RPC providers offer several advantages:

• Higher rate limits – Shared public endpoints can throttle your requests, especially during peak times.
• Dedicated resources – A dedicated node gives you exclusive access to compute and bandwidth, ensuring consistent performance.
• Archive data – Many providers offer archive nodes, which are essential for historical queries.
• WebSocket support – Real-time data feeds require WebSocket connections, which are not always available on public endpoints.
• Monitoring and support – Providers handle node maintenance, upgrades, and offer SLAs.

OnFinality is one such provider that supports Kaia. You can find the Kaia RPC endpoint on the Kaia network page. OnFinality offers both shared and dedicated RPC options, and you can view pricing to choose a plan that fits your needs.

Evaluating RPC Providers for Kaia

When comparing RPC providers, consider the following criteria:

OnFinality, for example, provides a global network of nodes and offers both shared and dedicated options. You can test the Kaia endpoint by making a simple JSON-RPC call:

curl -X POST https://klaytn.api.onfinality.io/public \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

This should return the latest block number in hexadecimal format.

Common Pitfalls and Troubleshooting

Here are some common issues you might encounter when using Kaia public nodes and how to resolve them.

Rate Limiting

Public endpoints often have rate limits. If you receive 429 Too Many Requests errors, you are hitting the limit. Solutions:

• Reduce request frequency by caching responses.
• Use a managed provider with higher limits.
• Implement retry logic with exponential backoff.

Outdated Endpoints

As mentioned, the old Klaytn endpoints are deprecated. If you are still using them, you will get connection errors. Update your configuration to the new URLs.

WebSocket Connection Drops

WebSocket connections can drop due to network issues or server restarts. Implement reconnection logic in your client.

Archive Data Missing

If you need historical state, ensure your provider offers archive nodes. Public endpoints typically only provide recent data.

Key Takeaways

• Kaia public nodes allow you to interact with the network without running your own node.
• The official public endpoints are free but have limitations like rate limits and potential delays.
• For production, consider a managed RPC provider or dedicated node for reliability and performance.
• Always use the current endpoint URLs to avoid service interruptions.
• Evaluate providers based on uptime, rate limits, archive support, WebSocket, and pricing.

Frequently Asked Questions

What is the Kaia mainnet chain ID?

The Kaia mainnet chain ID is 8217 (0x2019).

What is the Kaia testnet chain ID?

The Kaia Kairos testnet chain ID is 1001 (0x3E9).

What is the native currency of Kaia?

The native currency is KAIA, with 18 decimals.

How do I add Kaia to MetaMask?

You can add Kaia as a custom network in MetaMask using the chain settings provided above. Enter the RPC URL, chain ID, and symbol KAIA.

Are there any free Kaia RPC providers?

Yes, the official Kaia public endpoints are free, and some providers like OnFinality offer free tiers. Check the OnFinality pricing page for details.

What is the difference between a public node and a dedicated node?

A public node is shared among many users, while a dedicated node is exclusively for your use. Dedicated nodes offer better performance, higher rate limits, and more control.

How do I get support for Kaia RPC issues?

If you are using OnFinality, you can contact their support team. For the official Kaia endpoints, refer to the Kaia documentation for troubleshooting.

---

This article is part of the OnFinality RPC Assistant series. For more information about RPC providers and network support, visit our supported networks page.