Instruction for node operators
Find the system requirements at the link.
Installation script
In order to launch a EYWA Oracle node, you should use the installer script install.py. The script greatly simplifies the process of running a node and automates the following steps:
Install and configure the necessary environment for deployment and operating the EYWA Oracle node;
Takes care of node directory setup in server's filesystem;
Downloads actual EYWA Oracle docker image and configurations files;
Prerequisites
Make sure that Git is installed on the node. Instructions for the Git installation can be found here.
Before running the script on the server, make sure that the latest version of Python is installed. If not, install the python package, which provides the current release of Python3.
Process of installation
First, copy the repository with the following command:
Then navigate to the directory of the copied repository with the following command:
Next, execute the node installation script with the following command:
During execution, the script will ask you to do the following:
Enter your node name. Node name usually matches the hostname and this will be the name of the docker container;
Select the network to connect to. For the PoA mainnet you need to select option 1 - prod.
Enter the secret password for the keystore of the node. This password is needed to store node private keys in encrypted form.
Choose between automatic and manual mode. After the line "Manual or fully automatic installation (A/m)" enter A (upper case!) and press Enter to confirm.
After that the user will be shown the public address of the node in the Fantom and asked to top up the balance of that node with FTM and EYWA tokens:

At this point you should credit the balance of the node in the required amount of tokens. Minimum required amount for deposit:
5 FTM. FTM assets are needed for a node to be able to send transactions to EYWA governance smart contacts located in the Fantom network. These contracts control the operation of the EYWA protocol.
1 EPOA. While the oracle network is in PoA mode, PoA participants need to have EYWA-PoA tokens to get into the number of active cross-chain call validators. To get EYWA technical tokens for the PoA mainnet, the users need go to Zealy page and complete 3 quests:
Mainnet Node name request
Mainnet IP address request
Mainnet Public node key request
The data will be processed after which the technical team will send you the EYWA technical token to your address.
After the balance will be credited with the required number of tokens, press Enter. This will register the node in the smart-contract. As registration passes, the oracle will be restarted and will start synchronizing with the network of oracles. To understand that your node is in sync with the active set of validators, you can use the log view command. See the Node sync section for details.
Keystore backup
To ensure that in case of emergency you will not lose the private keys of your node, we strongly recommend that you make a backup of the keystore of the node.
Backup your /app/.data/keys folder which contains all network keys and private keys. The keys are encrypted, the password for encoding is requested by the script.
Node sync
In order to check the synchronization status of your node you can use the following command:
In the received answer you can see the height of the block to be processed:

If the height of the processed block is the same as the height of the block in the network of active validators, it means that the node is synchronized. You also can see the status of sync via the API http://127.0.0.1:8081/v1/sync_state * You should see FULLY_SYNCED. In order to view the version, use the following command:
Additional information
During the PoA mainnet, it is important for our technical team to collect information about the operation of nodes in order to optimize the process and make it as convenient and seamless as possible.
EYWA oracle needs to accept connections from the Internet on the network port 45554.
Opening a port for p2p communications :
Run the command to leave access to node metrics only for our system.
If you also want to get metrics in your Prometheus installation, use the following command:
Instead of IP, write the ip address of your Prometheus:
Instructions for transferring a node to a new server.
After the node has been installed on the server and the keys have been created, it is necessary to save a backup folder copy with these keys (backup) to be able to transfer the node to a new server.
To migrate a node to a new server, you need to perform the following steps:
Check the id of the container docker with the node:
Stop the node on the old server:
On the new server, download the backup (App folder) with the keys from the node you wish to move to the root folder
In that folder, delete the levelbd folder, which is located at the following path: app/.data/levelbd
Run the installation script on the new server
Last updated