> For the complete documentation index, see [llms.txt](https://docs.zerowave.my.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerowave.my.id/testnet/bevm/installation.md).

# Installation

## Overview

An **archive node** is responsible for preserving the historical records of block transactions. Typically, this type of node is utilized as an **RPC (Remote Procedure Call)** endpoint. The role of RPC in our network is indispensable as it bridges the gap between users, decentralized applications (dApps), and the blockchain, leveraging WebSocket and HTTP endpoints for this connection. For instance, in our network, the public endpoints deploy archive nodes to facilitate seamless access to BEVM chains for all users.

It is advisable for **DApp** developers to set up their own dedicated RPC archival node. This approach not only allows them to fetch the blockchain data they require but also reduces their reliance on public infrastructures, which may suffer from slower response times and restricted access due to heavy usage and rate limits.

## Docker Installation

### install Docker on VPS

```
curl -fsSL https://get.docker.com -o get-docker.sh
```

run the shell 

```
sudo sh get-docker.sh
```

### Mapping Host for Store Data

```
cd /var/lib
```

create new directory

```
mkdir node_bevm_test_storage
```

### Fetch Docker Image

```
sudo docker pull btclayer2/bevm:v0.1.1
```

### Run Program

```docker
 sudo docker run -d -v /var/lib/node_bevm_test_storage:/root/.local/share/bevm btclayer2/bevm:v0.1.1 bevm "--chain=testnet" "--name=your_node_name" "--pruning=archive" --telemetry-url "wss://telemetry.bevm.io/submit 0"
```

{% hint style="info" %}
replace "--name:your\_own\_name" with evm address to join incentives testnet
{% endhint %}

## Telmetry Check

Check your node in this link

{% embed url="<https://telemetry.bevm.io/>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://docs.zerowave.my.id/testnet/bevm/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.