Quick Start

Join the “Hitchhiking to AGI” ProgramSubmit an application to join the first wave of Inference Noderunners: Application Form

1. Preparing

Review the requirements

Verify that your device meets the ‘Requirements’.

Choose how you will run the node

There are currently three ways to run the Inference Node: Fortytwo App, Fortytwo Container, and Fortytwo CLI.To pick the one that suits you best, refer to the ‘Features’ page.

2. Installing the Node

Please ensure you have received an acceptance email with an activation code before attempting to install the Inference Node.

A unique activation code is required for each device the node is installed on.

Fortytwo App
Fortytwo Container
Fortytwo CLI

macOS
Windows
Linux (Ubuntu/Debian)

Download Fortytwo App for macOS

downloads.fortytwo.network/updates/latest-mac

Navigate to default downloads directory where the Fortytwo-x.x.x-mac.dmg file is located.

Run Fortytwo-x.x.x-mac.dmg.

Follow the on-screen instructions.

If you are updating from version 0.2.1 and earler, follow the steps in the Updating from Versions 0.2.1 and Earlier section.

Run the application.

3. Operating Your Node

The node will remain fully operational until it is stopped by the user, the application is closed by the user or the system restarts. You can minimize or close the application window, switch to other applications – the node will continue running in the background and will be available in system tray.

Updating Your Node

Fortytwo App updates automatically. Sometimes the user might be asked to restart the application to install the most recent updates.If you face issues with the updates, you can manually check the current version of ።‖ Fortytwo App on the Changelog page, and then manually download and reinstall the app using the current version links:

Download current version for macOS

Download current version for Windows

Download current version for Linux (Ubuntu/Debian)

You can find your current app version in the About window.

macOS: Updating from Versions 0.2.1 and Earlier

Unwrap for details

Versions 0.2.2 and above are code-signed, which means its internal app identity has changed from 0.2.1 and earlier versions. Because of this, the new version cannot access data previously stored in the Keychain by the unsigned builds. Fortytwo continues to use macOS Keychain to securely store your private key at system level.When launching the new version, macOS may ask for your system password to grant Fortytwo access to its secure data — you have two options:

You can safely enter your password and click “Always Allow” to avoid future prompts
Or you can delete the previous data and restore your profile in the new version as described below:

Steps for macOS users to reset the app data

Export your private key

Important! If you haven’t already saved your recovery phrase or at least your private key, export your private key now — otherwise, you will lose access to your account and your node.

How to export your private key:

Right click on the Fortytwo App icon in the Menu Bar.
Select Account > Export Private Key.
Select destination and confirm.

Make sure to save it to a secure location.

Delete the old app

Open your Apps folder in Finder. Select Fortytwo and move it to Trash.

Delete the files left from the old app

Find the Fortytwo app folder and move it to Trash.Short path:

~/Fortytwo

Full path:

/users/{username}/Fortytwo

Delete the old record

Open the Terminal and run this command:

security delete-generic-password -s "Fortytwo Safe Storage" || true

Install the latest version of the Fortytwo App

Download Fortytwo App for macOS

downloads.fortytwo.network/updates/latest-mac

Launch the App

Run the app and sign in again using your private key or secret recovery phrase.

Prerequisites:
hardware
Nvidia graphic card(s) on Windows or Linux
CPU on x86_64 architecture
software
Installed NVIDIA Container Toolkit
Installed Docker
Installed Git

Get the repository

Fortytwo Inference Node Setup

Clone the repository

Cloning the Repository from GitHub

Note: We do not recommend downloading and setting up the repository archive manually as it will be harder to keep Fortytwo Container up to date.

Windows
Linux (Ubuntu/Debian)

If you don’t have Git installed:
Install Git .

Open PowerShell as Administrator.

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:

New-Item -Path "$HOME\FortytwoContainer" -ItemType Directory -Force; Set-Location "$HOME\FortytwoContainer"

Run the following commands to clone the node package and enter the folder:

git clone https://github.com/Fortytwo-Network/fortytwo-inference-node-setup
cd fortytwo-inference-node-setup

If you don’t have Git installed: Install Git .

Open Terminal.

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 ~/FortytwoContainer && cd ~/FortytwoContainer

Run the following commands to clone the node package and enter the folder:

git clone https://github.com/Fortytwo-Network/fortytwo-inference-node-setup
cd fortytwo-inference-node-setup

Get the private key of your Web3 account

Your Web3 account’s private key must be different for every unique node in the network that you run simultaneously. There should be no two nodes with the same ID in the network.
For example: if you intend to run 8 nodes on 8×GPU rig at the same time, you will need 8 private keys.

Wallet and Account Management

This article will explain accounts and their credentials if you are new to Web3.

You have the following options to get the private key:

A. Create a new Web3 account with an activation code

Create a new account

make get-drop PRIVATE_KEY_PATH=$PATH_TO_SAVED_KEY CODE=$ACTIVATION_CODE

$PATH_TO_SAVED_KEY — The path where the file with your private key will be generated.

Make sure that the defined path exists.
If .account_private_key already exists in this locaiton, it will be ovewritten.

$ACTIVATION_CODE — Your activation code. It can only be used once.When executed, a new private key named .account_private_key will be generated at the defined path.

The log will show you the credentials of your new account. It is crucial to write your Secret Recovery Phrase down now. You will not be able to recover it later.

Get your private key address.

.account_private_key file is a hidden file by default. Reveal it. Text inside it is your private key.

Platform-specific notes on how to reveal hidden files

macOS
Windows

Open the folder in Finder.
Press Command + Shift + . to toggle hidden file visibility.

Open File Explorer.
Select the View tab from the top menu.
Click Show → Hidden items.
Hidden files and folders (including .account_private_key) will now be visible.

B. Connect the existing Web3 account with an activation code

Connect your wallet to the program

make get-drop WALLET=$PUBLIC_WALLET_ADDRESS CODE=$ACTIVATION_CODE

$PUBLIC_WALLET_ADDRESS — Your Web3 EVM-compatible account’s public address.
$ACTIVATION_CODE — Your activation code. It can be used only once.This command will add the wallet you defined to the gas compensation program.

Get your private key address.

Get your Web3 EVM-compatible account’s private key address from any Web3 wallet.

C. Migrate to Fortytwo Container from an already existing node

Get your private key address.See ‘Exporting Your Node ID, Your Web3 Credentials’ for instructions on how to get your private key from another Fortytwo application or get it from a Web3 wallet.

D. Fund an existing Web3 account on your own

Get your private key address.Get your Web3 EVM-compatible account’s private key address from any of Web3 wallets.

With no activation code, you’ll need to manually monitor and top-up MON and FOR balance for your node to work, with 2 MON and 100 FOR required to start the node. Your node will not automatically receive MON refills with no activation code.

With Fortytwo Container, you can choose the way you run your node:

One node per machine
Multi-node setup on a single machine

Setup the `.env` file

Create an .env file from the .env.example reference file and update the environment variables:

cp .env.example .env

Open the .env file and specify unique credentials for the node:

FT_ACCOUNT_PRIVATE_KEY — Unique Web3 account private key
FT_CAPSULE_LLM_HF_REPO and FT_CAPSULE_LLM_HF_MODEL_NAME — Unique model credentials

Unwrap for .env setup example

# protocol
FT_ACCOUNT_PRIVATE_KEY=$YOUR-UNIQUE-PRIVATE-KEY
FT_NODE_LISTENER_PORT=42042

# capsule 
FT_CAPSULE_HTTP_HOST="0.0.0.0"
FT_CAPSULE_HTTP_PORT=42442
FT_CAPSULE_LLM_HF_REPO=Fortytwo-Network/Strand-Rust-Coder-14B-v1-GGUF
FT_CAPSULE_LLM_HF_MODEL_NAME=Fortytwo_Strand-Rust-Coder-14B-v1-Q4_K_M.gguf

INPUT_MODEL_CACHE=./model_cache

Read the ‘Environment Setup’ page for more details.

Pre-download the model

It is desirable to pre-download the model before attempting to start the node.
Use this command to download a model:

make download-llm LLM_HF_REPO=$REPO-ID LLM_HF_MODEL_NAME=$MODEL-ID

Use the same credentials as in the environment file. In our case it looks like this:

make download-llm LLM_HF_REPO=Fortytwo-Network/Strand-Rust-Coder-14B-v1-GGUF LLM_HF_MODEL_NAME=Fortytwo_Strand-Rust-Coder-14B-v1-Q4_K_M.gguf

Read the ‘Environment Setup’ page for more details.

Launching the Node

If restarting your node after relaunching the terminal/OS, don’t forget that the following should be executed from the node repository folder, where your .env and docker-compose.yml are located.

Update the repository

To make sure that your repo is up to date, before each start, get the latest updates with the git pull command:

git pull

Launch Docker

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

Build the Docker Compose services

docker compose build

Run the services in the background

docker compose up -d

If the model defined in the .env file is not pre-downloaded, then your node will download it at startup.
In that case Capsule module might report “unhealthy” status if the download is too big. Note that it is not a bug with your setup.
Technically, your Capsule is still downloading the model and will start when it is ready. However, in this case, you will have to manually observe when your capsule will launch inside the Docker application, watch for the fortytwo-capsule container, then start the fortytwo-protocol container from inside the Docker application.The easiest way to not catch this behavior right now is to pre-download the models from step #4.

How to Make Sure it Works?

If everything went successfully, after launch, you can verify that the nodes are running correctly with:

docker ps

Your node should be running in its own container with the all the available GPU resources.You should as well be able to open Docker application and see the fortytwo-inference-node-setup process running.If you unwrap it, you can see the logging of the node running successfully with two containers:

fortytwo-capsule — Capsule reports on the model loading and performing. Starts first.
fortytwo-protocol — Protocol reports on the network. Protocol starts only after Capsule is all set and ready.

View Logs

docker compose logs -f -t --tail 100

Prints the last 100 lines of logs for all services, then continues streaming new ones.
Change --tail option to another value if required.

Export Logs

macOS
Windows
Linux (Ubuntu/Debian)

MACOS IS CURRENTLY NOT SUPPORTED

PowerShell

docker compose logs -t > "ft_node_logs_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"

Bash

docker compose logs -t > "ft_node_logs_$(date +'%Y%m%d_%H%M%S').txt"

The unique strength of the Fortytwo Container setup is that it allows to run several nodes on a single machine and allocate a particular GPU to a particular node. Let’s explore this functionality with an example setup where we would want to launch three nodes on a 4×GPU rig.The models for this example are:

Setup the `.env` files

Each Inference Node requires its own unqiue environment defined in the .env file. Since we want to run 3 nodes, we will be creating 3 environment files from the .env.example reference file and update the environment variables:

cp .env.example .env.strand-rust-coder
cp .env.example .env.vibethinker
cp .env.example .env.qwen

Open each newly created .env file and specify the unique credentials for each node:

FT_ACCOUNT_PRIVATE_KEY — Unique Web3 account private key
FT_NODE_LISTENER_PORT — Unique port
FT_CAPSULE_LLM_HF_REPO and FT_CAPSULE_LLM_HF_MODEL_NAME — Unique model credentials

For our example, this will be the setup, unwrap to see the contents of each file:

.env.strand-rust-coder

# protocol
FT_ACCOUNT_PRIVATE_KEY=$YOUR-FIRST-UNIQUE-PRIVATE-KEY
FT_NODE_LISTENER_PORT=42042

# capsule 
FT_CAPSULE_HTTP_HOST="0.0.0.0"
FT_CAPSULE_HTTP_PORT=42442
FT_CAPSULE_LLM_HF_REPO=Fortytwo-Network/Strand-Rust-Coder-14B-v1-GGUF
FT_CAPSULE_LLM_HF_MODEL_NAME=Fortytwo_Strand-Rust-Coder-14B-v1-Q4_K_M.gguf

INPUT_MODEL_CACHE=./model_cache

.env.vibethinker

# protocol
FT_ACCOUNT_PRIVATE_KEY=$YOUR-SECOND-UNIQUE-PRIVATE-KEY
FT_NODE_LISTENER_PORT=42043

# capsule 
FT_CAPSULE_HTTP_HOST="0.0.0.0"
FT_CAPSULE_HTTP_PORT=42442
FT_CAPSULE_LLM_HF_REPO=mradermacher/VibeThinker-1.5B-GGUF
FT_CAPSULE_LLM_HF_MODEL_NAME=VibeThinker-1.5B.Q4_K_M.gguf

INPUT_MODEL_CACHE=./model_cache

.env.qwen

# protocol
FT_ACCOUNT_PRIVATE_KEY=$YOUR-THIRD-UNIQUE-PRIVATE-KEY
FT_NODE_LISTENER_PORT=42044

# capsule 
FT_CAPSULE_HTTP_HOST="0.0.0.0"
FT_CAPSULE_HTTP_PORT=42442
FT_CAPSULE_LLM_HF_REPO=unsloth/Qwen3-1.7B-GGUF
FT_CAPSULE_LLM_HF_MODEL_NAME=Qwen3-1.7B-Q4_K_M.gguf

INPUT_MODEL_CACHE=./model_cache

Read the ‘Environment Setup’ page for more details.

Pre-download models

It is desirable to pre-download the models before attempting to start the nodes.
Use this command to download a model:

make download-llm LLM_HF_REPO=$REPO-ID LLM_HF_MODEL_NAME=$MODEL-ID

Use the same credentials as in the environment files. In our case it looks like this:

make download-llm LLM_HF_REPO=Fortytwo-Network/Strand-Rust-Coder-14B-v1-GGUF LLM_HF_MODEL_NAME=Fortytwo_Strand-Rust-Coder-14B-v1-Q4_K_M.gguf
make download-llm LLM_HF_REPO=mradermacher/VibeThinker-1.5B-GGUF LLM_HF_MODEL_NAME=VibeThinker-1.5B.Q4_K_M.gguf 
make download-llm LLM_HF_REPO=unsloth/Qwen3-1.7B-GGUF LLM_HF_MODEL_NAME=Qwen3-1.7B-Q4_K_M.gguf

Read the ‘Environment Setup’ page for more details.

Create Docker Compose files

Create separate compose files for each node from the docker-compose.yml reference:

cp docker-compose.yml docker-compose-strand-rust-coder.yml
cp docker-compose.yml docker-compose-vibethinker.yml
cp docker-compose.yml docker-compose-qwen.yml

Plan the GPU usage

Verify your GPU configuration using the nvidia-smi command:

nvidia-smi

In our example, we established that we have a 4×GPU rig. So, we should have 4 GPUs with IDs 0, 1, 2, and 3 (shown in the first GPU column).Our plan is to:

For Fortytwo_Strand-Rust-Coder — Use GPU #1 and #2
For VibeThinker — Use GPU #0
For Qwen3 — Use GPU #3

Fortytwo_Strand-Rust-Coder is the largest model here, so we allocate two GPUs to it.
GPU order doesn’t matter here.nvidia-smi output should be as follows:

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 570.195.03             Driver Version: 570.195.03     CUDA Version: 12.8     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA A10G                    Off |   00000000:00:1B.0 Off |                    0 |
|  0%   29C    P0             58W /  300W |       0MiB /  23028MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   1  NVIDIA A10G                    Off |   00000000:00:1C.0 Off |                    0 |
|  0%   28C    P0             56W /  300W |       0MiB /  23028MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   2  NVIDIA A10G                    Off |   00000000:00:1D.0 Off |                    0 |
|  0%   28C    P0             58W /  300W |       0MiB /  23028MiB |      3%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   3  NVIDIA A10G                    Off |   00000000:00:1E.0 Off |                    0 |
|  0%   28C    P0             56W /  300W |       0MiB /  23028MiB |      2%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

Assign GPUs to Each Node

Edit each Docker Compose file to assign specific GPU(s) by their IDs.For our example, we need to make the following edits:

docker-compose-strand-rust-coder.yml

deploy:
  resources:
    reservations:
      devices:
        - driver: nvidia
          device_ids: ['1', '2']  # Assign to GPUs 1 and 2
          capabilities:
            - gpu

docker-compose-vibethinker.yml

deploy:
  resources:
    reservations:
      devices:
        - driver: nvidia
          device_ids: ['0']  # Assign to GPU 0
          capabilities:
            - gpu

docker-compose-qwen.yml

deploy:
  resources:
    reservations:
      devices:
        - driver: nvidia
          device_ids: ['3']  # Assign to GPU 3
          capabilities:
            - gpu

Using device_ids: ['all'] will assign all available GPUs for that node.

Launching the Node

If you are restarting your node after relaunching the terminal/OS, don’t forget that the following should be executed from the node repository folder, where your .env and custom docker compose .yml files are located.

Update the repository

To make sure that your repo is up to date, before each start, get the latest updates with the git pull command:

git pull

Launch Docker

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

Build the Docker Compose services

docker compose build

Run the services in the background

Start each node using its respective compose file and environment file:

docker compose -f docker-compose-strand-rust-coder.yml --env-file .env.strand-rust-coder -p strand-rust-coder up -d
docker compose -f docker-compose-vibethinker.yml --env-file .env.vibethinker -p vibethinker up -d
docker compose -f docker-compose-qwen.yml --env-file .env.qwen -p qwen up -d

If a model is not pre-downloaded, your node downloads it upon startup.
In that case, the Capsule module might report “unhealthy” status if the download is too big. Note that it is not an issue with your setup.
Technically, your Capsule is still downloading the model and will start when it is ready. However, in this case, you will have to manually observe when your capsule launches inside the Docker application, watch for the fortytwo-capsule container, then start the fortytwo-protocol container from inside the Docker application.The easiest way to avoid this behavior at the moment is to pre-download the models from step #4.

How to Make Sure it Works?

After launch, you can verify that the nodes are running correctly with this command:

docker ps

Each node should be running in its own container with the assigned GPU resources.You should also be able to open the Docker application and see the strand-rust-coder, vibethinker, and qwen processes running.If you unwrap each one of them, you can see the logging of the node running successfully with two containers:

fortytwo-capsule — Capsule reports on the model loading and performance. Starts first.
fortytwo-protocol — Protocol reports on the network. Protocol starts only after Capsule is set and ready.

View Logs

docker compose logs -f -t --tail 100

Prints the last 100 lines of logs for all services, then continues streaming new ones.
Change --tail option to another value if required.If you only want to see the logs of a particular process, replace docker-compose-name.yml with that process’s name.

docker compose -f docker-compose-name.yml logs -f -t --tail 100

Export Logs

macOS
Windows
Linux (Ubuntu/Debian)

MACOS IS CURRENTLY NOT SUPPORTED

PowerShell

docker compose logs -t > "ft_node_logs_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"

Bash

docker compose logs -t > "ft_node_logs_$(date +'%Y%m%d_%H%M%S').txt"

If you only want to export the logs of a particular process, replace docker-compose-name.yml with that process’s name.

macOS
Windows
Linux (Ubuntu/Debian)

MACOS IS CURRENTLY NOT SUPPORTED

PowerShell

docker compose -f docker-compose-name.yml logs -t > "ft_node_logs_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"

Bash

docker compose -f docker-compose-name.yml logs -t > "ft_node_logs_$(date +'%Y%m%d_%H%M%S').txt"

3. 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 components update automatically every time it is launched and while operational.However, you need to manually update the repository to get the latest environment updates.At every start, execture the following command.

git pull

If everything is stable, check for updates on the Changelog page. When you see a ⊡ Fortytwo Container update available, stop your node, run the git pull command, and then restart the node. These commands will let you compare your current version to remote version:

git fetch
git log -1 origin/main --format="Remote: %h %ci"
git log -1 --format="Local:  %h %ci"

Stopping Your Node

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

docker compose down

If you want to stop one particular process, replace docker-compose-name.yml with that process’s name.

docker compose -f docker-compose-name.yml down

macOS
Windows
Linux (Ubuntu/Debian)

Open the Terminal.

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:

Zsh

mkdir -p ~/FortytwoCLI && cd ~/FortytwoCLI

Run the following commands to download the node package, extract it, and execute the installation script:

Zsh

curl -L -o fortytwo-console-app.zip https://github.com/Fortytwo-Network/fortytwo-console-app/archive/refs/heads/main.zip
unzip fortytwo-console-app.zip -d . && rm fortytwo-console-app.zip
cd fortytwo-console-app-main
chmod +x macos.sh && ./macos.sh

Follow the on-screen instructions in the script to complete the setup.

The node will start automatically.

Open PowerShell as Administrator.

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:

PowerShell

New-Item -Path "$HOME\FortytwoCLI" -ItemType Directory -Force; Set-Location "$HOME\FortytwoCLI"

Run the following commands to download the node package, extract it, and execute the installation script with a temporary execution policy override:

PowerShell

Invoke-WebRequest -Uri "https://github.com/Fortytwo-Network/fortytwo-console-app/archive/refs/heads/main.zip" -OutFile "fortytwo-console-app.zip"
Expand-Archive -Path fortytwo-console-app.zip -DestinationPath . -Force; Remove-Item -Path fortytwo-console-app.zip
cd fortytwo-console-app-main
Unblock-File -Path .\windows.ps1
powershell -ExecutionPolicy Bypass -File .\windows.ps1

Follow the on-screen instructions to complete the setup.

The node will start automatically.

Open the Terminal.

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:

Bash

mkdir -p ~/FortytwoCLI && cd ~/FortytwoCLI

Run the following commands to download the node package, extract it, and execute the installation script:

Bash

curl -L -o fortytwo-console-app.zip https://github.com/Fortytwo-Network/fortytwo-console-app/archive/refs/heads/main.zip
unzip fortytwo-console-app.zip
cd fortytwo-console-app-main
chmod +x linux.sh && ./linux.sh

Follow the on-screen instructions to complete the setup.

The node will start automatically.

3. Operating Your Node

The node will remain fully operational until it is terminated by the user or the system restarts. You can minimize the terminal window or switch to other applications – the node will continue running in the background.

Updating Your Node

Fortytwo node automatically updates every time it is launched. When you start the node, it checks for the latest available version and installs any updates before running.If you face issues with the updates, you can manually check the current version of >_ Fortytwo CLI on the Changelog page, and then manually download and reinstall the app.You can find your current version under ◰ Setup script — version validation when lauhcing the CLI script.

Stopping Your Node

Press Ctrl+C in the terminal window to terminate the node process.

Restarting Fortytwo Node

On October 23, 2025, we’ve changed the name of the default folder from Fortytwo to FortytwoCLI. If you’ve installed your Fortytwo CLI before this date, your default path will differ. To access the folder, look for Fortytwo instead of FortytwoCLI.

macOS
Windows
Linux (Ubuntu/Debian)

Open the Terminal.

Navigate to the directory where the node is installed using the cd command. If the node was installed in the default location, run:

Zsh

cd ~/FortytwoCLI/fortytwo-console-app-main

Run the node startup script:

Zsh

./macos.sh

Follow the on-screen instructions.

The node will start automatically.

Open PowerShell as Administrator.

Navigate to the directory where the node is installed using the cd command. If the node was installed in the default location, run:

PowerShell

Set-Location "$HOME\FortytwoCLI\fortytwo-console-app-main"

Run the node startup script:

PowerShell

powershell -ExecutionPolicy Bypass -File .\windows.ps1

Follow the on-screen instructions.

The node will start automatically.

Open the Terminal.

Navigate to the directory where the node is installed using the cd command. If the node was installed in the default location, run:

Bash

cd ~/FortytwoCLI/fortytwo-console-app-main

Run the node startup script:

Bash

./linux.sh

Follow the on-screen instructions.

The node will start automatically.

Download Fortytwo App for macOS

Download Fortytwo App for Windows

Download Fortytwo App for Linux (Ubuntu/Debian)

Download current version for macOS

Download current version for Windows

Download current version for Linux (Ubuntu/Debian)

Download Fortytwo App for macOS

Get Stated

Inference Node

Relay Node

API

Legal

1. Preparing

2. Installing the Node

3. Operating Your Node

Updating Your Node

macOS: Updating from Versions 0.2.1 and Earlier

Fortytwo Inference Node Setup

Wallet and Account Management

Launching the Node

How to Make Sure it Works?

View Logs

Export Logs

Launching the Node

How to Make Sure it Works?

View Logs

Export Logs

3. Operating Your Node

Updating Your Node

Stopping Your Node

3. Operating Your Node

Updating Your Node

Stopping Your Node

Restarting Fortytwo Node

Get Stated

Inference Node

Relay Node

API

Legal

​1. Preparing

​2. Installing the Node

Download Fortytwo App for macOS

Download Fortytwo App for Windows

Download Fortytwo App for Linux (Ubuntu/Debian)

​3. Operating Your Node

​Updating Your Node

Download current version for macOS

Download current version for Windows

Download current version for Linux (Ubuntu/Debian)

​ macOS: Updating from Versions 0.2.1 and Earlier

Download Fortytwo App for macOS

Fortytwo Inference Node Setup

Wallet and Account Management

​Launching the Node

​How to Make Sure it Works?

​View Logs

​Export Logs

​Launching the Node

​How to Make Sure it Works?

​View Logs

​Export Logs

​3. Operating Your Node

​Updating Your Node

​Stopping Your Node

​3. Operating Your Node

​Updating Your Node

​Stopping Your Node

​Restarting Fortytwo Node

1. Preparing

2. Installing the Node

3. Operating Your Node

Updating Your Node

macOS: Updating from Versions 0.2.1 and Earlier

Launching the Node

How to Make Sure it Works?

View Logs

Export Logs

Launching the Node

How to Make Sure it Works?

View Logs

Export Logs

3. Operating Your Node

Updating Your Node

Stopping Your Node

3. Operating Your Node

Updating Your Node

Stopping Your Node

Restarting Fortytwo Node