# Installation

**Step 1: Clone the Light Node Repository**

```
git clone https://github.com/Layer-Edge/light-node.git
cd light-node
```

**Step 2: Install Required Dependencies**

Ensure the following dependencies are installed:

* **Go**: Version 1.18 or higher
* **Rust**: Version 1.81.0 or higher 

  <pre data-full-width="true"><code>curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
  </code></pre>
* **Risc0 Toolchain**: If not installed, run:

  <pre data-full-width="true"><code>curl -L https://risczero.com/install | bash &#x26;&#x26; rzup install
  </code></pre>
* **LayerEdge gRPC Endpoint**: Ensure access to a LayerEdge node for seamless communication.

**Step 3: Configure Environment Variables**

Set up the required environment variables in your terminal session or add them to a `.env` file:

```
GRPC_URL=grpc.testnet.layeredge.io:9090
CONTRACT_ADDR=cosmos1ufs3tlq4umljk0qfe8k5ya0x6hpavn897u2cnf9k0en9jr7qarqqt56709
ZK_PROVER_URL=http://127.0.0.1:3001
# Alternatively:
ZK_PROVER_URL=https://layeredge.mintair.xyz/
API_REQUEST_TIMEOUT=100
POINTS_API=https://light-node.layeredge.io
PRIVATE_KEY='cli-node-private-key'
```

Ensure that the `ZK_PROVER_URL` matches the server where the Merkle service is running.

**Step 4: Start the Merkle Service**

Before running the Light Node, start the Merkle service:

```
cd risc0-merkle-service
cargo build && cargo run
```

Wait until the Merkle service is fully initialized before proceeding.

**Step 5: Build and Run the LayerEdge Light Node**

In a separate terminal window, navigate to the root directory and execute:

```
go build
./light-node
```

Ensure that the Light Node is running **independently** and correctly **connected** to the Merkle service.

***

#### **Connecting CLI Node with LayerEdge Dashboard** <a href="#connecting-cli-node-with-layeredge-dashboard" id="connecting-cli-node-with-layeredge-dashboard"></a>

To link your CLI node with the dashboard for **analytics**:

**Fetch Points via CLI**

```
https://light-node.layeredge.io/api/cli-node/points/{walletAddress}
```

Replace `{walletAddress}` with your **actual CLI wallet address**.

**Connect to Dashboard**

1. Navigate to [dashboard.layeredge.io](https://dashboard.layeredge.io/)
2. Connect your wallet
3. Link your CLI node’s Public Key

**Important Notes:**

* One CLI wallet **can only** link to one dashboard wallet.
* Linking is **mandatory**, even if the CLI and dashboard wallets are identical.

**Dashboard Monitoring Features**

* **Node status** (Active/Inactive)
* **Points tracking & detailed analytics**

***

#### **Logging & Monitoring** <a href="#logging-and-monitoring" id="logging-and-monitoring"></a>

The node provides comprehensive logs for:

* **Merkle tree discovery**
* **ZK proof generation and verification**
* **Submission status**
* **Performance optimizations** (tree sleep state)

***

#### **Security Best Practices** <a href="#security-best-practices" id="security-best-practices"></a>

* Always store keys, mnemonics, and AUTHKEY offline.
* Utilize firewall protections and secure SSH configurations.
* Regularly update nodes from official LayerEdge sources.

***

#### **Troubleshooting Common Issues** <a href="#troubleshooting-common-issues" id="troubleshooting-common-issues"></a>

**Issue:** gRPC connection is inactive. **Solution:** Verify gRPC connection settings.

**Issue:** Risc0 prover service is not running. **Solution:** Restart the prover service and check logs.

**Issue:** Incorrect wallet or signature configurations. **Solution:** Double-check wallet addresses and environment variables.

Consult detailed logs for more specific errors.


---

# 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://documentation.codeblocklabs.com/blockchain-nodes/layeredge/installation.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.