TON Research

This open development community and enthusiasts research place. We will post our news and updates this project there.

TON whitepapers:

• Telegram Open Network Whitepaper
• Telegram Open Network Virtual Machine
• Telegram Open Network Blockchain
• Fift: A Brief Introduction (Smart contract language for TON)

---

Table of contents:

• What we already did:
• Future steps:
• Installation & Setup
  • Docker
  • Releases (macOS)
• Tutorial (how to)
• Got questions?
• Project links:
• Contributing
• Contact us on telegam

What we already did:

• 🏗 Build lite client node: First release

• 🖥 Started Lite Client on macOS

• 📩 Explain, how to send transactions to TON network

• 🎓 Now we are writing tutorials / FAQ / HOWTO how to use TON.

• 🏗 Instructions for building lite client on Ubuntu 16.04

• 🐳 Packaged lite client into Docker container

• 👉 any request and suggestions are very welcome!

Future steps:

Creating FAQ & Video tutorial (WIP): ✨feel free to propose your topics

• Step-by-step guide: How to build a TON client
• How to get test Grams
• Development:
  • Write first hello-world smart contract
  • How to deploy a smart contract
  • How to send transactions

Also, you will find there:

• Future releases of binaries
• A FAQ with most popular questions (WIP)

Installation & Setup

There is two options. By running Docker or precompilled binary for macOS below:

Docker

The easiest way to run the node in a docker container:

docker run -d copperbits/ton

You might want to run in interactive mode and mount current dir into the container to be able to compile fif files:

docker run -ti -v "$(pwd):/data" --name ton copperbits/ton

Compile a fif file (if your container is running and current dir is mounted):

docker exec ton fift test.fif

Releases (macOS)

Lite Client Latest release

• Download latest release
• Go to command line, where binary placed
• Run:

./test-lite-client -C ton-lite-client-test1.config.json

• run help to get started

Tutorial (how to)

HOWTO.md

Got questions?

If you have any quistions about project/installation - feel free to open an issue!

Project links:

• Bugs, suggestions or feature requests, open an issue
• Star GitHub repo to support this project 👍
• License in GNU Lesser General Public License v2.1 🔓
• Shipped by CooperBits team ☀️ and contributors 👏

Contributing

Your contributions are appreciated. You can follow CONTRIBUTING guide to get everything started.

Contact us on telegam

• Telegam public group

---

Readme: This is a distribution of a preliminary version of the TON Blockchain Lite Client along with the relevant portions of the TON Blockchain Library. It is not necessarily representative of the totality of the TON Blockchain code developed so far; rather it is a simplified stable version, containing only those files that are necessary for compiling the Lite Client, and sometimes outdated versions of these files sufficient for this purpose.

Use this software at your own risk; consult the DISCLAIMER for more information.

The software is licensed under GNU Lesser General Public License version 2 or later; consult LICENSE.LGPL and LGPL.v2 for more information. If you ever use any of these source files to develop your own versions of this or other software, you must attach a comment with the contents of LGPL.v2 to the beginning of each source file taken from this archive.

The software is likely to compile and work properly on most Linux systems. It should work on macOS and even Windows; however, we do not guarantee this for this preliminary version.

Basic compilation and installation instructions

1. Download and unpack the newest version of this archive, available at https://test.ton.org/download The TON Blockchain Test Network is updated quite often, so we cannot guarantee that older versions of the Lite Client will always work. Backward compatibility is not enforced at this development stage.

2. Install the newest versions of make, cmake (version 3.0.2 or later), OpenSSL (including C header files), and g++ or clang (or another C++14-compatible compiler as appropriate for your operating system).

3. Suppose that you have unpacked this archive to directory ~/lite-client, where ~ is your home directory, and that you have created an empty directory ~/liteclient-build. Then run the following in a terminal on a Linux system:

cd ~/liteclient-build
cmake ~/lite-client
cmake --build . --target test-lite-client

You might also want to build some extra utilities useful for smart-contract development:

cmake --build . --target fift

4. Download the newest configuration file from https://test.ton.org/ton-lite-client-test1.config.json :

wget https://test.ton.org/ton-lite-client-test1.config.json

5. Run the Lite Client:

./test-lite-client -C ton-lite-client-test1.config.json

If everything was installed successfully, the Lite Client will connect to a special server (a full node for the TON Blockchain Test Network #1) and will send some queries to the server. If you indicate a writeable "database" directory as an extra argument to the client, it will download and save the block and the state corresponding to the newest masterchain block:

./test-lite-client -C ton-lite-client-test1.config.json -D ~/ton-db-dir

Basic help info can be obtained by typing "help" into the Lite Client. Type "quit" or press Ctrl-C to exit.

6. Now you can create new smart contracts, examine the state of existing smart contracts, send external messages to smart contracts and so on. You can also use Fift (if you have compiled it) to compile, execute, and debug your smart contracts locally.

More details on these activities, including step-by-step instructions for creating a simple wallet smart contract (along with its source code), may be found in the HOWTO file included in this archive.

7. Some documentation on the TON Blockchain and TON Virtual Machine may be found at the download page https://test.ton.org/download . Be aware that this documentation may not be completely in sync with the version currently employed by the Test Network, because some minor implementation details are likely to be changed during the final development and testing phases.