Register and Run a Human Node

Human Network Mainnet Alpha is now Permissionless, please process the following instructions to run a node on Human Network!

As an external operator, you'll be asked to run a multiplier/attester node. To onboard, you'll be asked to perform the 3 following steps:

  1. Registration as EigenLayer or Symbiotic operator through Othentic CLI

  2. Registration on Human Network smart contract

  3. Run the docker image with docker compose

Prerequisites

Hardware requirements

Component
Requirement

CPU

16 vCPU

Memory (RAM)

16GB

Storage

256GB SSD

Networking

50 Mbps

Cloud Provider Instance Types

Provider
Instance Type

AWS

m7i.xlarge

GCP

e2-medium

Azure

Standard_B2s

OVH

…

Operator Key Setup

Human Network is an AVS built using the Othentic Stack. This architecture enhances security by allowing Operators to separate key usage.

There are two key types:

  • The Controller key, which uses ECDSA cryptography

  • The Consensus key, which uses BLS cryptography

To generate these keys, download the othentic-cli tool:

Once you've installed the CLI, refer to this guide for instructions on generating separate Controller and Consensus keys.

Note: Only the Consensus key is required for ongoing node operations. Therefore, it is highly recommended the host machine contains only the Consensus key, while the Controller key is kept in a highly-secure, separate airgapped environment.

After you've saved both keys in separate keystore files, you're ready to proceed to the next section.

Prepare Host Machine

We recommend running the operator node software on a linux-based server with fast and reliable network connectivity. Any offer from a major cloud provider would be sufficient.

Software Environment

The officially supported approach to running the operator node software is through a Docker Compose setup.

Make sure you have correctly set up the following:

  • Docker Engine v24+ with Docker Compose.

  • Functioning wget1 and wcurl.

  • R/W Access to home dir (~/)

  • Access to private RPC nodes for Ethereum mainnet and base

User Permissions

Make sure the docker user has permission to read and write to the node working directory.

Ports

Make sure the ports in use are open to the internet on the host machine, and verify security group settings.

Step 1: Registration with Othentic

  • Copy the following environment variables and save as .env, and set the missing variables.

Note that both chosen TCP and UDP ports must be open along with the ports: 9876 and 8545 as these are required by the attestor node.

Be careful not to add extra space in the .env file.

Please do not modify the seeds after registration.

PRIVATE_KEY_ATTESTER can be the same as PRIVATE_KEY.

Setup OPERATOR_ADDRESS in case you're using different controller and consensus keys.

In case you don't feel comfortable with providing your private key in the .env file, please refer to this section to use keystore instead.

  • Run registration command:

Then follow the instructions to register. See also: Registering as an Operator to Othentic AVS

Use the AVS governance contract address 0x42F15F9E4dF4994317453477e80e24797CC1A929

Please correctly select you Shared Security Provider (EigenLayer or Symbiotic) by using Space bar on your keyboard before pressing Enter.

Step 2: Registration on Human Network smart contract (0x46589681fA8dbe5B7a11B0a74aF2633E170fCfbB)

Each multiplier node will need to also act as an attester node by verifying the tasks performed by the other multipliers. But the attester part will be run in parallel and doesn't require any additional code.

Register - don't re-register if already registered

First register with the Human Network PeerRegistry smart contract.

  • <rpc-url> URL for an private RPC node, used to send the registration transaction to the blockchain. Use an Ethereum Holesky node when registering for Human Network testnet. Use an Ethereum mainnet node when registering for Human Network mainnet. We recommend to use a private RPC as Alchemy or Quicknode for more reliability.

  • <private-key> should be for the account you have registered as an Othentic operator. It's necessary to send the transaction from your operator account because the PeerRegistry contract needs to associate your wallet address with the rest of your node's metadata.

  • <multiaddr> should be the multiaddr address of your Human node. For example, if your node's IP address is 100.27.208.30 and it is exposed on port 8080, then your multiaddr is /ip4/100.27.208.30/udp/8080/quic-v1.

  • <rpcaddr> should be the RPC address of your Human node. For example, if your node's IP address is 100.27.208.30 and it is exposed on port 8080, then your RPC address is http://100.27.208.30:8080.

If the call is successful, you will see a transaction receipt.

When populating your environment variables, make sure your multiaddr and rpcaddr match what you registered.

Step 3: Running a Multiplier/Attester node

Copy the following docker compose file and save as docker-compose.yml

Fill in your announced address for the attestor by entering your public IP of the instance and the Attestor Peer ID (see note below for more details on this as it is different from your PeerRegistry PeerId)

You can figure out the value of Peer_id for the --announced-addresses via two ways: - Run node for the first time with --announced-addresses commented out in docker-compose.yml and in the logs search for the Libp2p node started with peer id: phrase using command: sudo docker logs attestor | grep "Libp2p node started with peer id:" - Or, you can get the PeerId by running the command: docker run -it mishtinetwork/operator:mainnetalphaV3.2.0 othentic-cli node get-id --node-type attester

Run the docker compose with following command:

PreviousMainnets and TestnetsNextUse Keystore for private key encryption

Last updated