Non-producing Node Setup

Goal

This section describes how to set up a non-producing node within the ARISEN network. A non-producing node is a node that is not configured to produce blocks, instead it is connected and synchronized with other peers from an ARISEN based blockchain, exposing one or more services publicly or privately by enabling one or more aos Plugins, except the producer_plugin.

Before you begin

Install the ARISEN software before starting this section.
It is assumed that aos, arisecli, and awallet are accessible through the path. If you built ARISEN using shell scripts, make sure to run the Install Script.
Know how to pass aos options to enable or disable functionality.

Steps

To setup a non-producing node is simple.

1.Set Peers
2.Enable one or more available plugins

1. Set Peers

You need to set some peers in your config ini, for example:

# config.ini:

p2p-peer-address = 106.10.42.238:9876

Or you can include the peer in as a boot flag when running aos, as follows:

aos ... --p2p-peer-address=106.10.42.238:9876

2. Enable one or more available plugins

Each available plugin is listed and detailed in the aos Plugins section. When aos starts, it will expose the functionality provided by the enabled plugins it was started with. For example, if you start aos with state_history_plugin enabled, you will have a non-producing node that offers full blockchain history. If you start aos with http_plugin enabled, you will have a non-producing node which exposes the ARISEN RPC API. Therefore, you can extend the basic functionality provided by a non-producing node by enabling any number of existing plugins on top of it. Another aspect to consider is that some plugins have dependencies to other plugins. Therefore, you need to satisfy all dependencies for a plugin in order to enable it.