Windows & macOS Setup Guides
Linux Exclusivity Notice: The native ZugChain validator suite is designed exclusively for Linux environments. However, you can perfectly run the network on Windows or macOS by using local Ubuntu virtualization. Follow your operating system's complete A-to-Z guide below.
01 / Prepare Windows (Install WSL2)
To run the node, we first need to activate Windows' built-in Linux subsystem. Open PowerShell as Administrator and run:
wsl --installAfter installation, restart your PC. Open the new "Ubuntu" application from your Windows Start Menu. You will do all following steps inside this Ubuntu terminal.
02 / Install Geth (Execution Client)
sudo add-apt-repository -y ppa:ethereum/ethereumsudo apt-get updatesudo apt-get install ethereum -y03 / Network & Firewall Configuration
Open the required ports on your Ubuntu firewall:
sudo ufw allow 30303
sudo ufw allow 13000/tcp
sudo ufw allow 12000/udp
sudo ufw allow 3500/tcp
sudo ufw enable(Hint: You may also need to allow these ports in your Windows Defender Firewall).
04 / Clone Repository & Initialize Node
Download the ZugChain suite and run the automated installer:
05 / Key Generation & Secure Import
To participate in consensus and earn rewards, the blockchain needs to recognize you via cryptographic keys. You must generate these keys offline, deposit exactly 32,000 ZUG using them, and then import them into your server safely.
Generate Your Keys
Go to the official CLI tool linked above. Follow the instructions to generate a new mnemonic (passphrase) and your validator keys. It will produce a JSON file named something like keystore-m_12381_3600_0_0_0-123456.json. You must remember the password you used to encrypt it.
Upload Keys to your Server
You need to transfer the generated JSON file over to your Linux/Ubuntu environment. The easiest way for beginners is to copy the text inside the file and paste it into a new file on your server.
Import to the Validator Wallet (CRITICAL)
Now, securely import your key into the Validator Client's local database:
CRITICAL - Auto-Restart Requirement: During the import step above, the terminal will ask you to create a NEW Wallet Password. You MUST immediately save this password into a specific file using the command below, or your validator will fail to restart:
06 / Start the Node & Monitor
Ignite the background services and check your logs:
01 / Prepare macOS (Create Ubuntu VM)
Because ZugChain uses native Linux tools, we will create an isolated Ubuntu environment right on your Mac using Multipass (works perfectly on Apple Silicon M1/M2/M3 and Intel). Open your Mac Terminal and run:
You are now inside Ubuntu! Run all following steps in this terminal.
02 / Install Geth (Execution Client)
Install the execution layer software inside your VM:
03 / Network & Firewall Configuration
Open the required network ports:
04 / Clone Repository & Initialize Node
Download the ZugChain suite and run the automated installer:
05 / Key Generation & Secure Import
To participate in consensus and earn rewards, the blockchain needs to recognize you via cryptographic keys. You must generate these keys offline, deposit exactly 32,000 ZUG using them, and then import them into your server safely.
Generate Your Keys
Go to the official CLI tool linked above. Follow the instructions to generate a new mnemonic (passphrase) and your validator keys. It will produce a JSON file named something like keystore-m_12381_3600_0_0_0-123456.json. You must remember the password you used to encrypt it.
Upload Keys to your Server
You need to transfer the generated JSON file over to your Linux/Ubuntu environment. The easiest way for beginners is to copy the text inside the file and paste it into a new file on your server.
Import to the Validator Wallet (CRITICAL)
Now, securely import your key into the Validator Client's local database:
CRITICAL - Auto-Restart Requirement: During the import step above, the terminal will ask you to create a NEW Wallet Password. You MUST immediately save this password into a specific file using the command below, or your validator will fail to restart:
06 / Start the Node & Monitor
Ignite the background services and check your logs:
Last updated
Was this helpful?