Installation

Javascript SDK

You no longer need to manually install binaries.

All binaries for development and testing are provided with the packages:

• Choose your Javascript SDK

Precompiled binaries

Prerequisites

For the local development of TOS smart contracts without Javascript, you need to prepare binaries of func, fift, and lite client on your device.

You can download and set them up below, or read this article from TOS Society:

• Setting up TOS Development Environment

1. Download

Download the binaries from the table below. Make sure to select the correct version for your operating system and to install any additional dependencies:

OS	TOS binaries	fift	func	lite-client	Additional dependencies
MacOS x86-64	download	download	download	download
MacOS arm64	download				brew install openssl ninja libmicrohttpd pkg-config
Windows x86-64	download	download	download	download	Install OpenSSL 1.1.1
Linux x86_64	download	download	download	download
Linux arm64	download				sudo apt install libatomic1 libssl-dev

2. Setup your binaries

Windows

1. After downloading, you need to create a new folder. For example: C:/Users/%USERNAME%/tos/bin and move the installed files there.

2. To open the Windows environment variables, press the Win + R buttons on the keyboard, type sysdm.cpl, and press Enter.

3. On the "Advanced" tab, click the "Environment Variables..." button.

4. In the "User variables" section, select the "Path" variable and click "Edit" (this is usually required).

5. To add a new value (path) to the system variable in the next window, click the button "New". In the new field, you need to specify the path to the folder where the previously installed files are stored:

   C:\Users\%USERNAME%\tos\bin\

6. To check whether everything was installed correctly, run in terminal (cmd.exe):

   fift -V -and func -V -and lite-client -V

7. If you plan to use fift, you need FIFTPATH environment variable with the necessary imports:

   1. Download fiftlib.zip
   2. Open the zip in some directory on your machine (like C:/Users/%USERNAME%/tos/lib/fiftlib)
   3. Create a new (click button "New") environment variable FIFTPATH in "User variables" section.
   4. In the "Variable value" field, specify the path to the files: /%USERNAME%/tos/lib/fiftlib and click OK. Done.

important

Instead of the %USERNAME% keyword, you must insert your own username.

Linux / MacOS

1. After downloading, make sure the downloaded binaries are executable by changing their permissions.

   chmod +x func
   chmod +x fift
   chmod +x lite-client

2. It's also useful to add these binaries to your path (or copy them to /usr/local/bin) so you can access them from anywhere.

   cp ./func /usr/local/bin/func
   cp ./fift /usr/local/bin/fift
   cp ./lite-client /usr/local/bin/lite-client

3. To check that everything was installed correctly, run in terminal.

   fift -V && func -V && lite-client -V

4. If you plan to use fift, also download fiftlib.zip, open the zip in some directory on your device (like /usr/local/lib/fiftlib), and set the environment variable FIFTPATH to point to this directory.

   unzip fiftlib.zip
   mkdir -p /usr/local/lib/fiftlib
   cp fiftlib/* /usr/local/lib/fiftlib

Hey, you're almost finished :)

Remember to set the environment variable FIFTPATH to point to this directory.

Build from source

If you don't want to rely on pre-compiled binaries and prefer to compile the binaries yourself, you can follow the official instructions.

The ready-to-use gist instructions are provided below:

Linux (Ubuntu / Debian)

sudo apt update
sudo apt install git make cmake g++ libssl-dev zlib1g-dev wget
cd ~ && git clone https://github.com/tos-network/tos.git
cd ~/tos && git submodule update --init
mkdir ~/tos/build && cd ~/tos/build && cmake .. -DCMAKE_BUILD_TYPE=Release && make -j 4

Other sources for binaries

The core team provides automatic builds for several operating systems as GitHub Actions.

Click on the link above, choose the workflow on the left relevant to your operating system, click on a recent green passing build, and download tos-binaries under "Artifacts".