All nodes are set up and connected to the network using pre-compiled juneogo executable files. In later stages of the project, the juneogo protocol will be open source.
Depending on its configuration, a node can be of the following types:
This node can access blockchain data and propose transactions through RPC calls. However, it is not a validator of the Juneo Primary Network or any Multi-Chain Networks (MCNs).
An API Node is the same as a Regular node, however it supports RPC calls from remote machines.
Validator nodes have all of the capabilities of a Regular Node/ API node, but they also participate in the network's consensus mechanism by validating transactions.
An archive node has database pruning disabled for certain chains it is validating, meaning it will have archive data of all historical states of those chains.
{% hint style="info" %} A node can be several types simultaneously - an Archive Node for one chain it is validating, but a Validator node for another chain. {% endhint %}
For more details about the Network Architecture, see the Juneo Litepaper or visit juneo.com.
| Set up and Connect a node manually | How to set up and connect to the Socotra Testnet network without the installer script | |
| Create a Multi-Chain Network | How to create a MCN on the Socotra Testnet | |
| Deploy a VM | How to deploy a VM on your MCN |
| Node Backup and Restore | How to backup important files to be able to restore a node. |
|---|
| Add a node to the Validator set | How to add a node to the Validator Set |