Joining
How to join THORChain as an Node.

Joining THORChain

Now that you have a THORNode deployed in your Kubernetes cluster, you need to start operating your node to join the network.
There are a couple of steps to follow to do so.

1. Check your current node status

The first step would be to make sure your deployment was successful and your node is running correctly. _**_To check the current status of your node, you can run the command status from the node-launcherrepository on your terminal:
1
make status
Copied!
You will get an output along those lines, the example below is for a testnet node:
1
________ ______ ___ _ __ __
2
/_ __/ // / __ \/ _ \/ |/ /__ ___/ /__
3
/ / / _ / /_/ / , _/ / _ \/ _ / -_)
4
/_/ /_//_/\____/_/|_/_/|_/\___/\_,_/\__/
5
ADDRESS tthor13hh6qyj0xgw0gv7qpay8thfucxw8hqkved9vr2
6
IP
7
VERSION 0.0.0
8
STATUS Unknown
9
BOND 0.00
10
REWARDS 0.00
11
SLASH 0
12
PREFLIGHT { "status": "Standby", "reason": "node account has invalid registered IP address", "code": 1 }
13
API http://:1317/thorchain/doc/
14
RPC http://:26657
15
MIDGARD http://:8080/v2/doc
16
CHAIN SYNC BLOCKS
17
THOR 55.250% 37,097/67,144
18
BNB 99.915% 155,426,471/155,559,013
19
BTC 2.399% 227,986/678,340
20
ETH 7.764% 947,182/12,199,994
21
LTC 0.012% 6,526/1,818,000
22
BCH 2.293% 197,340/682,404
Copied!
Your node is running but as you can see in the `Preflight` section, your node is not yet ready to be churned in and currently is in standby status, since your node has no IP address setup yet.
But to be able to set up the node IP address, you first need to get it registered in the chain by sending your BOND.
Before sending the BOND, verify that your THORNode is fully synced with connected chains. Connected chains such as Ethereum & Bitcoin may take a day to sync. If your node is fully bonded and is selected to churn in to THORChain as ACTIVE without fully syncing all connected chains, you will immediately get slashed for missing observations, and lose money. It is normal to see Ethereum sit on 99.999% for many hours - be patient.

2 - Send a small BOND (recommend 100-1000)

1) You will do a "Deposit" transaction using native THORChain RUNE (not ERC20 or BEP2 RUNE). This is an internal MsgDeposit transaction (different from a MsgSend to another wallet). There is no destination address -- use an appropriate wallet such as ASGARDEX Electron. The Bond is locked in a module controlled by the state machine.
2) Deposit your BOND using the memo BOND:<thornode-address> (or use an appropriate GUI that does this memo for you). Start small, the bond will be picked up.
Some make commands during setup require RUNE (0.02 to 1.0) to execute into the state machine to prevent DDoS. If your bond is too small (e.g. 1 RUNE) you may run out and not be able to complete the setup until adding more.
Bonding using BOND option in ASGARDEX
Give the network 3-5 seconds to pick up your bond. To verify it has received your bond, run the following:
1
curl https://thornode.thorchain.info/thorchain/node/<node-address>
Copied!
If you run make status again, you should see this:
1
________ ______ ___ _ __ __
2
/_ __/ // / __ \/ _ \/ |/ /__ ___/ /__
3
/ / / _ / /_/ / , _/ / _ \/ _ / -_)
4
/_/ /_//_/\____/_/|_/_/|_/\___/\_,_/\__/
5
ADDRESS tthor13hh6qyj0xgw0gv7qpay8thfucxw8hqkved9vr2
6
IP
7
VERSION 0.0.0
8
STATUS Whitelisted
9
BOND 1000.00
10
REWARDS 0.00
11
SLASH 0
12
PREFLIGHT { "status": "Standby", "reason": "node account has invalid registered IP address", "code": 1 }
13
API http://:1317/thorchain/doc/
14
RPC http://:26657
15
MIDGARD http://:8080/v2/doc
16
CHAIN SYNC BLOCKS
17
THOR 55.250% 37,097/67,144
18
BNB 99.915% 155,426,471/155,559,013
19
BTC 2.399% 227,986/678,340
20
ETH 7.764% 947,182/12,199,994
21
LTC 0.012% 6,526/1,818,000
22
BCH 2.293% 197,340/682,404
Copied!
As you can see, it is in standby but does not have an IP registered yet. This is needed for peer discovery.

3 - Setup Node IP Address

You must tell THORChain your IP-Address for its address book and seed-service to run properly:
1
make set-ip-address
Copied!
If you run the status command again, you should now see a different message for the Preflight section saying you need to set your node keys.
Once your IP address has been registered for discovery, you can use your own host for queries.

4 - Setup Node keys

Tell THORChain about your public keys for signing sessions:
1
make set-node-keys
Copied!
If you run the make status command again, you should now see that your node is in status “ready” and is now ready to be churned in the next rotation.

5 - Set Version

Make sure your node broadcasts its latest version, else you won't churn in since THORChain enforces a version requirement. This version will appear in your make status. If you are on 0.0.0 then you haven't set your version:
1
make set-version
Copied!

6 - Send Final Bond

If you followed steps 1-5 above, your preflight will be saying:
1
PREFLIGHT { "status": "Standby", "reason": "node account does not have minimum bond requirement: 100000000000/30000000000000, "code": 1 }
Copied!
To address this, send the remaining bond, that is higher than the minimum bond. You can find that quantity on https://thornode.thorchain.info/thorchain/constants and look for MinimumBondInRune. During Chaosnet some values may be override with MIMIR. If you finally run make status you should see this, with keyword "Ready":
1
________ ______ ___ _ __ __
2
/_ __/ // / __ \/ _ \/ |/ /__ ___/ /__
3
/ / / _ / /_/ / , _/ / _ \/ _ / -_)
4
/_/ /_//_/\____/_/|_/_/|_/\___/\_,_/\__/
5
ADDRESS tthor13hh6qyj0xgw0gv7qpay8thfucxw8hqkved9vr2
6
IP 1.2.3.4
7
VERSION 0.54.0
8
STATUS Standby
9
BOND 300,099.96
10
REWARDS 0.00
11
SLASH 0
12
PREFLIGHT { "status": "Ready", "reason": "OK", "code": 0 }
13
API http://1.2.3.4:1317/thorchain/doc/
14
RPC http://1.2.3.4:26657
15
MIDGARD http://1.2.3.4:8080/v2/doc
16
CHAIN SYNC BLOCKS
17
THOR 100.000% 67,144/67,144
18
BNB 100.000% 155,559,013/155,559,013
19
BTC 100.000% 678,340/678,340
20
ETH 100.000% 12,199,994/12,199,994
21
LTC 100.000% 1,818,000/1,818,000
22
BCH 100.000% 682,404/682,404
Copied!

Bonding The Right Amount

Although your node is ready to be churned in, it doesn’t mean it will be the next one to be selected since someone else could have posted a higher bond than you. To maximise chances of a quick entry, monitor Midgard to see what everyone else is bonding and try to outbid them. Keep an eye on maximumStandbyBond and make sure you are bonding higher than that amount.
1
curl http://52.221.153.64:8080/v2/network | json_pp
2
3
resp:
4
"bondMetrics" : {
5
"minimumActiveBond" : "10001000000000",
6
"medianStandbyBond" : "1010000000000",
7
"medianActiveBond" : "15001000000000",
8
"averageStandbyBond" : "1010000000000",
9
"maximumActiveBond" : "15001000000000",
10
"averageActiveBond" : "12006800000000",
11
"maximumStandbyBond" : "1010000000000",
12
"totalStandbyBond" : "1010000000000",
13
"totalActiveBond" : "60034000000000",
14
"minimumStandbyBond" : "1010000000000"
15
}
Copied!
Some useful community sites to assist monitoring your node are https://thorchain.network, https://thorchain.net and https://thorchain.live. You should use your API endpoint as an authoritative reference.
The endpoint will show data on average, median, total, minimum and maximum bond amounts. For fastest entry, bond higher than the current maximum.
RUNE is always displayed in 1e8 format, 100000000 = 1 RUNE

Bonding More

At any time during standby, you can bond more by making an additional BOND transaction with memo:
BOND:<thornode-address>
Only the original wallet that did the first BOND will be able to LEAVE/UNBOND. You can top up BOND using a different wallet but make sure you keep the private key to the original BOND wallet secure and accessible.
You can also remove some of your bond whilst you are on standby, using the UNBOND memo.
Last modified 1mo ago