Comment on page
RPC & Block Explorers
Submit your deployment address to this form. We will provide engineering support and prioritize specific infrastructure needs.
The public Eclipse Devnet RPC is
https://staging-rpc.dev.eclipsenetwork.xyz
.- CPU: 16 cores / 32 threads, or more
- RAM: 512 GB or more if
account-index
is used - Disk:
- Consider a larger ledger disk if longer transaction history is required
- Accounts and ledger should not be stored on the same disk
First, make sure that you've properly set up your Solana CLI:
solana --version
Eclipse Devnet uses the Solana JSON-RPC. You should use Solana version 1.14.
Next, set the RPC correctly:
solana config set --url https://staging-rpc.dev.eclipsenetwork.xyz
Create a keypair:
solana-keygen new -o validator-keypair.json
You can modify the following script to boot your RPC node:
#!/bin/bash
exec solana-validator \
--identity validator-keypair.json \
--known-validator FdFZZ9TpRJTfynYd1Apk3MP77wRwuEJ2Y4pDrq8ULJM6 \
--only-known-rpc \
--full-rpc-api \
--no-voting \
--ledger /mnt/ledger \
--log /home/eclipse/eclipse-rpc.log \
--rpc-port 8899 \
--rpc-bind-address 0.0.0.0 \
--private-rpc \
--dynamic-port-range 8201-8300 \
--entrypoint 34.27.6.58:8200 \
--expected-genesis-hash CcicZJ8JVnQQvF4WFimQN1aW6pou5qpr5JMFAjFJ88DX \
--wal-recovery-mode skip_any_corrupted_record \
--limit-ledger-size
The Eclipse RPC can be explored via a variety of block explorers:
- You can use any existing Solana block explorer such as Solscan or Solana Explorer. For Solscan, we've configured this link which points to the correct RPC.
- You can also use the Modular Cloud Explorer which aims to provide visibility into Celestia DA blobs and other components of the modular stack: Modular Cloud Eclipse Devnet Explorer