The Zenon Node znnd has the following default data paths:

• Linux: ~/.znn

• MacOS: ~/Library/znn Please note that the path can be different due to the hardened runtime policy

• Windows: C:\Users\yourusername\AppData\Roaming\znn

You can change the default DataPath using znnd --data "value"

Folder Structure

The Zenon Node has the following folder structure:

.
├── config.json               - config file used by znnd 
├── consensus                 - consensus DB used by znnd
├── genesis.json              - genesis config file. Used to create the genesis Momentum
├── log                       - logs generated by znnd
│   ├── error                 - only error logs generated by znnd
│   │   └── zenon.error.log   - latest logs - maxes out at 100MB
│   └── zenon.log             - latest logs - maxes out at 100MB
├── network                   - network DB used by znnd
├── network-private-key       - network identity
├── nom                       - nom DB used by znnd
├── syrius                    - syrius files
└── wallet                    - folder cointaining all keyFiles
    ├── user-1                - keyFile with custom name
    └── z1qpnq2hl2...         - keyFile with no custom name

Phase 1 Specs

• EpochDurationInSeconds: 24 60 60 (1 day)

• MomentumTime: 10 seconds

Pillar Node Parameters

• PillarStakeAmount: 15000 ZNN

• PillarQsrStakeBaseAmount: 150000 QSR

• PillarQsrStakeIncreaseAmount: 10000 QSR

• PillarEpochLockTime: 83 epochs

• PillarEpochRevokeTime: 7 epochs

• PillarNameLengthMax: 40 characters

Sentinel Node Parameters

• SentinelZnnRegisterAmount: 5000 ZNN

• SentinelQsrDepositAmount: 50000 QSR

• SentinelEpochLockTime: 27 epochs

• SentinelEpochRevokeTime: 3 epochs

Staking Parameters

• StakeTimeUnit: 30 epochs

• StakeTimeMin: 30 epochs

• StakeTimeMax: 360 epochs

• StakeMinAmount: 1 ZNN

Plasma Parameters

• FuseMinAmount: 10 QSR

• FuseExpiration: 10 hours

ZTS Token Parameters

• TokenIssueAmount: 1 ZNN (burned)

• TokenNameLengthMax: 40 characters

• TokenSymbolLengthMax: 10 characters

• TokenDomainLengthMax: 128 characters

• TokenMaxSupplyBig: 2^255 - 1

• TokenMaxDecimals: 18

Swap Parameters

• SwapAssetDecayEpochsOffset: 90

• SwapAssetDecayTickEpochs: 30

• SwapAssetDecayTickValuePercentage: 10

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

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

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

3. Start the Node Daemon

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

Otherwise use:

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.

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

5. Generate a ZNN Alphanet Address (optional)

6. Check for Pending Funds (optional)

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

7. Receive the Pending Funds (optional)

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

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

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

8. Check Your Balance (optional)

9. Deploy a Pillar, Sentinel or Full Node

10. Stop the Node Daemon

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

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

Otherwise use:

Phase 0 (Alphanet)

Wallet

The wallet data is stored inside a KeyStore

AES-256-GCM for symmetric encryption

Argon2.IDkey as Key Derivation Function

• time: 1

• memory: 64 * 1024

• threads: 4

• key_length: 32

An encrypted KeyStore is referred to as KeyVault.

KeyVault Example

{
  "baseAddress":"z1qqjnwjjpnue8xmmpanz6csze6tcmtzzdtfsww7",
  "crypto":{
    "argon2Params": {
      "salt":"0x1563f86f7afa59dd0be150ffeac10896"
    },
    "cipherData":"0xe81dbb96f5b9839f3741ceff8362e1ebf09e05a8311354658ddf979577ffd0dd34df55757d1fd37e677e3ae7d055b2ed",
    "cipherName":"aes-256-gcm",
    "kdf":"argon2.IDKey",
    "nonce":"0xb7cc39120d5b87a3b7af58b7"
  },
  "timestamp":1633548746,
  "version":1
}

Digital Signing Algorithm

Ed25519 is a deterministic signature scheme using curve25519

Key Derivation

Ed25519 which is compatible with BIP44

• key parameter: ed25519 seed

• hardened offset: 0x80000000

BIP44 Format

m / purpose' / coin_type' / account' / change / address_index

Alphanet (Network of Momentum Phase 0) uses coin_type value 73404

Alphanet Address Format

bech32

• human readable part: z

data

• user account prefix byte: 0

• embedded contract prefix byte: 1

• core: first 19 bytes of sha3(pubKey)

address: bech32(hrp, data)

Example

Entropy

bc827d0a00a72354dce4c44a59485288500b49382f9ba88a016351787b7b15ca

Mnemonic

route become dream access impulse price inform obtain engage ski believe awful absent pig thing vibrant possible exotic flee pepper marble rural fire fancy

BIP44 Path

m/44'/73404'/0'

Private Key

d6b01f96b566d7df9b5b53b1971e4baeb74cc64167a9843f82d04b2194ca4863

Public Key

3e13d7238d0e768a567dce84b54915f2323f2dcd0ef9a716d9c61abed631ba10

User Prefix Byte

00

Core Bytes

25374a419f32736f61ecc5ac4059d2f1b5884d

Address

z1qqjnwjjpnue8xmmpanz6csze6tcmtzzdtfsww7

Zenon Dart SDK Example

Code

import 'package:hex/hex.dart';
import 'package:znn_sdk_dart/znn_sdk_dart.dart';

Future<void> main() async {
  final mnemonic =
      'route become dream access impulse price inform obtain engage ski believe awful absent pig thing vibrant possible exotic flee pepper marble rural fire fancy';

  var keyStore = KeyStore.fromMnemonic(mnemonic);
  var keyPair = keyStore.getKeyPair(0);
  var privateKey = keyPair.getPrivateKey();
  var publicKey = await keyPair.getPublicKey();
  var address = await keyPair.address;

  print('Entropy: \n${keyStore.entropy}\n');
  print('Mnemonic: \n${keyStore.mnemonic}\n');
  print('BIP44 path: \n${Derivation.getDerivationAccount(0)}\n');
  print('Private key: \n${HEX.encode(privateKey!)}\n');
  print('Public key: \n${HEX.encode(publicKey!)}\n');
  print('User & Core bytes: \n${HEX.encode(address!.core!)}\n');
  print('Address: \n$address');
}

Output

Entropy:
bc827d0a00a72354dce4c44a59485288500b49382f9ba88a016351787b7b15ca

Mnemonic:
route become dream access impulse price inform obtain engage ski believe awful absent pig thing vibrant possible exotic flee pepper marble rural fire fancy

BIP44 path:
m/44'/73404'/0'

Private key:
d6b01f96b566d7df9b5b53b1971e4baeb74cc64167a9843f82d04b2194ca4863

Public key:
3e13d7238d0e768a567dce84b54915f2323f2dcd0ef9a716d9c61abed631ba10

User & Core bytes:
0025374a419f32736f61ecc5ac4059d2f1b5884d

Address:
z1qqjnwjjpnue8xmmpanz6csze6tcmtzzdtfsww7

• Specifications

• Cryptography

• Node Paths

• Tutorials

• Linux

  • Node Deployment