# Network Node Set-Up

This guide will help you set up a **Network (non-validator) BLOCX node** using Docker.

> 💡 Ideal if you want to support the network or explore the BLOCX chain without participating in consensus as a validator.

***

### Step 0: Clone the Repository

Start by cloning the official node setup repository:

```
git clone https://github.com/BLOCXTECH/BLOCX-Node-Setup.git
cd BLOCX-Node-Setup
```

***

###  Step 1: Install Docker

Run the helper script to install Docker on your server:

```
./docker-setup.sh
```

> This will install all required Docker components to run your node.

***

### Step 2: Launch the Setup Script

Now start the node setup process by running:

```
./initExecution.sh
```

Select the `init` option when prompted.
\
Then `start` option when prompted.

***

> ✅ You should see:
>
> ```
> [+] Running 3/3
> Container blocx-temp-execution-1  Started
> Container blocx-temp-beacon-1     Started
> Node started successfully.
> ```

***

### Your Node is Live!

Your **Network node** is now:

* Syncing with the BLOCX chain
* Connected to the network
* Contributing to network decentralization

***

### Alternative: Connect Directly via Public RPC

If you don’t want to set up your own node, you can directly connect to our live BLOCX RPC endpoint using the details below:

* **RPC URL**: `https://rpc.blocxscan.com`
* **Network Name**: `BLOCX. Mainnet`
* **Ticker**: `BLOCX`
* **CHAIN ID**: `86996`
* **Explorer URL**: `https://blocxscan.com/`

You can add this to your MetaMask, dApp, or wallet tools directly.

***

### You're Done!

You’ve either:

* Set up a **fully synced Network node**, or
* Connected directly via RPC for easier access

***


---

# 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://blocx.gitbook.io/blocx./get-started/network-node-set-up.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.