Introduction
Welcome to the GHOST TestNet 3.1 Launch Guide. In TestNet 2.0 we had 140 Nodes and ability to send $CSPR. With TestNet 3.1 there is a ton of stuff coming including further GHOST Eye updates, staking, slashing, etc. All existing TestNet 2.0 and 3.0 Full Nodes MUST update to TestNet 3.1 to take advantage of new functionality.
1. Prerequisites
Before you can proceed with launching you GHOST Node please make sure to go though the following guide:
- GHOST Chain Startup Guide – create the proper environment and install GHOST Chain.
- Testing Connectivity Guide – test whether or not you node can become a Boot Node and set proper firewall rules.
2. GHOST Chain Key Generation
Start with creating the following directory:
Get your username:
Give the user permission to the directory and substitute {USERNAME} for the one from previous command:
Generating Node Keys
To generate the node key use the following command:

3. Launching GHOST TestNet 3.1
Go to ghost-node
directory:
Remove ghost
ledger:
Make sure ghost-node
is up to date:
Recompile ghost-node
using starter.sh
and --release
flag. Make ghost-node service
being able to be started by default user using --make-global
:
The default option is capitalized which is N
, you can also press Enter to choose the default option. In this case we want to recompile so type y
and press Enter to proceed:
Recompiling will take some time!
Check GHOST Node version, the output should be ghost 0.7.197-8a0cbb94b4d
:
Check checksum the output should be ad653233c978bfd00c5e4525b17628632bc4319c5f5f4b4dcc2f050ef3c3d145
:
Create running ghost-node
service that starts on system boot using --unit-file
flag. And we must set up the ghost-node
launch command by setting arguments using --set-arguments
flag:
Only change the defaults if you are advanced otherwise press Enter for the following prompts.
If this is your first node simply press Enter to proceed with the default. If this is your second node you should type a different port here, for example 30334
, and then you should open this port on your firewall and create a dedicated port forwarding rule on your router as specified in the Testing Connectivity Guide:
To choose default options press Enter here:
It is recommended that you give your node a Name you can recognize:
Validator Node vs Full Node
GHOST Chain consists of 3 types of nodes:
- Boot Node – a type of node that other nodes can connect to in order to verify their legitimacy
- Validator Node – a type of node that has $GHST Staking Capability
- Archival Node – a type of node that will store the archive of the GHOST Chain ledger
If you want to be a Full Node type y
:
If you want to be a Validator Node type N
:
You can press Enter here:
Boot Node
For the following prompt:
Paste one of the following Boot Node address:
If you want your node to become a GHOST Chain Boot Node and to have a dedicated Boot Node Address listed in this guide please follow the Create Custom Boot Node Address guide and let us know in GHOST Whales.
Boot Node Address | Port Status |
---|---|
Checking port 30334 for https://bootnode69.chain.ghostchain.io...
|
|
Checking port 30333 for https://bootnode70.chain.ghostchain.io...
|
|
Checking port 30333 for https://ghostvision.mywire.org...
|
|
Checking port 30334 for https://ghostvision.mywire.org...
|
|
Checking port 30335 for https://ghostvision.mywire.org...
|
|
Checking port 30333 for http://84.247.181.131...
|
|
Checking port 30333 for http://47.199.13.160...
|
|
Checking port 30334 for http://85.190.242.68...
|
|
Checking port 30334 for http://47.199.13.160...
|
|
Checking port 30335 for http://47.199.13.160...
|
|
Checking port 30336 for http://47.199.13.160...
|
|
Checking port 30337 for http://47.199.13.160...
|
|
Checking port 30333 for http://Fujisan1.mywire.org...
|
|
Checking port 30334 for http://Fujisan2.mywire.org...
|
|
Checking port 30335 for http://Fujisan3.mywire.org...
|
|
Checking port 30336 for http://Fujisan4.mywire.org...
|
Changing unit-file
name is optional, otherwise press Enter:
IF ERROR and [!] user ghost not found
pops up press y
:
DO NOT enable ghost-node.service
press Enter:
DO NOT start ghost-node.service
press Enter:
Restart ghost-node
:
Enable ghost-node
:
To see the logs produced by your ghost-node
:
To exit journalctl -f -u ghost-node
Press CTRL + C.
Finally, go to GHOST Telemetry so see your node live on the map.
Congratulations! You have an operational GHOST Node.
Existing Full Nodes Migrating to TestNet 3.1
Only follow this section if you currently have a GHOST TestNet 2.0 or GHOST TestNet 3.0 Full Node.
Stop ghost-node
process:
Remove old GHOST TestNet Ledger:
Go to ghost-node
directory:
Pull the most recent GHOST Chain PR from GHOST GIT:
Recompile your GHOST Node:
Check GHOST Node version, the output should be ghost 0.7.197-8a0cbb94b4d
:
Check checksum the output should be ad653233c978bfd00c5e4525b17628632bc4319c5f5f4b4dcc2f050ef3c3d145
:
Restart GHOST Node:
Check GHOST Node log:
Troubleshooting
For future troubleshooting be aware of the following commands:
Update GHOST Node
Go to GHOST directory:
Pull the most recent GHOST Node Repo:
Set arguments. In one of the prompts it is recommended that you give your node a Name you can recognize:
Check GHOST Node log:
To exit journalctl -f -u ghost-node
Press CTRL + C.
Delete GHOST Chain ledger
Check session keys
Systemd-journal Permission
Find your user:
Replace $USER
with your user:
Replace $USER
with your user:
Create new group:
To see the logs produced by your ghost-node
:
Miscellaneous
To soft reload the entire system:
To stop ghost-node
:
To restart ghost-node
:
To see the logs produced by your ghost-node
:
What is GHOST Chain?
GHOST Chain is a decentralized EVM bridge with a privacy layer providing a much needed cross-chain interoperability and anonimity in the web3 space.Become Validator | GHOST Chain | ghostDAO Litepaper