| content_title |
|---|
Non-producing Node Setup |
This section describes how to set up a non-producing node within the EOSIO-Taurus 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 EOSIO-Taurus based blockchain, exposing one or more services publicly or privately by enabling one or more Nodeos Plugins, except the producer_plugin.
- Install the EOSIO-Taurus software before starting this section.
- It is assumed that
nodeos,cleos, andkeosdare accessible through the system path. - Know how to pass Nodeos options to enable or disable functionality.
To setup a non-producing node is simple.
You need to set some peers in your config ini, for example:
# config.ini:
p2p-peer-address = 106.10.42.238:9876Or you can include the peer in as a boot flag when running nodeos, as follows:
nodeos ... --p2p-peer-address=106.10.42.238:9876Each available plugin is listed and detailed in the Nodeos Plugins section. When nodeos starts, it will expose the functionality provided by the enabled plugins it was started with. For example, if you start nodeos with state_history_plugin enabled, you will have a non-producing node that offers full blockchain history. If you start nodeos with http_plugin enabled, you will have a non-producing node which exposes the EOSIO-Taurus 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.