Individual or corporate developers can access both free public endpoints and premium services through the Klaytn network of RPC providers. However, we urge projects and developers to collaborate with specialized RPC providers who offer highly available, reliable RPCs and are better equipped to meet their needs when building their enterprise metaverse application.
Below is a list of Public RPC Node providers in our ecosystem.
Public Endpoint Nodes
Public EN allows you to solely focus on building and testing your blockchain product without the distraction of maintaining infrastructure to connect and interact with the Klaytn network.
- Klaytn Foundation
- Klaytn Foundation
|1||ANKR||Mainnet||500 requests per second on the free plan, and 1,500 on the premium. It is upgradable on request.||Free and Subscription Plan|
|2||POKT||Mainnet||250,000 Requests Per Day Free Tier (up to two applications, with unlimited endpoints)||Free and Pay-As-You-Go Plan|
|3||BlockPi||Mainnet||20 requests per second on free services, and unlimited for paid packages.||Free and Paid Plan|
|4||Klaytn API Service(KAS)||Mainnet||10,000 requests per day (100 requests per second) for the free plan||Free and Paid Plan|
|5||Tatum||Mainnet||5 requests per second for the free plan, and 200 requests per second for the paid plans (Start, Basic)||Free and Subscription Plan|
|6||AllThatNode||Mainnet||20,000 request per day||Free and Paid Plan|
In general, a diverse set of nodes ensure that the blockchain network (e.g Klaytn) is secure. These nodes, store and analyze blockchain information, validate the blockchain's state. Each node on the same network can interact with another node to accomplish a variety of tasks.
One type of node serving a unique purpose is the archival node, which is responsible for storing the complete historical data of the blockchain. The most current blockchain state is stored by other types, including the full node and the light node.
An archival node is a node with the ability to preserve all of the blockchain's historical data, all the way back to the genesis block. This involves keeping track of transactions, block headers, and receipts.
Why should you care about Archival node
Compared to full nodes and light nodes, archive nodes have unique characteristics that allow for new and fascinating use cases for developers. Highlighted below are some of the reasons why you should care about archival nodes.
Your metaverse smart contract may need to be tested in some edge circumstances based on an older version of the blockchain, which could occasionally be more recent than the first 128 blocks when utilizing a full node. This is where archive nodes come into play. With archive nodes, you can query older blockchain data quickly without running into errors.
In order to develop a reputation system in your metaverse application, for instance, you may need to keep track of users' actions over an extended period of time. This is one real-world illustration of the necessity of archive nodes.
How to run your own Node
In general public RPC endpoints will have rate limits due to security reasons or the subscription plan might be expensive depending on the service providers. In such case you can opt to run your own node to interact with Klaytn network.
If you are an enterprise application and expect huge traffic and worried about stability concerns it would be advisable to run your dedicated rpc nodes.
Setting up your own node
Anyone who wants to send transactions or query the state of Klaytn network using Klaytn APIs needs to do so via an Endpoint Node. Endpoint Nodes are the interface to the Klaytn Network.
The Endpoint Node install binary comes with the following interfaces and utilities.
JSON-RPC APIs: JSON-RPC server runs inside the node, and it exposes APIs for Blockchain Application development. It has several node management APIs as well.
Setting up your own node means you'll be downloading a copy of the Klaytn blockchain through a client. Thus, you'll need high-end computers for the job. You can go for a deep dive into setting up your own Klaytn node with the following documentation.
Rather than syncing from scratch, you can use the snapshots available for mainnet and testnet. You can contact the team via discord to get the AMI image for the archive node if you are using aws.