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

• SentinelZnnRegisterAmount: 5000 ZNN

• SentinelQsrDepositAmount: 50000 QSR

• SentinelEpochLockTime: 27 epochs

• StakeTimeUnit: 30 epochs

• StakeTimeMin: 30 epochs

• StakeTimeMax: 360 epochs

• FuseMinAmount: 10 QSR

• FuseExpiration: 10 hours

• TokenIssueAmount: 1 ZNN (burned)

• TokenNameLengthMax: 40 characters

• TokenSymbolLengthMax: 10 characters

• SwapAssetDecayEpochsOffset: 90

• SwapAssetDecayTickEpochs: 30

• SwapAssetDecayTickValuePercentage: 10

• Specifications

• Cryptography

• Node Paths

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"

The Zenon Node has the following folder structure:

Legacy

• Specifications

• Cryptography

• Node Paths

Welcome to our official guide for setting up a Zenon Network Pillar. This comprehensive manual will walk you through selecting the right hosting provider, configuring your server, installing necessary dependencies, and deploying the Zenon controller. Whether you're a seasoned developer or new to blockchain infrastructure, this guide will ensure a smooth and secure setup process.

Table of Contents

1. Prerequisites

2. Set Up the Orchestrator on the New VM

3. Transfer the Orchestrator Configuration

4. Set Up and Start the Orchestrator Service

• Old VM Access: Ensure the original VM (old Pillar) is still accessible and running the orchestrator.

• New VM Setup: The new VM should have a working Pillar node synced with the Zenon Network of Momentum (NoM), as per the .

• Backup: Back up the old VM’s orchestrator directory (/root/.orchestrator) and producer keystore before proceeding.

If the orchestrator isn’t already installed on the new VM, follow the initial setup steps from the first.

Copy the entire .orchestrator folder from the old VM to the new VM. This includes the old /producer folder and old config.json:

Follow of the Setup Guide.

Confirm the orchestrator is functioning and recognized by the bridge.

a) Check Logs:

View recent logs for errors:

b) Test Health Check:

Query the orchestrator’s API:

Expected output includes version info, e.g.,

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)

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.

Ed25519 is a deterministic signature scheme using curve25519

Ed25519 which is compatible with BIP44

• key parameter: ed25519 seed

• hardened offset: 0x80000000

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

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)

Table of Contents

1. Prerequisites

2. Stop the znnd Service

3. Download the Latest znn-controller

Before proceeding with the update, ensure you have the following:

• Access Credentials: SSH access to your server with sudo privileges.

• Basic Knowledge: Familiarity with command-line interfaces and server management.

• Backup: It's recommended to back up your current configuration and controller files before performing the update.

1. Access Your Server via SSH:

   Open your terminal and connect to your server using SSH:

   Replace username with your server's username (commonly root) and your_server_ip with your server's IP address.

2. Stop the znnd Service:

1. Identify the Latest Release URL:

   Visit the to find the latest version of the znn-controller. Copy the download URL for the x86/64 Linux release.

2. Download the Latest Controller:

   Replace YOUR_LATEST_URL with the actual URL of the latest znn-controller release.

• Extract the Downloaded ZIP File:

  • -o Flag: Overwrites existing files without prompting.

• Remove the ZIP File:

• Run the Updated znn-controller:

• Deployment Options:

  Upon execution, you will be presented with deployment options:

• Select Deploy Option:

  • Action: Enter 1 and press Enter to deploy the updated controller.

• Continue Using Existing Configuration:

  • Prompt:

  • Action: Enter Y and press Enter

• Check the Status of the Controller:

  Run the znn-controller and select the status option to verify that the update was successful.

  • Interactive Prompt:

Ubuntu 20.04 LTS was used for this tutorial.

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.

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

If you don't have gpg

Table of Contents

1. Prerequisites

2. Choosing a Hosting Provider

3. Minimum Hardware Requirements

Before proceeding, ensure you have the following:

• Basic Knowledge: Familiarity with command-line interfaces and server management.

• Access Credentials: SSH access to your chosen server with sudo privileges.

Selecting a reliable hosting provider is crucial for the stability and performance of your Zenon Pillar. Consider the following factors when choosing a provider:

• Reliability and Uptime: Ensure the provider offers high uptime guarantees (99.9% or higher).

• Performance: Look for providers with robust CPU and RAM options to handle blockchain operations.

• Scalability: Ability to upgrade resources as your node grows.

• Security: Features like DDoS protection, firewalls, and regular backups.

Popular Hosting Providers:

• DigitalOcean

• Amazon Web Services (AWS)

• Hetzner

• Google Cloud Platform (GCP)

Choose a provider that best fits your requirements and budget.

To ensure optimal performance and stability of your Zenon Pillar, your server should meet the following minimum hardware specifications:

For optimal performance and compatibility with the Zenon controller, it is recommended to use a Linux distribution. The x86/64 znn_controller-linux release is compatible with several distros, including:

• Ubuntu 22.04 LTS (Recommended)

• Debian 11

• CentOS 8

• Fedora 36

1. Obtain SSH Credentials: After setting up your server with your chosen provider, retrieve the SSH IP address, username, and password/key.

2. Connect via SSH:

   Replace username with your server's username (commonly root) and your_server_ip with your server's IP address.

Ensure your server's package lists and installed packages are up to date by running the command individually:

• apt update: Updates the package index.

• apt upgrade -y: Upgrades all installed packages to their latest versions.

Install unzip and other necessary utilities:

• unzip: Required for extracting the Zenon controller ZIP file.

• wget: Facilitates downloading files from the internet.

1. Download the Zenon Controller: Execute the following command to download and extract the Zenon controller:

   Visit the official Zenon Network Github repository for the latest znn_controller_dart release:

   • wget -O: Downloads the file and saves it with the specified name.

For the initial sync of your Zenon Pillar, it's recommended to configure automatic restarts. This ensures that the controller restarts hourly, speeding up the sync process.

1. Open Crontab Editor:

2. Add Cron Job:

   1. Press i to enter insert mode.

1. Start the Zenon Controller:

2. Deployment Options:

   Upon running the controller, you will be presented with deployment options. To deploy your pillar:

   • Select option 1) Deploy

Once and ONLY once your new Pillar has synced up to the latest height, should you proceed with this step of the migration. If you update your producer address prior to a full sync, you will miss rewards as your Pillar will not be participating in the network until it's fully caught up. Therefore if your new Pillar reached the latest height:

1. Open Your syrius Desktop Wallet

   1. Click on the in the navigation bar.

   2. Select the address of the Pillar you're migrating.

   3. Click on Pillars in the navigation bar.

After your pillar has successfully synced to the latest height and you've updated your Pillar's Producer Address in your syrius wallet, it's crucial to remove the cron job so that the Pillar doesn't miss momentums unnecessarily:

1. Comment Out the Cron Job:

   Prevent the automatic restart to avoid interrupting the controller's operation.

   • Re-open Crontab Editor:

   • Locate the Cron Job:

Replace the PRIVATE-IP with your Pillar's Private IP address:

You will receive a response:

When the state goes from 1 to 2, then your Pillar is fully synced.

Table of Contents

1. Prerequisites

2. Opening Required Firewall Ports

3. Obtaining an Ethereum Node from Alchemy

Before proceeding, ensure you have the following:

• Basic Knowledge: Familiarity with command-line interfaces and server management.

• Access Credentials: SSH access to your chosen server with sudo privileges.

• BNB and Ethereum Nodes: Access to a BNB and Ethereum node provider like to obtain WebSocket (WSS) endpoints.

• Producer Passphrase:

To facilitate communication and health checks, ensure the following ports are open on your server’s firewall:

1. Port 55055 (TCP): Open for gossip communication between nodes.

2. Port 55000 (TCP): Open for API health checks.

Steps to Open Ports:

Assuming you’re using ufw (Uncomplicated Firewall) on Ubuntu:

Note: If you’re using a different firewall management tool, adjust the commands accordingly.

To interact with the Binance Smart Chain and Ethereum network, you need access to a Binance Smart Chain and Ethereum node. Alchemy provides reliable node services.

Steps to Obtain the WSS Endpoint

1. Sign Up/Login to Alchemy:

   1. Visit and create an account or log in.

2. Create a New App:

   1. Navigate to the dashboard and create a new app.

1. Obtain SSH Credentials: After setting up your server with your chosen provider, retrieve the SSH IP address, username, and password/key.

2. Connect via SSH:

   Replace username with your server's username (commonly root) and your_server_ip with your server's IP address.

Ensure your server's package lists and installed packages are up to date by running the command individually:

• apt update: Updates the package index.

• apt upgrade -y: Upgrades all installed packages to their latest versions.

Install unzip and other necessary utilities:

• unzip: Required for extracting the Zenon controller ZIP file.

• wget: Facilitates downloading files from the internet.

This section covers downloading the Orchestrator binary, setting up the configuration file, and preparing the orchestrator for deployment.

First, download the latest Orchestrator binary. Ensure you're using the most recent release by checking the .

Download Command:

Note: Replace the URL with the latest release if a newer version is available.

Unzip the downloaded file:

Move the Binary and Create the Configuration Directory

1. Copy the Binary to /usr/local/bin/:

2. Run the Orchestrator Binary to Initialize:

   • Expected Outcome: The process will fail initially but will create a working directory at /root/.orchestrator/.

Edit the config.json file to suit your environment:

Configuration Steps:

1. Update WebSocket URLs:

   • BNB: Replace with your Alchemy BNB WSS endpoint.

   • Ethereum: Replace with your Alchemy Ethereum WSS endpoint.

2. Provide Producer Key File Passphrase:

Assuming you are running the Orchestrator on the pillar, copy the producer file to the Orchestrator's data path:

Note: Ensure the path to the producer file is correct. Adjust the command if your producer file is located elsewhere.

To ensure that the Orchestrator runs continuously and starts on boot, set it up as a systemd service.

Open a new service file for the Orchestrator:

Copy and paste the following content into the service file:

Reload systemd to recognize the new service:

Enable the service to start on boot:

Start the Orchestrator service:

Check if the Orchestrator service is running correctly:

Expected Output:

Note: The Active: active (running) status indicates that the service is running correctly.

To fully deploy your Orchestrator with the Zenon Network, ensure that you have fused at least 120 QSR tokens to the Pillar Producer Address.

1. Access Your Pillar Producer Address:

   • Use your Syrius wallet or another compatible wallet to access your producer address.

2. Fuse QSR Tokens:

   • Follow the wallet's instructions to fuse QSR tokens.