# Running a Solaxy Rollup Node

This guide explains how to download, configure, and run the `svm-rollup` binary to operate a Solaxy rollup node connected to the Celestia data availability layer.

Running a node allows participants to support network infrastructure, maintain state replication, and prepare for validator participation as the network expands.

#### 💻 Hardware Requirements

For reliable rollup node performance, the following specifications are recommended:

* **CPU:** 16 vCPUs
* **Memory:** 32 GiB RAM
* **Storage:** 1 TB disk

These specifications ensure stable syncing, transaction processing, and state management under sustained network activity.

#### 📦 System Prerequisites

Supported environment:

* **Linux x86\_64** (Ubuntu 24.04 or compatible)

Install required system dependencies:

```bash
sudo apt update
sudo apt install -y build-essential cmake pkg-config libudev-dev
```

#### ⬇️ Download the Rollup Binary

The latest Solaxy rollup binary bundle is distributed through a stable release endpoint.

Download the binary and genesis state:

```bash
curl -LO https://download.solaxy.io/solaxy/svm-rollup.tar.gz
curl -LO https://download.solaxy.io/solaxy/state_export.svmd
```

#### 📂 Extract the Bundle

Unpack the release archive and place the genesis state file in the appropriate directory:

```bash
tar -xzf svm-rollup-latest.tar.gz
cp state_export.svmd svm-rollup/genesis/state_export.svmd
cd svm-rollup
```

After extraction, the directory structure will resemble:

```
svm-rollup/
  svm-rollup        # Rollup binary
  config.toml       # Rollup configuration
  genesis/          # Genesis configuration and state
```

#### ⚙️  Configuration

Provide your own configuration on how to access the Celestia network, by modifying the `da` section in the `config.toml` .

You **must** configure the following fields:

* `rpc_url`
* `grpc_url`
* `signer_private_key`

#### 🪙  Wallet for prover rewards

Configure the wallet you want to receive rewards on in the `config.toml` file. In the `proof_manager` section, the `prover_address` key, and also in the `sequencer` section the `rollup_address` key - both should point to your preferred wallet address.\
\
**Note:** The address must exist on the rollup and be funded in order to post the required bond.

Current bond values:

* Sequencer minimum registration bond: `10,000` SOLX lamports.
* Current genesis prover bond: `200,000` SOLX lamports.
* A new community operator is **not** pre-funded in genesis, so you need SOLX on your rollup address before registering.
* Hold enough TIA to submit blobs to Celestia

#### ▶️ Start the Rollup Node

Launch the rollup node:

```bash
export SOV_PROVER_MODE=skip
./svm-rollup --da-layer celestia --rollup-config-path config.toml --genesis-paths genesis

```

The node will begin syncing and connecting to the Celestia data availability layer.

#### 🔎 Verify Node Operation

Once the node is running, verify connectivity via the RPC endpoint:

{% code overflow="wrap" %}

```bash
curl -s http://localhost:8899/rpc -X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"getAccountInfo","params":["SysvarC1ock11111111111111111111111111111111",{"encoding":"jsonParsed"}]}'
```

{% endcode %}

A valid JSON response confirms the node is operational and serving RPC requests.

#### 🌐 Network Context

The Solaxy rollup operates as a modular Layer 2 built using the Sovereign SDK and secured by Celestia for data availability. Running a node contributes to:

* Network resilience
* State replication
* Infrastructure decentralization
* Validator readiness

As validator participation expands, this rollup node setup forms the foundation for broader community-operated infrastructure.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.solaxy.io/running-a-solaxy-rollup-node.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.