Skip to main content

Seed node: theory and starting

Introduction​

There are two types of nodes used in The Power Ecosystem:

  1. Consensus node. It is a node that connects to a chain and participates in Consensus along with other Consensus nodes.
  2. Seed node. It is a node that connects to a chain of nodes, receives a copy of a blockchain data, and provides it to the users upon a request. As opposed to Consensus nodes, Seed nodes don't participate in Consensus.

Seed nodes theory​

As determined above, Seed nodes store and spread the copy of blockchain data, but don't participate in Consensus on creating new blocks.

Seed nodes are necessary to undertake the extra-load caused by the increased quantity of users from the Consensus nodes, as well as minimize the security risks. So, the users connect to Seed nodes, receive their copy of blockchain data needed, and send their transaction into the blockchain.

How to use the Seed node?​

To use the Seed node:

  1. Check the prerequisites here.

  2. Download the node. Here you have two options:

    1. Download the node using the Docker image.
    2. Download the source code and build it (only for advanced users).

  3. Install Erlang (this step is applicable for Docker installation ONLY):

    Before starting Tea Ceremony you need to set up your environment by installing Erlang. You will need Erlang to run the Tea Ceremony client. You will not be able to start the node and connect to the chain without Tea Ceremony. To install Erlang, run:

    apt -y install erlang-base erlang-public-key erlang-ssl

    Note

    You need to install erlang-public key and erlang-ssl. Otherwise, Erlang will not operate properly!

  4. Get the power CLI:

    1. Get the power cli by running the following command:

      wget https://tea.thepower.io/tp

    2. Change the tp file mode to executable by running the following command:

      chmod +x tp

  5. Generate private key by running the following command:

    ./tp --genkey --ed25519

    As a result of this action, you will get the tpcli.key file. This file contains your private and public keys. Here is an example of this file. DON'T use the keys specified in this example:

    % cat tpcli.key
    {privkey,"302E020100300506032B6570042204204B1F52826447066469E7DBCA4E95CB0A03A2998D268C27885364D4AD7B7B0A8E"}.
    {pubkey,"302A300506032B6570032100667C84FB1195C73F97AE14430C2024490C0EA6490F6EC0C1DE3FAEB4B6B32251"}.
    caution

    You may share your public key when necessary, but never share your private key.

    Backup the file and continue.

  6. Rename the file tpcli.key to node.config.

:::caution

This and the following steps are crucial because you will NOT be able to start your node without genesis.txt and node.config files. You can find more information about these files here.

:::

  1. Delete all the contents of the file except the key (privkey line) (if any content present) and copy the following:

    {tpic,#{peers => [],port => 1800}}.
    {discovery,#{addresses => []}}.

    {privkey,"302E020100300506032B6570042204200011223344556677001122334455667700112233445566770011223344556677"}.

    {replica, true}.
    {upstream, [
       <PEER_ADDRESS>
    ]}.

    {hostname, <Hostname>}.

    {dbsuffix,""}.
    {loglevel, info}.
    {info_log, "log/info.log"}.
    {error_log, "log/error.log"}.
    {debug_log, "log/debug.log"}.
    {rpcsport, 1443}.
    {rpcport, 1080}.

    :::warning

    Use this guide for more information on node.config. :::

    :::caution

    You need to replace:

    • privkey with your private key;

    • hostname with your hostname;

    • upstream. It is obtained from The Power Ecosystem administrators.

      :::

  1. Build and run the node using the following guides. Which guide to use depends on the way you've downloaded the node:

    1. Use this guide to build and start the node from Docker image.
    2. Use this guide to build and start the node from sources.