Introduction
Welcome to the GHOST TestNet 3.0 Launch Guide. In TestNet 2.0 we have 140 Nodes and ability to send $CSPR. With TestNet 3.0 there is a ton of stuff coming including further GHOST Eye updates, staking, slashing, etc. All existing TestNet 2.0 Full Nodes MUST update to TestNet 3.0 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.0
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 the hash of the build:
You should see:
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
Currently you have to qualify to become a validator node through GHOST Whales. If you were NOT included in the ghosties file then you cannot be a validator node and you can only be a full node so for disable validator mode? [y/N]
type y
. If you were included in the ghosties file the you can press Enter:
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 start and enable 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.
Migrating from TestNet 2.0 to 3.0
Only follow this section if you currently have a GHOST TestNet 2.0 Full Node
Stop ghost-node
process:
Remove GHOST TestNet 2.0 Ledger:
Go to ghost-node
directory:
Pull the most recent GHOST Chain PR from GHOST GIT:
Recompile your GHOST Node:
Check checksum the output should be 5aeb6fd5b9b14bdbc1a61600655b5217ded7c1b7cb05bd32929354e88935ae97
:
Check ghost-node
version, the output should be ghost 0.7.196-22984545194
:
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
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?
GHOST Ecosystem is at the forefront of decentralized cross-chain interoperability, providing the ability to transfer tokens, NFTs, and other digital assets across multiple blockchains.ghostAirdrop | ghostAirdrop Bot | Medium | Telegram | Twitter | Website