RPC Providers

Introduction

Solana makes use of independent nodes which have the responsibility of working to confirm programs and outputs of programs on one of the three Solana clusters, Devnet, Testnet or Mainnet Beta. A cluster is made up of a set of validators that work to confirm transactions. These are owned and operated by individuals. These nodes are also responsible for storing data and transaction history which is shared amongst the nodes. A node can become a validator node if it is being used to vote on valid blocks and if SOL is delegated to the validator identity it can become a leader node. This is the link to the information on how to become a validator.

Not all nodes can become leader nodes or vote to confirm blocks. They still serve the other functionalities of validator nodes, but since they cannot vote they are primarily used to respond to requests on the blockchain. These are RPC nodes. RPC stands for remote procedure call, and these RPC nodes are used to send transactions through the blockchain.

Solana maintains three public API nodes, one for each cluster which are Devnet, Mainnet Beta, and Testnet. These API nodes are what allow users to connect to the cluster. To connect to Devnet users can look at:

https://api.devnet.solana.com

This is the node for Devnet, and it is rate limited.

In the Mainnet Beta cluster, many developers choose to use their own private RPC node to take advantage of higher rate limits not avalible to them from Solana's public API nodes.

For Mainnet Beta in the picture above, from the Solana Docs, we can view the rate limits from using the mainnet api node. The Mainnet Node does not support the Metaplex DAS API currently.

We will proceed to define some capabilities of RPC nodes and then present you with several options. We recommend you choose one based on your project's needs.

Metaplex DAS API

Another distinguishing feature of RPCs is if they support the Metaplex DAS API. The Metaplex Digital Asset Standard (DAS) API represents a unified interface for interacting with digital assets on Solana, supporting both standard (Token Metadata) and compressed (Bubblegum) assets. The API defines a set of methods that RPCs implement in order to provide asset data.

For Developers the DAS API is required to interact with cNFTs, but it can also make working with TM Assets easier and faster. When reading from chain we therefore highly recommend using RPC nodes with DAS Support to make the user experience as fast as possible.

You can find out more about the DAS API in a dedicated section.

Archive and Nonarchive Nodes

We can divide nodes into two different categories. The first one we will look at are the Archive nodes. These can store information of previous blocks. In the case of these archival nodes, we can leverage having access to all previous blocks in several ways. Some of the advantages include being able to view an address's balance history and view any state in the history. Due to the high system requirements of running a full historical node, having private nodes available with this feature is highly beneficial.

Unlike archival nodes, a non-archive node, or just a regular node, will only have access to some of the previous blocks, which is upwards of 100 blocks. We previously mentioned that running an archival node has intensive requirements, but even a non-archive node can become hard to manage. For this reason, users often choose a private RPC provider. Most use cases involving private RPCs in Solana usually revolve around Mainnet-beta uses since this involves real SOL tokens, and there is a higher chance of being rate limited.

RPCs Available

The following section includes multiple RPC providers.

RPCs with DAS Support

• Extrnode
• Helius
• Hello Moon
• QuickNode
• Shyft
• Triton

RPCs without DAS Support

• Alchemy
• Ankr
• Blockdaemon
• Chainstack
• Figment
• GetBlock
• NOWNodes
• Syndica

Further Information

If you have any questions or would like to further understand this topic, you are welcome to ask join the Metaplex Discord Server.