Pillar

For the Pillar deployment process one will need access to both a local and a remote machine. The local machine is represented by the controller wallet, where you create the Pillar Slot and register the Pillar on the network. The remote machine is usually represented by a VPS with some minimum recommended specs and a public IP that is actively participating in the consensus protocol.

You will need to generate 3 distinct addresses for the Pillar creation tutorial:

• pillarAddress = address from which the Pillar is registered that contains the necessary funds (15,000 ZNN that will be locked and can be recovered after you disassemble the Pillar and 150,000 QSR + additional 10,000 QSR for every new Pillar Slot in the network that will be burned and cannot be recovered)

• pillarRewardsAddress = address used to collect the Pillar rewards

• producerAddress = address used to produce the momentums that is stored on the remote machine; must be generated from a different seed than your local wallet keyStore for security purposes

Sentinel

The Sentinel deployment process is similar to the Pillar deployment process.

Controller Wallet

The latest version of the s y r i u s wallet is recommended to be used as controller wallet. Advanced users can use the znn-cli instead.

Remote Machine

These commands should be issued from your remote machine (e.g. VPS). If you won't use a VPS provider, you will need an additional setup including enabling port forwarding. This tutorial is intended for a VPS with some minimum recommended specs and a public IP.

Minimum Requirements

Hardware:

• CPU >= 4 cores

• RAM >= 4 GB

• Storage >= 40 GB free space

• >100Mbps network dedicated bandwidth

Software:

• Linux distros e.g. Ubuntu 20.04 LTS/Debian 11

• Recommended NTP configuration*

• Recommended Watchdog service*

(*) Included if the setup is performed using the znn-controller

Steps

1. Download the znn-controller

See zenon-network / go-zenon for the latest releases.

2. Run znn-controller as root

sudo ./znn-controller

3. Follow the provided instructions

Ubuntu 20.04 LTS was used for this tutorial.

1. Download the Binaries

Download znnd, znn-cli and znn-controller from their respective GitHub repos. Please note that znn-controller is only available for Linux at the moment.

2. Verification (depreciated)

Import the Zenon Testnet PGP key from hkps.pool.sks-keyservers.net

gpg --keyserver hkps.pool.sks-keyservers.net --recv E2D8289C0A9D2C28A3320B62D2AAFD5D9088F1A2

If you don't have gpg installed, please use sudo apt install gnupg

gpg: key E2D8289C0A9D2C28A3320B62D2AAFD5D9088F1A2: public key "Zenon Testnet <portal@zenon.network>"

Verify the signature. The same command can be used on macOS:

gpg --verify `path_to_sig`.sig `path_to_release_bundle`

gpg: Good signature from "Zenon Testnet <portal@zenon.network>"

3. Start the Node Daemon

If you are on a Linux machine, use the znn-controller option 1) Deploy:

./znn-controller

Otherwise use:

./znnd

4. Verify Node RPC Communication

Inspect the config.json file using your favorite text editor.

Navigate to ~/.znn/config.json.

Check if the http, websocket entries are enabled (true). By default, all Endpoints are public.

The default HTTPPort is 35997 and WSPort is 35998.

{
  "RPC": {
    "EnableHTTP": true,
    "EnableWS": true,
    "Endpoints": null
  }
}

You can also disable the RPC communication via znn-cli:

./znn-cli disableRPC

RPC successfully disabled
Start znnd to use the new configuration

5. Generate a ZNN Alphanet Address (optional)

./znn-cli wallet.createNew yourComplexPassphrase

Successfully created keystore: z1qz8tylu88et6ffy227pw8gak5qvn5awg35l96x

6. Check for Pending Funds (optional)

./znn-cli unreceived --keyStore z1qz8tylu88et6ffy227pw8gak5qvn5awg35l96x --passphrase yourComplexPassphrase

If you have pending funds you should see messages like these:

Unreceived 15000.00000000 ZNN from z1qqjr86g6220kmhn2jrelwhtk7u0mp4r5amjwf2.
Use hash b3e51142119174f8af3ea793a7353ec8b5b4e2208f9ebe50549ead5440fd6b49 to receive.

Unreceived 15000.00000000 QSR from z1qqjr86g6220kmhn2jrelwhtk7u0mp4r5amjwf2.
Use hash c68c674c81d4d9abc2b7a20c999352c21a8128033f9b34105b3616119f116e3c to receive.

7. Receive the Pending Funds (optional)

In order to receive the ZNN you need to issue the command receive with the corresponding hash:

./znn-cli receive b3e51142119174f8af3ea793a7353ec8b5b4e2208f9ebe50549ead5440fd6b49 --keyStore z1qz8tylu88et6ffy227pw8gak5qvn5awg35l96x --passphrase yourComplexPassphrase

If you don't have Plasma, you'll need to generate it via PoW, please wait.

Creating receive transaction ...
Generating Plasma, please wait ...
Done

Similarly, you'll receive the QSR by issuing the command receive with the corresponding hash:

./znn-cli receive c68c...6e3c --keyStore z1qz8tylu88et6ffy227pw8gak5qvn5awg35l96x --passphrase yourComplexPassphrase

Creating receive transaction ...
Generating Plasma, please wait ...
Done

8. Check Your Balance (optional)

./znn-cli balance --keyStore z1qz8tylu88et6ffy227pw8gak5qvn5awg35l96x --passphrase yourComplexPassphrase

Balance for account-chain z1qz8tylu88et6ffy227pw8gak5qvn5awg35l96x having height 2
150000.00000000 QSR
15000.00000000 ZNN

9. Deploy a Pillar, Sentinel or Full Node

Follow these Node Deployment instructions to deploy a Pillar or Sentinel.

10. Stop the Node Daemon

You can use the stop command from znn-cli if znnd is located at the same working directory:

./znn-cli stop znnd

If you deployed via znn-controller please use option 4 (Stop service)

Otherwise use:

pkill -9 znnd