V6 Mainnet Node Instructions
Step-by-step guide to run a V6 Mainnet Node, brought to you by OriginTrail Club and the DKG Node Alliance.
You must create a total of 4 wallets for the following step.
# | Wallet | Description |
|---|---|---|
1 | EVM Operational wallet | Hot wallet for non admin node operations
Example: Metamask wallet |
2 | EVM Management wallet | Cold wallet for admin node operations
Example: Ledger |
3 | Substrate Operational wallet | Hot wallet to map with wallet #1
Example: polkadot.js, Talisman wallet |
4 | Substrate Management wallet | Cold wallet to map with wallet #2
Example: Ledger |
Mapping a hardware EVM wallet (such as Ledger) to a hot substrate wallet (such as polkadot.js or Talisman wallet) could expose your funds to the Internet since both EVM and substrate wallets can have full access to your funds on the Polkadot Ecosystem. Waiting for OTP Ledger support before mapping is strongly advised to protect your funds.
For the time being, the safest method to run a mainnet node is highlighted in the temporary safe method to run a mainnet node section.
By using the information found here, add the OriginTrail Mainnet Network on your MetaMask client and switch to it.
Fund your wallets in step 1 with OTP tokens. For example, you can use TRAC holder OTP reward or teleport OTP bounty to fund your wallets.
You can also ask for some dust on OriginTrail Node Community. You need at least 2 OTP (1 OTP for ED amount and the other for transations) on your substrate wallets (wallet 3 and 4 from step 1)
Once the funding of both substrate wallets are completed, head to the mapping interface and select Parachain Mainnet.
Your goal here is to map wallet 1 and 3 together, and wallet 2 and 4 together from step 1.
To do so, connect to the mapping interface with the appropriate MetaMask wallet and paste the corresponding substrate wallet. 2 pop-ups will follow and sign both transactions.
If mapping doesn't prompt you with 2 transactions, try disabling all other extensions and restart your browser. You can also use a different browser. Choose between Chrome, Brave, Firefox.
Repeat for wallet 2 and 4 from step 1 and you would have completed the mapping process for your node.
Once the TRAC token is acquired, you must teleport your tokens to the OriginTrail Parachain in order to use them on the parachain. Follow the Teleportation Guide for a complete set of instructions.
Reminder:
OTP is used as gas to send teleported TRAC so always have at least 2 OTP on each wallet containing teleported TRAC.
To view your TRAC balance on Metamask, first switch your network to OriginTrail Parachain Network, then add the TRAC token address using the import function
0xFfFFFFff00000000000000000000000000000001
In order to deploy your OriginTrail V6 node, you will need a Linux server with the following minimum recommended hardware:
- 4GB RAM
- 2CPUs
- 50GB HDD space
Log in to the server as root. You cannot use sudo and run this script. The command "npm ci" might fail.
Gather the following information:
Value | Description |
|---|---|
EVM_OPERATIONAL_WALLET | Public address of wallet #1 in step 1 |
EVM_OPERATIONAL_PRIVATE_KEY | Private key of wallet #1 in step 1 |
EVM_MANAGEMENT_WALLET | Public address of wallet #2 in step 1 |
SHARES_TOKEN_NAME | Your choice of token name |
SHARES_TOKEN_SYMBOL | The token symbol of your token name |
Run the one-liner installer script:
cd /root/ && curl https://raw.githubusercontent.com/OriginTrail/ot-node/v6/release/mainnet/installer/installer.sh --output installer.sh && chmod +x installer.sh && ./installer.sh
You must choose a SQL password for the installer to work. Do not leave that field empty.
Reminder:
In order to use aliases to quickly check node logs, start/stop/restart node, change node config, you must execute the following script after the installation:
source ~/.bashrc
Once the sourcing is done, try the following:
otnode-logs
otnode-start
otnode-stop
otnode-restart
otnode-config
Even though your node is online, your node does not have any stake nor ask price, which will be covered on Step 7. However, before you continue, please read the following:
After successfully installing your V6 node, make sure you visit https://girraph.com/alliance to register your node to the DKG Node Alliance.
The benefits of joining the DKG Node Alliance include special access to a private Telegram channel, exclusive node support by top community members, node monitoring and maintenance scripts, collaboration to maintain a healthy DKG network, voting and governance and more to come.
The Node Alliance will leverage the DKG to become a DAO and currently occupies over 50% of the DKG V6 Node network.
Currently DKG Node Alliance members include Amos, LuKu, CosmiCloud, Calvin and myself just to name a few.
Houston V6 Node Command Center is an interface to help manage your node and view network statistics.
First, log in with your management and operational EVM wallets;
Go to tab "Service Tokenomics";
Input your ask price and sign the transaction. The team default is 0.24/(epoch * KB);
Input the amount of stake you want. Minimum stake is 50,000 TRAC;
Restart your node:
systemctl restart otnode
The installer above will only set up all the prerequisites and node files. You must run 2 scripts to create the node profile and set your service ask price.
First, stop the node:
systemctl stop otnode
Gather the following information:
Value | Description |
|---|---|
EVM Operational wallet private key | private key from wallet 1 in step 1 |
EVM Management wallet private key | private key from wallet 2 in step 1 |
Hub Contract Address | 0x5fA7916c48Fe6D5F1738d12Ad234b78c90B4cAdA
Check the official link to make sure it is the correct one. |
Ask price | Your price as a node runner to host assets.
Team default: 0.00375/(epoch * KB) |
rpcEndpoint | |
Stake | Your initial stake for your node
(minimum: 50000) |
Navigate to the current ot-node version folder:
cd /root/ot-node/current
Once you have all the information above, run the following command by replacing the values in <> with the correct information (you can also change the other options if needed):
Set the stake of your node:
npm run set-stake -- --rpcEndpoint=https://astrosat-parachain-rpc.origin-trail.network/ --stake=50000 --operationalWalletPrivateKey=<private_key> --managementWalletPrivateKey=<private_key> --hubContractAddress=0x5fA7916c48Fe6D5F1738d12Ad234b78c90B4cAdA
Set the service ask of your node:
npm run set-ask -- --rpcEndpoint=https://astrosat-parachain-rpc.origin-trail.network/ --ask=0.24 --privateKey=<operational_wallet_private_key> --hubContractAddress=0x5fA7916c48Fe6D5F1738d12Ad234b78c90B4cAdA
Once you are done, restart the node:
systemctl restart otnode
This is when your initial stake of 50k TRAC or above is sent from your initial wallet to your node profile contract.
Check the logs, everything should be completed!
journalctl -u otnode --output cat -fn 100
Reminder:
You can now use aliases such as otnode-logs to quickly view logs without having to type the entire string above!
- 1.
- 1.1 main wallet pair to receive your teleported TRAC and OTP bounty
- 2.1 operational wallet pair for your node
- 3.1 management wallet pair for your node
- 2.Receive your teleported TRAC and OTP bounty on main mapped wallet (wallet #1 above)
- 3.Send some teleported TRAC to management evm wallet (wallet #3 above), and some OTP to op / management wallets
- 4.Set up your node following the instructions above
- 5.When OTP is supported by ledger, change your management and operational wallet addresses to a brand new ledger evm + ledger otp mapped wallet
Last modified 34m ago