Network nodes
Live health of registered sanect RPCs. Auto-refresh every 30s.
| Node | Status | Height | Behind tip | Catching up | Response | EVM RPC |
|---|---|---|---|---|---|---|
| Pinging nodes… | ||||||
Want a .community-rpc.sanect.org URL for your node?
Subdomain claims are CLI-only — they require a secret token that lives on your node and is only readable by root. This prevents random visitors from claiming names for nodes they don't own.
On your node (with root SSH access), run:
cd /opt/sanect && git pull sudo bash scripts/sanect-publish-rpc.sh
The wizard walks through firewall, DNS, TLS, container env, and the subdomain claim in one flow. Reads the secret token locally and submits the claim authenticated.
Get listed on this page
Add these env vars on your sanect node and restart the container — your node appears here within 60 seconds.
EXPLORER_HEARTBEAT_URL=https://scan.sanect.com/api/network/heartbeat PUBLIC_RPC_URL=https://your-rpc-here.example.com # optional, set to advertise public RPC
Public node: setPUBLIC_RPC_URL to your reachable URL. The explorer pings it back to verify your node_id matches, then lists it publicly with real-time health stats.
Private node: leavePUBLIC_RPC_URL unset. Your node still appears on this dashboard (so you can confirm heartbeats are landing) but no URL is exposed publicly.
Warning: don't expose validators that hold significant stake without rate-limiting. Public RPC opens you to DoS amplification.