Solana Mainnet RPC - Quickstart
Introduction
To deploy a Solana mainnet RPC, you'll use the SLV command-line tool.
This quickstart guide explains how to use the SLV command-line tool to deploy a Solana mainnet RPC with Geyser Yellowstone plugin.
You must have Ubuntu 24.04 LTS clean installed on your server.
Preparing a Baremetal Server
While it is possible to run a Solana client on VPS or virtual machine (VM), achieving optimal performance and stable operation is challenging. RPC nodes and validators, in particular, operate under high-load conditions, making it crucial to set up an appropriate server environment.
Solana officially recommends using baremetal servers.
Recommended specifications for an RPC node are as follows:
- Minimum Requirements: 24-core CPU, 512GB RAM or higher
- Recommended for Indexed Nodes: 32-core CPU, 1152GB RAM or higher
CPU clock speed is particularly important for Solana nodes. As noted in the official documentation, having the latest generation CPU with high clock speeds can significantly maximize performance, beyond simply increasing core count. Recently, Firedancer has also started recommending 32-core CPUs, making it optimal to utilize 32 cores, especially considering the handling of a large volume of RPC requests.
SLV Metal provides baremetal servers designed to deliver the highest performance within your budget.
When executing the
slv metal list command, you can find the RPC option specifically tailored for Solana RPC nodes.slv metal list ? 🛡️ Select SLV BareMetal Type (APP) 📦 APP - For Trade Bot,Testnet Validator, DApp and More! 🚀 MV - For Solana Mainnet Validator ❯ 🛡️⚡️ RPC - For Solana RPC Node
If you have not yet set up your baremetal server, please follow the Baremetal Server Setup Guide.
Additionally, refer to the following resources:
Deploy Solana RPC Node
First, initialize the Solana RPC configuration.
Please select network as your desired Solana network.
slv rpc init ? Select Solana Network (mainnet) testnet devnet ❯ mainnet
Next, confirm whether you have a Solana Node Compatible Server.
? 🛡️ Do you have a Solana Node Compatible Server? (yes) ❯ yes no
This tutorial assumes you select
yes.Set Server User and IP Address
Set the server user, IP address, and RSA key path.
? What's the user for the server? (root) › root ? Enter the server IP address › x.x.x.x ? What's the path to your RSA key? (~/.ssh/id_rsa)
Automatic Region Detection
Next, the system will ping each block engine from your configured node to automatically detect the nearest region. By measuring actual ping values, you can select the optimal region.
🔍 Checking SSH connection... ✔︎ SSH connection succeeded 📍 Measuring latencies from x.x.x.x to mainnet regions... Pinging Amsterdam (amsterdam.mainnet.block-engine.jito.wtf)... Pinging Dublin (dublin.mainnet.block-engine.jito.wtf)... Pinging Frankfurt (frankfurt.mainnet.block-engine.jito.wtf)... Pinging London (london.mainnet.block-engine.jito.wtf)... Pinging New York (ny.mainnet.block-engine.jito.wtf)... Pinging Salt Lake City (slc.mainnet.block-engine.jito.wtf)... Pinging Singapore (singapore.mainnet.block-engine.jito.wtf)... Pinging Tokyo (tokyo.mainnet.block-engine.jito.wtf)... ✅ Singapore: 0.291 ms ✅ London: 154.071 ms ✅ Dublin: 167.267 ms ✅ Frankfurt: 149.081 ms ✅ Amsterdam: 154.501 ms ✅ New York: 228.624 ms ✅ Salt Lake City: 278.016 ms ✅ Tokyo: 376.816 ms 🎯 Nearest region: 🇸🇬 Singapore Latency: 0.291 ms Block Engine: https://singapore.mainnet.block-engine.jito.wtf Shred Receiver: 202.8.11.224:1002 Relayer: http://singapore.mainnet.relayer.jito.wtf:8100 NTP Server: ntp.singapore.jito.wtf
Generate Identity Keypair
If you don't have an identity keypair, you can generate a new one.
? Do you want to create a new identity key now? (Y/n) › Yes 🔑 Generating new identity key... ✨ Generated Key: p3tnYqjciWz8DnjApUVDPWTEhdzdX6qvqTaRCrckSLV ✨ Moved Key to: ~/.slv/keys/p3tnYqjciWz8DnjApUVDPWTEhdzdX6qvqTaRCrckSLV.json
Select Solana CLI
Select the Solana CLI version.
? Select Solana CLI (jito) agave ❯ jito firedancer-agave firedancer-jito
Select RPC Type
Select the RPC type.
? Select an RPC type ❯ Geyser gRPC Index RPC SendTx RPC Index RPC + gRPC
In this tutorial, we select
Geyser gRPC.Confirm Configuration
Finally, confirm the configuration.
✔︎ Success ✔ Inventory updated to ~/.slv/inventory.mainnet.rpcs.yml ✔ Successfully created solv user on p3tnYqjciWz8DnjApUVDPWTEhdzdX6qvqTaRCrckSLV ✔︎ mainnet_rpcs inventory file has been saved to ~/.slv/inventory.mainnet.rpcs.yml Now you can deploy with: $ slv rpc deploy -n mainnet -p p3tnYqjciWz8DnjApUVDPWTEhdzdX6qvqTaRCrckSLV
After that, the
solv user is created on the bare metal server, and
the Solana RPC configuration is saved to ~/.slv/inventory.mainnet.rpcs.yml.Deploy Solana RPC Node
Once you confirm the configuration, the deployment will start.
slv rpc deploy -n mainnet -p p3tnYqjciWz8DnjApUVDPWTEhdzdX6qvqTaRCrckSLV
Your mainnet RPC Nodes Settings: ┌──────────────┬─────────────────────────────────────────────┐ │ Identity Key │ p3tnYqjciWz8DnjApUVDPWTEhdzdX6qvqTaRCrckSLV │ ├──────────────┼─────────────────────────────────────────────┤ │ Name │ p3tnYqjciWz8DnjApUVDPWTEhdzdX6qvqTaRCrckSLV │ ├──────────────┼─────────────────────────────────────────────┤ │ IP │ x.x.x.x. │ ├──────────────┼─────────────────────────────────────────────┤ │ Region │ singapore │ ├──────────────┼─────────────────────────────────────────────┤ │ RPC Type │ Geyser gRPC │ ├──────────────┼─────────────────────────────────────────────┤ │ Version │ 3.0.7-jito │ └──────────────┴─────────────────────────────────────────────┘ . . . Successfully Deployed RPC on mainnet ⚡️⚡️⚡️ Enhanced Solana RPC Connection API Key ⚡️⚡️⚡️ We're excited to offer a free API key exclusively for the Validators DAO community 🎉 It's our way of supporting the community and empowering you with fast, reliable connections. To get your Free API key, simply join us through the link below: Validators DAO: `https://discord.gg/X4BgkBHavp` Unlock fast connections and elevate your experience with your very own API key 🚀 You can monitor your Node with the following steps: Log in to your server with SSH: ssh [email protected] Then, run the following command to monitor your node: $ solv m
It's done! Your Solana RPC node is now deployed.
It will take some time to synchronize with the Solana network.
Debugging & Monitoring
After deployment, you can check the status of the Solana RPC node with the following command:
ssh solv@<your-server-ip> solv m
solv is an alias for agave-validator -l /mnt/ledger.
This setting is added to ~/.profile during the RPC node deployment.SLV RPC Commands
Usage: slv rpc Version: 0.9.700 Description: 🛠️ Manage Solana RPC Nodes 🛠️ Options: -h, --help - Show this help. Commands: init - 🚀 Initialize a new RPC node configuration deploy - 📦 Deploy RPC Nodes list - 📋 List RPC Nodes setup:firedancer - 🔥 Setup/Update Firedancer Validator update:firedancer - 🔄 Update Firedancer Version build:solana-cli - 🛠️ Build Solana CLI from Source install:solana - ➡️ Install Solana CLI Binary update:script - ⚙️ Update RPC Startup Config update:geyser - ⚡️ Update Geyser Version start - 🟢 Start RPC stop - 🔴 Stop RPC restart - ♻️ Restart RPC cleanup - 🧹 Cleanup RPC - Remove Ledger/Snapshot Unnecessary Files get:snapshot - 💾 Download Snapshot with aria2c update:allowed-ips - 🛡️ Update allowed IPs for mainnet RPC nodes