Skip to main content
This program has not commenced yet. The Fortytwo Relay Setup repository is remaining private and you will not be able to perform an installation until the first wave of invitations reaches first participants.
Get Relay Access
Please ensure you have received an acceptance email containing your whitelisted public wallet address before attempting to launch the Relay Node. A unique whitelisted wallet address is required for each device on which the Relay Node is installed.

​
Requirements & Recommendations

Before installing a Fortytwo Relay Node, verify that the ‘Relay Node Requirements’ are met.
  • It is recommended to have previous experience of operating relay or being Validator/Operator on a blockchain with knowledge of Docker and Linux.
  • It is best to run Fortytwo Relay on a dedicated server. Both Relay Node and Inference Node can run on the same server if set up correctly (read more here).
  • Staying online 24/7 will greatly affect the node’s quality and rewards.

​
1. Prerequisites

Access to Fortytwo Relay Setup Repository
Installed Docker
Private key from an EVM-Compatible Web3 account

​
2. Setting Up the Fortytwo Relay Node

1

Review the requirements

Being a Relay Noderunner has specific requirements: ‘Relay Node Requirements’.Make sure that your system/virtual machine meets them before proceeding to launch the node.
2

Get the repository

Clone or download and extract the Relay Node repository manually: Fortytwo Relay Setup . If you need more specific instructions, unwrap the following section:
  • Get via CMD
  • Download Manually
  • macOS
  • Windows
  • Linux (Ubuntu/Debian)
1
If you have previously removed git (git comes preinstalled on macOS):Install Git
or install Xcode Command Line Tools:
xcode-select --install
2
Open the Terminal.
3
Navigate to your preferred installation directory with cd command, or run the following command to continue installation in the default location in your home directory:
mkdir -p ~/FortytwoRelay && cd ~/FortytwoRelay
4
Run the following commands to clone the node package and enter the folder:
git clone https://github.com/Fortytwo-Network/fortytwo-relay-setup
cd fortytwo-relay-setup
3

Setup the `.env` file

Create an .env file from the .env.example reference file and update environment variables:
cp .env.example .env
Open the .env file and specify your unique FT_ACCOUNT_PRIVATE_KEY.
Read the ‘Environment Setup’ page for details.
Your private key must be different from the account that you use with your Inference Node.
Keep your Private Key secure! Never share it publicly or commit it to version control systems.
4

Set up the port

Check the .env file and ensure that FT_NODE_LISTENER_PORT is publicly accessible over both TCP and UDP. Static public IP is required.‘Ports Availablity Verification’ can help you check if the Swarm will be able to see your node.

​
How To Run a Relay Node Alongside an Inference Node

To run your Inference and Relay Nodes on the same machine at the same time, you need to:
1

Edit the .env file

  • Change the default FT_NODE_LISTENER_PORT and FT_RPC_SERVICE_PORT. They have to be different from the Inference Node ports, which by default are 42042 and 42420 respectively.
  • Define a unique FT_ACCOUNT_PRIVATE_KEY, it must be different from the account that you use with your Inference Node.
Read the ‘Environment Setup’ page for details.
2

Ensure that FT_NODE_LISTENER_PORT is publicly accessible over both TCP and UDP

Note that static public IP is required.‘Ports Availablity Verification’ can help you check if the Swarm will be able to see your node.

​
3. Launching the Fortytwo Relay Node

1

Launch Docker

Launch Docker and wait until its interface says “Engine running”.
2

Build the Docker Compose services

  docker compose build
3

Run the services in the background

  docker compose up -d

​
How to Make Sure it Works?

If everything went successfully, you should now be able to open Docker and see the fortytwo-relay-setup or fortytwo-relay-setup-main process running (depending on how you got the repository). If you unwrap it and go to fortytwo-relay container, you can see the logging of the node running successfully. The node periodically tests its health and reports on your relay address status, like in this example: 
fortytwo-relay  | UTC 20XX-XX-25 14:25:14.520081  INFO Check health
fortytwo-relay  | UTC 20XX-XX-25 14:25:14.520106  INFO Relay address is public. Current address /ip4/X.XXX.XXX.XX/tcp/42042
The most common error you might encounter is an issue with closed ports: 
WARN Relay address status is unknown (attempt X/3). Please ensure that your node listener port is accessible from the outside.
ERROR Failed to determine NAT status after 3 attempts.
In this case, please refer to the ‘Environment Setup’ page.

​
4. Operating Your Node

The node will remain fully operational until it is terminated by the user or the system restarts.

​
Updating Your Node

The node updates automatically every time it is launched and while operational.

​
Stopping Your Node

To stop the running container, either stop it from the Docker interface, or execute the following command from the same folder where the docker-compose.yml is located: 
docker compose down

​
Support

If you encounter any issues or have questions about Relay nodes:
  • Join our Discord community . Relay Noderunners have access to the #relay-support channel.
    • The Relay Noderunner role is required to access the #relay-support channel and is assigned to you automatically if you specify your Discord username in your Relay Application Form .
    • If you did not specify your Discord username in your Application, contact our Community team on Discord to receive the Relay Noderunner role.
  • See our ‘FAQ’.