RPC & Block Explorers
Submit your deployment address to this form. We will provide engineering support and prioritize specific infrastructure needs.
Eclipse Testnet
Network Name | Eclipse Testnet |
---|---|
Description | Realistic to Mainnet but with no real economic value. |
RPC |
|
Block Explorers | |
Celestia Namespace |
Eclipse Devnet2
Network Name | Eclipse Devnet2 (Devnet1 is being deprecated) |
---|---|
Description | Simulates developer experience. |
RPC |
|
Block Explorers |
RPC Requirements
Our RPC specs reflect Solana's RPC node recommendations:
CPU: 16 cores / 32 threads, or more
RAM: 512 GB or more if
account-index
is usedDisk:
Consider a larger ledger disk if longer transaction history is required
Accounts and ledger should not be stored on the same disk
Setup an RPC Node
First, make sure that you've properly set up your Solana CLI: solana --version
Eclipse uses the Solana JSON-RPC. You should use Solana version 1.17.
Next, set the RPC correctly. In this example, we use Eclipse Devnet2: solana config set --url https://staging-rpc.dev2.eclipsenetwork.xyz
Create a keypair: solana-keygen new -o validator-keypair.json
You can modify the following script to boot your RPC node:
Note that you should not run a full node behind NAT.
You can also spin up your own dedicated RPC node with one of our RPC provider partners.
Last updated