Preparation for V8 DKG Core Node deployment
This page will help you prepare all the requirements for the V8 DKG Core Node installation process.
Before initiating an installer, there are a few important requirements that each node runner should prepare in order to initialize the v8 DKG node successfully.
1. Hardware requirements:
In order to deploy your V8 DKG node, you will need a Linux server with the minimum recommended hardware as presented below:
4GB RAM
2 CPUs
50GB HDD space
Make sure that you have root access to your server.
The installer script provided in these instructions is designed for installing the OriginTrail node on Ubuntu 20.04 LTS and 22.04 LTS distributions. It is also possible to install the OriginTrail V8 Core Node on other systems, but it would require modifications to the installer script. If you have any such modifications in mind, we highly encourage your contributions. Please visit our GitHub for more information.
During the v8 DKG Core Node installation process, the interactive installer will prompt you to input all the required information outlined below. Please make sure that you have all the requirement inputs prepared before running the installer.
2. Important note on Core Node keys (wallets):
DKG Core Nodes periodically execute blockchain transactions, for which they need node keys (wallets) of the H160 type (Ethereum). There are two categories of keys associated with DKG nodes however:
operational keys, which are used directly by the node to make blockchain transactions. The nodes requires their private keys to be accessible (stored in the node configuration file), so that the node can sign transactions
admin keys, which are used by the node operator, and not by the node itself. Admin keys are intended for administrative transactions to be done by the node operator (such as rotating keys), meaning the nodes don't need access to their private keys (doesn't need to be stored on the node server or configuration file). An admin key can be stored with a hardware wallet, a multisig or any other Ethereum compatible wallet of your preference.
To get a DKG node running, you will need at least one operational key and one admin key. For more information on keys and their roles, please refer to the detailed documentation.
The OriginTrail DKG nodes operate with a two token system:
the TRAC token which is the native utility token of the DKG used for knowledge publishing, and
the native blockchain token of the chosen chain, used for interacting with DKG smart contracts (currently Base Sepolia only)
At the current stage, V8 DKG Core Nodes run on Base Sepolia blockchain which is Base testnet, and use Base Sepolia test TRAC tokens
3. Funding your Base Sepolia keys:
Acquire Base Sepolia ETH:
The list of Base Sepolia faucets can be found in the official Base documentation.
Acquire Base Sepolia TRAC:
In order to acquire TRAC on Base Sepolia network, you should use the Faucet bot provided by the team on our official Discord channels.
Once you join, go to "testnet-discussion" channel and send !help command as a message in order to see all available commands and tokens that it can provide.
In order to receive Base Sepolia TRAC, send the following message to the channel:
!fundme_v8_base_sepolia_trac <wallet_address>
Example:
!fundme_v8_base_sepolia_trac 0x0134a3e4...
Once executed, you will receive 60000 TRAC tokens to the provided wallet address.
In case of any problems with the Faucet, you can contact any team member on Discord for the assistance or send an email to tech@origin-trail.com
4. Acquire Base Sepolia RPC endpoint:
There are many RPC providers that host and provide Base Sepolia endpoints and its up to a node runner to choose the best possible option for their nodes.
Additionally, Base team provides a few free RPC endpoints which can be found in their official documentation, here.
5. Configure firewall on the server:
OriginTrail node requires the following ports to be allowed in order to properly operate.
8900 (default node API endpoint)
9000 (networking port for communication with other nodes)
Please keep in mind that different cloud providers use different security practices when it comes to configuring firewalls on the servers so make sure that firewall rules are configured according to their practices.
Last updated
