Archive Node
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.
We maintain 4 different networks: the BEVM Mainnet, BEVM Canary, BEVM Testnet and BEVM Canary Testnet.
| Chain | Token |
|---|---|
BEVM Mainnet | BTC |
BEVM Canary | BTC |
BEVM Testnet | BTC |
BEVM Canary Testnet | BTC |
Requirements
Machine
NOTE
Storage space will increase as the network grows.
Archive nodes may require a larger server, depending on the amount and frequency of data requested by a dApp.
| Component | Requirement |
|---|---|
System | Ubuntu 20.04+ |
CPU | 2 cores |
Memory | 2 GB |
SSD | 300 GB (recommended) |
Ports
| Description | Port |
|---|---|
P2P | 30333 |
RPC | 8086 |
WS | 8087 |
ports 30333 and 30334 need to be opened for incoming traffic at the Firewall. Archive nodes should not expose WS and RPC ports to the public.
Installation
There are 2 different ways to run an BEVM Mainnet node:
Use Docker
Use Binary
Last updated