Testnet
Search…
Prepare your system
This page will guide you through setting up your system to be able to install and run your humanode.

Security consideration

At the moment the Humanode testnet does not use secure enclaves nor our cryptographic schemes to process biometric data as it requires further development.
The Humanode core team is using best practices to manage sensitive data. Secure biometric data processing is done by integrating FaceTec and end-to-end encryption. All processed data is stored in an encrypted form in the cloud. The keys are under control by Humanode in the following way:
    FaceTec SDK encrypts processed biometric data at the client-side with 2048-bit RSA keys.
    The server uses these keys to process the aforementioned data.
    The keys have been generated in the VM locally to prevent leakage.
    Private keys never leave the VM, and access to the VM is restricted.

Internet connection

To become a Humanode validator and take part in block production in the Humanode testnet you are required to have a properly configured network connection.
We recommend running your node in the cloud, such that you won't have any trouble with NAT. You can use Amazon, DigitalOcean, Scaleway, or any other cloud provider that you like. If you decide to run the node at home, please make sure you forward TCP port 30333 to your system.
You will need to connect to your node's RPC endpoint from a handheld device (i.e. phone), and we'll guide you through how to do this with ngrok in the later sections. If you don't like ngrok, you can configure it manually if you know what you're doing. Just make sure you have a proper TLS certificate and that the connection is routed to TCP port 9933.
To install ngrok, please follow these instructions. You only need unzip it and configure your auth token, setting up the tunnel is explained later.
Note that in case you if you're using WSL 2 on Windows, and have an AMD64 processor, you have to choose More Options -> Linux -> Linux.

Hardware requirements

    2 CPU Cores
    4 GB RAM
    40 GB disk space
    100 Mbps internet connection
    Public IP address or ports forwarded in NAT (and ngrok-like tunnel)

Software requirements

Currently, we officially support only Linux-based operating systems.
However, we provide binaries for macOS and a workaround for Windows users too.

Linux-based

To run the Humanode peer on a Linux-based system you don't need to take any extra steps. Just make sure that your system time is configured properly.

macOS

As of now, Humanode binaries are not signed with Apple-approved certificates, so to run the peer on macOS you have to disable system integrity protection and gatekeeper.
Please follow this guide from Apple to disable the system integrity protection and use the command sudo spctl --master-disable to turn off the gatekeeper.
Be careful, and turn them back on after you're done with the testnet, unless you know what you're doing.

Windows

If you're on Windows, you'll need to use Windows Subsystem for Linux v2 (WSL 2) to run the Humanode peer. Native Windows binaries are currently not provided.
To install WSL on Windows, follow the official guide from Microsoft.
Then install the Ubuntu 20.04 LTS from Microsoft Store.

Validating WSL 2 installation

To make sure you've set up WSL 2 correctly, use the following command in PowerShell:
1
wsl --list --verbose
Copied!
The output should look like this:
1
NAME STATE VERSION
2
* Ubuntu Running 2
Copied!
The VERSION column should be 2, if it's 1 you might have to switch your Ubuntu WSL instance to version 2.
To do this, you'll need to run a command like this: wsl --set-version "<distro_name>" 2:
Should look something like this:
1
wsl --set-version "Ubuntu" 2
Copied!
Then use the wsl --list --verbose command again to check that everything worked, version should now be 2.

System time

One of the most common but difficult-to-find issues is that the time in your OS is not accurate. For a distributed system like blockchain, having a correctly set time is important, as the synchronization algorithms rely on it. Even a small drift from the network time will cause your node to produce invalid blocks, preventing you from properly participating in the consensus.
Therefore, please, configure your system to use NTP for automatic time syncronization. As long as you're using an OS with correctly implemented system clocks, the timezone you are using is irrelevant, and won't affect the correctness of the consensus. However, if you have issues (i.e. you're on Windows), you should set your system time zone to UTC. You can use online clock to tell if your system time is drifting from the commonly accepted time.

Handheld devices

    iOS or Android
    Camera
    Accelerometer
    Modern Web browser (Chrome / Firefox / Safari)
You will need a handheld device (like a phone or tablet) to capture the biometric data. No special configuration is required.
Last modified 5d ago