SolaxyEasyNode

One-line installer for a complete Solaxy node: SVM Rollup + Celestia Bridge Node + PostgreSQL + Web Dashboard.

                    ___
                ___/ _ \___
            ___/   (_)   \___
         __/                 \__
       _/    S O L A X Y        \_
     _/ _________________________ \_
    /__|_________________________|__\
   ///                             \\\
  ///═══════════════════════════════\\\
  \\\           ▀▀▀▀▀▀▀            ///
   \\\___________________________///
    \_____________________________/
        \_____________________/
           \_______________/
              \  \   /  /
               \  \ /  /
                \_   _/
                  \_/

Quick Install

curl -sSL https://raw.githubusercontent.com/Marcolist/SolaxyEasyNode/main/install.sh | bash

The installer shows progress bars for all downloads and extractions.

Why this exists

Running a Solaxy node currently requires multiple manual steps:

• Celestia build
• Rollup config
• Service wiring
• Monitoring setup

SolaxyEasyNode reduces setup time and provides a production-ready dashboard + Telegram alerts.

Screenshots

Node Dashboard

Telegram Bot

Node Map

What Gets Installed

Component	Description
svm-rollup	Solaxy SVM Rollup full node
Celestia Bridge Node	DA layer bridge node (Mainnet, with pruning)
PostgreSQL	Database for blocks, transactions, accounts
Go 1.26.1	Required to build Celestia v0.29.1-mocha from source
Dashboard	Web UI at http://<LAN_IP>:5555

Celestia Bridge Node

The installer uses a Celestia Bridge Node in pruning mode. The SyncFromHeight is set automatically to the genesis DA height from chain_state_zk.json, so no unnecessary blocks are synced.

	Bridge Node
Network	Celestia Mainnet (--p2p.network celestia)
Disk	~20-50 GB (with pruning window)
RAM	~4-8 GB
Sync	Hours (from genesis DA height)
Pruning	Dynamic — covers genesis-to-head + 48h buffer (min 720h)
RPC Auth	Skipped (--rpc.skip-auth) for stable rollup connection

After Installation

• Dashboard: http://<your-ip>:5555
• RPC Endpoint: http://127.0.0.1:8899
• Config: ~/svm-rollup/config.toml (also editable from the dashboard Settings panel)
• Logs: journalctl -u solaxy-node -f

Service Management

# Status
sudo systemctl status solaxy-node celestia-bridge solaxy-dashboard

# Restart
sudo systemctl restart solaxy-node

# Logs (follow)
journalctl -u solaxy-node -f
journalctl -u celestia-bridge -f

Or use the Settings panel in the dashboard to start/stop/restart services.

Dashboard Features

• Real-time sync progress for Solaxy and Celestia
• PostgreSQL stats (blocks, transactions, accounts)
• Server resource monitoring (CPU, memory, disk, network)
• Node identity and wallet info (LAN IP, hostname, public IP)
• Reward model & node roles reference
• Settings panel: Edit all config.toml values and manage services from the UI

Requirements

• Ubuntu 22.04 / 24.04 (or Debian-based)
• 4+ CPU cores, 8+ GB RAM, 100+ GB SSD
• Internet connection

File Structure

~/svm-rollup/
├── svm-rollup              # Node binary
├── config.toml             # Node configuration
├── node-wallet.json        # Solana keypair
├── genesis/                # Genesis state
│   └── chain_state_zk.json # Contains genesis_da_height for SyncFromHeight
└── data/                   # Chain data (grows over time)

~/dashboard/
├── app.py                  # Flask dashboard
└── templates/
    └── index.html

~/.celestia-bridge/         # Celestia bridge node store & keys

Systemd Services

Service	Description
celestia-bridge	Celestia bridge node (Mainnet, Restart=always)
solaxy-node	SVM rollup node (depends on Celestia + PostgreSQL)
solaxy-dashboard	Web dashboard on port 5555

Troubleshooting

# Check if all services are running
sudo systemctl status solaxy-node celestia-bridge solaxy-dashboard postgresql

# View recent errors
journalctl -u solaxy-node --since "10 min ago" --no-pager
journalctl -u celestia-bridge --since "10 min ago" --no-pager

# Restart everything
sudo systemctl restart celestia-bridge solaxy-node solaxy-dashboard

# If Celestia bridge fails to start, check core endpoint
nc -w 3 rpc.celestia.pops.one 9090 && echo "OK" || echo "NOT REACHABLE"

# If rollup can't connect to Celestia RPC, verify --rpc.skip-auth is set
grep ExecStart /etc/systemd/system/celestia-bridge.service