Awesome nodes TON

Telegram Open Network (TON) is a next-generation blockchain and communication platform developed by the founders of the popular messenger Telegram

Official testnet site is: https://test.ton.org

System requirements for TON full node

Testnet:

Resource	Minimal option	Recommended option
Memory	4 GB *	8 GB and more
CPU	2 Cores	8 Cores
Disk	3-5 GB SSD daily	for the Testnet
Network	50 Mbps Up/Down	100 Mbps Up/Down

* Compilation may not pass with 2 GBytes of RAM

Mainnet: (based on the official How-To)

Resource	Minimal option	Recommended option
Memory	256 MB	8 GBytes and more
CPU	2 CPU x 8 Cores	16 Cores and more
Disk	*	512 GB SSD for hot data
Disk	*	8 TB HDD for archive
Network	100 Mbps Up/Down	1 Gbps Up/Down

* There is no estimation before the Mainnet launch

Contents

• Deployment in Ubuntu 18.04
• Dockerfile for TON fullnode

Deployment in Ubuntu 18.04

This recipe can be used for direct deployment in Ubuntu, creating Docker images and Packer images for a Full Node

• ubuntu-18.04/build.sh - Update system and build code
• ubuntu-18.04/configure.sh - Generate initial config
• ubuntu-18.04/startup.sh - Enable systemd autostart and log rotate feature

Full automatic install

Root priveleges required for creating directories and update system configs (sudo -i)

wget -O - https://raw.githubusercontent.com/awesome-nodes/ton/master/ubuntu-18.04/build.sh | bash
wget -O - https://raw.githubusercontent.com/awesome-nodes/ton/master/ubuntu-18.04/configure.sh | bash
wget -O - https://raw.githubusercontent.com/awesome-nodes/ton/master/ubuntu-18.04/startup.sh | bash

Rebuild

For rebuild it is reccommended to stop services, remove src directory and run build step agan

cd ~
wget -O build.sh https://raw.githubusercontent.com/awesome-nodes/ton/master/ubuntu-18.04/build.sh
chmod +x build.sh
rm -rf ton
systemctl stop ton.service
./build.sh
systemctl start ton.service

Manual start

You may start node manualy like this:

validator-engine -C /var/ton-work/etc/ton-global.config.json --db /var/ton-work/db/ -l /var/log/ton/log -t 2

where -t x means number of the threads for a multicore configuration. Default value is 8.

Inside the log directory, there are separates log files for the each thread. I would recommend using -t 1 for the first launch for easier debugging.