StakeMinAmount: 1 ZNN

An encrypted KeyStore is referred to as KeyVault.

KeyVault Example

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

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

Mnemonic

BIP44 Path

Private Key

Public Key

User Prefix Byte

Core Bytes

Address

Zenon Dart SDK Example

Code

Output

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

Folder Structure

The Zenon Node has the following folder structure:

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

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:

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

Otherwise use:

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

3. Follow the provided instructions

• Interactive Prompt:

• Action:

  • Enter 4 and press Enter to stop the running the znnd service.

Note: Ensure the service has completely stopped before proceeding to the next step. You can enter 2 and press Enter to verify the Status of the znnd service.

Action: Enter 2 and press Enter to view the current status.

Microsoft Azure

This command grants you root privileges for the installation process.

• Add a # at the Beginning:

  This comments out the line, disabling the scheduled restart.

1) Prerequisites

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.

2) Choosing a Hosting Provider

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.

• Support: 24/7 customer support can be invaluable.

• Cost: Balance between features and your budget.

Popular Hosting Providers:

• DigitalOcean

• Amazon Web Services (AWS)

• Hetzner

• Google Cloud Platform (GCP)

• Microsoft Azure

• Vultr

• Linode

Choose a provider that best fits your requirements and budget.

3) Minimum Hardware Requirements

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

4) Choosing the Operating System

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

5) Server Setup and Configuration

Accessing the Server

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.

3. Switch to Root User:

   This command grants you root privileges for the installation process.

Updating the System

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.

Installing Required Packages

Install unzip and other necessary utilities:

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

• wget: Facilitates downloading files from the internet.

6) Installing the Zenon Controller

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: https://github.com/zenon-network/znn_controller_dart/releases

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

   • unzip -o: Extracts the ZIP file, overwriting existing files if necessary.

   • rm: Removes the ZIP file after extraction to save space.

2. Verify Installation:

   Ensure the znn-controller executable is present:

   You should see the znn-controller file listed.

7) Configuring Automatic Restarts with Cron

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.

   2. Navigate to the end of the file.

   3. Add the following line to schedule a restart every hour:

3. Save and Exit:

   1. Press Esc to exit insert mode.

   2. Type :wq and press Enter to save and quit.

8) Deploying the Pillar

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

3. Monitoring Synchronization: The controller will begin syncing to the latest block height of the Zenon network. This process may take some time (even days) depending on network conditions and server performance. To monitor the status of your sync:

   Select option 2) Status And compare it to the latest height in your syrius wallet, or trusted Zenon Network explorers:

9) Update Producer Address

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.

   4. Click on +Update Pillar

   5. For the Pillar producer address field, paste the new Pillar's Producer Address, and press Next and Update until it saves the new address. Steps to get your new Pillar's Address are written below.

2. Start the Zenon Controller:

3. Deployment Options:

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

   • Select option 2) Status

4. Copy Producer Address Use this new Pillar Producer Address to update in the syrius wallet.

10) Post-Deployment Steps

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:

   • Add a # at the Beginning:

     This comments out the line, disabling the scheduled restart.

2. Save and Exit:

   1. Press Esc to exit insert mode.

   2. Type :wq and press Enter to save and quit.

3. Shut down old Pillar on old Hosting Provider: Once the above steps have been completed, you can shut down your server which hosted your old Pillar. It is recommended that you delete the server only after you've successfully collected your Pillar rewards in the syrius wallet (using the new Pillar's Producer Address). You can wait until the next reward distribution for this (the next day, depending at which hour of the day you've migrated).

11) Useful Commands

Watch the Pillar's logs in real-time:

Verify the Sync / Height Status:

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.

1) Prerequisites

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 Alchemy to obtain WebSocket (WSS) endpoints.

• Producer Passphrase: The passphrase for your Producer Key File, retrievable via the znn-controller.

• QSR Tokens: At least 120 QSR tokens fused to the Pillar Producer Address.

2) Opening Required Firewall Ports

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.

3) Obtaining a Binance Smart Chain and Ethereum Node from Alchemy

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 Alchemy and create an account or log in.

2. Create a New App:

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

   2. Select the desired network (e.g., Mainnet, Ropsten).

3. Retrieve the WSS Endpoint:

   1. Once the app is created, go to the app’s dashboard.

   2. Locate the WebSocket endpoint URL.

4. Example Endpoint:

4) Server Setup and Configuration

Accessing the Server

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.

3. Switch to Root User:

   This command grants you root privileges for the installation process.

Updating the System

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.

Installing Required Packages

Install unzip and other necessary utilities:

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

• wget: Facilitates downloading files from the internet.

5) Installing the Orchestrator

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

1. Download the Orchestrator Binary

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

Download Command:

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

2. Extract the Orchestrator Binary

Unzip the downloaded file:

3. Setup the Config.json 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/.

4. Configure the Config.json File

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:

   • Retrieve by running the znn-controller and selecting the 2) Status option.

3. Maintain Unique EvmAddress:

   • Do not change or remove the EvmAddress once created.

4. Add Bootstrap Address:

5. Sample config.json Structure:

5. Copy the Producer File

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.

6) Setting Up Orchestrator as a Service

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

1. Create a systemd Service File

Open a new service file for the Orchestrator:

2. Add Service Configuration

Copy and paste the following content into the service file:

3. Activate and Start the Orchestrator Service

Reload systemd to recognize the new service:

Enable the service to start on boot:

Start the Orchestrator service:

4. Verify the Orchestrator Service Status

Check if the Orchestrator service is running correctly:

Expected Output:

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

7) Fusing QSR Tokens

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

Steps to Fuse QSR Tokens

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.

   • Ensure you have at least 120 QSR fused to meet the network's requirements.

8) Useful Commands