To build the trustnote's testnet it is required to follow the instruction below. This instruction will result in successful build only on Linux systems. The most important reason is, Linux is a better platform for developers. Even more, the complexity of windows environment which requires plenty of additional packages are avoided by using Linux system. This manual describes the installation of testnet from installing few additional packages and required tools on the system to all the required setting needed to be modified. Finally, it is explained that how to make the testnet works properly.

The following procedure has been tested on ubuntu version 16.04 successfully.

First step is to install "compiler" and "git" as below:

sudo apt-get install build-essential git

Next is to install "nvm":

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.1/install.sh | bash

Finally, to reconnect your server and make sure that "nvm" working, also checking the "nvm" version:

nvm -v

Further more, to install "lts node.js" in "nvm":

nvm install 8.9.4

And for checking the version of "node.js" and "npm":

node -v
npm -v

It's also required to install "node.js process manager":

npm install pm2 -g

And to install "node.js native code compiler":

npm install node-gyp -g

In order to download the trsutnote source code, you are required to generate ssh key before continuing the following steps.

git clone https://github.com/trustnote/testnet-builder.git

Even more, we should download "hub", "witness" and "headless" from "gitee" in "testnet-builder/". After the download completion it is required to run 'npm install' in each sub-folder.

cd testnet-builder
git clone https://github.com/trustnote/trustnote-hub.git
git clone https://github.com/trustnote/trustnote-witness.git
git clone https://github.com/trustnote/trustnote-headless.git
git clone https://github.com/trustnote/trustnote-explorer.git

If "npm install" throws any error or exception, it is required to run "npm install" for more times until it works properly.

├── config-files
│   ├── constants.js
│   ├── hub-conf.js
│   ├── witness-conf.js
│   ├── witness-headless-start.js
│   └── witness-start.js
├── data -- store key and address files
├── deploy.sh -- used to generate 12 witnesses automatically
├── genesis-scripts -- store scripts whick are related to generate the genesis unit
│   ├── conf.js
│   ├── create_allConfig.js -- used to generate 12 witnesses's keys and addresses , and should be runned before create_genesis.js
│   ├── create_genesis.js -- used to generate the genesis unit
│   └── package.json
├── Readme.md -- this file
├── remove-all-data.sh delete the database of hub, witness and headless in “~/.config/”
├── start.sh -- start up hub and 12 witnesses by using pm2
├── trustnote-explorer
├── trustnote-headless
├── trustnote-hub
└── trustnote-witness

It is required to copy all files in "testnet-builder" folder to "trustnote-headless/play:

cp -r ~/testnet-builder/genesis-scripts/* ~/testnet-builder/trustnote-headless/play/

And then:

cd ~/testnet-builder/trustnote-headless/play
node create_allConfig.js

Eventually all data generated will be available at "~/testnet-builder/data/"

├── allAddress.json
write something ├── config.json -- seed, keys and address of witness1,witness2,...,witness12,headless13,headless14 and headless15
├── headlessXX -- primary data of headlessXX
│   ├── conf.json
│   └── keys.json
├── witnessXX -- primary data of witnessXX
│   ├── conf.json
│   └── keys.json
└── witnessAddress.json

In the following steps headless15, assigned in trustnote-headless/play/package.json, will be used to generate the genesis unit.

To delete headless15's database:

rm -rf ~/.config/headless15/trustnote*

Next for renewing headless15's conf.json and keys.json:

cp -r ~/testnet-builder/data/headless15/ ~/.config/

Also to get the addresses of "witnesses" and "headlesses":

cat ~/testnet-builder/data/config.json
{
"passphrase": "",
"mnemonic_phrase": "faith oak symbol link window deliver gym shift know lab forest cupboard",
"temp_priv_key": "ZXDxyZAPltxWEoloDUnHgh8bpzsO5B+3N3uvTh3FfO8=",
"prev_temp_priv_key": "EyM9Cei0+ACAQvXmXOqvzsdgp5JTPQLPBFkcTzK0yYs=",
"address": "OZAMEJPXNVBSRDPYO5WQWDOWBUTNUIF7",
"wallet": "iOF60fTjMyjNEMHLjAYR3ptTBv12wKHpS9LyQyE5FaU=",
"is_change": 0,
"address_index": 0,
"definition": [
"sig",
{
"pubkey": "At+qvLBte+RkXGZCQ1+7uU5pHm03Y3S9Ciapj/KEq2yj"
}
]
},

Now, it is required to run "create_genesis.js" for first time to get hash value of the genesis unit.

node create_genesis.js

So, you will get the hash of the genesis unit if everything is OK.

---------->>->> Genesis d, hash=uYjgSazo4Q+OtA7gZrHGuMWoFvUQFitzuu6juWGA/cI=

To update the exports.GENESIS_UNIT in "config-files/constants.js" which will be used by hub and witnesses.

vi ~/testnet-build/config-files/constants.js

Also, delete "database of headless15" before running "create_genesis.js" for second time.

rm -rf ~/.config/headless15/trustnote*

To startup hub and witness first it is required to update exports.initial_witnesses in "hub-conf.js" and "explorer-conf.js" by using the data in "testnet-builder/data/witnessAddress.json".

cat ~/testnet-builder/data/witnessAddress.json
vi ~/testnet-builder/config-files/hub-conf.js
vi ~/testnet-builder/config-files/explorer-conf.js

Second running the "deploy" script:

cd ~/testnet-builder
./deploy.sh

Now, it's time to startup "hub" and "witnesses":

./start.sh

Then, for viewing hub's log:

pm2 logs hub

Finally, for checking incoming connections:

Tue Feb 27 2018 13:54:51 GMT+0800 (CST): 12 incoming connections, 0 outgoing connections, 0 outgoing connections being opened

This last step is running "create_genesis.js" one more time. Last time, hub considered the genesis unit as invalid. Therefore, after updating the hash value of the genesis unit in hub and witness, you are required to run create_genesis.js again. Please, note that before running create_genesis.js, you must delete headless15's database first.

rm -rf ~/.config/headless15/trustnote* cd ~/testnet-builder/trustnote-headless/play
node create_genesis.js

Finally, we will observe that the testnet is built and running successfully, and you can visit the DAG ledger explorer by ip:port.

• ./config-files/hub-conf.js exports.port exports.initial_witnesses
• ./config-files/witness-conf.js exports.hub exports.deviceName exports.payout_address
• ./config-files/constants.js exports.GENESIS_UNIT
• ./config-files/witness-headless-start.js set default passphrase
• ./config-files/witness-start.js delete sendMail function in noticeAdmin()
• ./config-files/witness-conf.js exports.webPort exports.initial_witnesses exports.initial_peers
• When witness and headless startup，they will read conf.json and keys.json from ~/.config/$devicename/. If there is no keys.json in the so called directory, they will generate new key and write it in the keys.json.