Nillion Verifier

🛠️ Hardware Requirements

The system requirements for Nillion Verifier are quite low, here is an example of the system characteristics on which the launch of the node was tested.

Node Type	CPU	RAM	Storage
Full (Recommended)	4 vCPU	6 GB	100GB SSD

Additional requirements

• Go version - 1.21 or newer

Version tag	Folder Name	Docker name
v1.0.1	nillion	nillion

⏱️ Installation time: ~10-30 minutes

Note. The attacker will store the credentials in a file called credentials.json in the created folder. If you lose this file, you will lose access to the accuser's keys/address.

cat nillion/accuser/credentials.json

📝 Manual installation

📌Step 1: Adding the Nillion Testnet to Keplr and inviting test tokens.

1. Create a wallet in Keplr, or use an existing one.

2. Add Nillion Testnet to your wallet - https://chains.keplr.app/

1. Copy your Nillion address.

2. Request test tokens to your address - nillion faucet

After that, proceed to install Nillion Verifier.

📌Step 2: Installation packeges and dependencies

sudo apt update -y && sudo apt upgrade -y
for pkg in docker.io docker-doc docker-compose podman-docker containerd runc; do sudo apt-get remove $pkg; done

sudo apt-get update
sudo apt-get install ca-certificates curl gnupg
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg

echo \
  "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \
  "$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \
  sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

sudo apt update -y && sudo apt upgrade -y

sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

# Docker version check
docker --version

📌Step 3: Install Verifier node

1- Pull docker images

docker pull nillion/verifier:v1.0.1

2- Create folder

mkdir -p nillion/verifier

3- Initialize verifier

docker run -v ./nillion/verifier:/var/tmp nillion/verifier:v1.0.1 initialise

This outputs registration details.

• accound_id: Nillion address of the accuser

• public_key: Public Key of the accuser

Save this data, we will use it later.

📌Step 4: Verify your Nillion Verifier

Go back to verifier.nillion.com, select Verified — Set up for Linux and go to step 5. Initialize the accuser.

1. Select Verifier

1. Select Set up for Linux

1. Select "5.Initialising the verifier.

   

1. If everything is fine, you will see the following inscription.

If you have an error, you may have to wait 10-30 minutes, then try again.

1. Request test tokens from the faucet, to your address "Verifier account id"

After you have requested tokens to your Keplr wallet address, verified the node in step 5, wait for some time 30-60 minutes, and proceed to the next step.

📌Step 5: Running the verifier

Now run your verifier:

docker run -v ./nillion/verifier:/var/tmp nillion/verifier:v1.0.1 verify --rpc-endpoint "https://testnet-nillion-rpc.lavenderfive.com"

Your verifier is now running. It pause for a cool down period before starting to challenge secrets.

📌Step 6: Backup your verifier's credentials.

Note. The attacker will store the credentials in a file called credentials.json in the created folder. If you lose this file, you will lose access to the accuser's keys/address.

cat nillion/verifier/credentials.json

📌Step 7: We check the operation of the node in the dashboard.

Let's go back to the dashboard where you will see something like this in front of you.

You also have the option to stake ETH Mainnet to increase your rewards.

You can check the operation of the node and find useful commands in the Useful command section.