TON Blockchain Testnet Lite Client to be Available

Telegram team hadn'tĀ confirmed the authenticity of the page and the data published on it
30 May 2019   354

Users have gained access to the test network of the Telegram Open Network (TON) blockchain platform - a preliminary version of the light client has been published.

This simplified version includes only the files needed for compilation, in particular, the RocksDB database and the Abseil library. After assembling and configuring the light client, it connects to the full node of the TON test network.

In addition, the site published step-by-step instructions for creating smart contracts in TON in the Fift programming language specially created for Telegram.

Additionally, users can familiarize themselves with the description of the TON virtual machine and blockchain platform.

It should be noted that representatives of Telegram did not publicly confirm the accuracy of the page and the data published on it.

Recall that the launch of the TON blockchain platform will take place in the third quarter of 2019. Earlier, developers reported on the successful conduct of a closed testing project.

You can get more info and download source code, configutation file, etc at the webpage.

Google to Propose to Develop Own Libc For LLVM

Development is caused by Google's unsatisfaction in the existing libc andĀ it's planned to be phased, gradually increasing functionality
26 June 2019   26

One of the developers from Google raised on the LLVM mailing list the topic of developing a multi-platform standard C-library (Libc) within the framework of the LLVM project. For a number of reasons, Google is not satisfied with the current libc (glibc, musl) and the company is on its way to developing a new implementation, which is proposed to be developed as part of LLVM.

LLVM developments have recently been used as the basis for building Google's assembly tools. The main idea is that if Google has already begun to develop its libc, then why not immediately develop its system as part of LLVM, which already offers its standard library for C ++ (Libc ++), but does not have a similar standard library for C ( Libc).

Development is planned to be phased, gradually increasing functionality. The first options are proposed to be in the form of a layer between the application and the system libc, from which the unrealized features will be borrowed. After reaching a certain level of functionality, the new Libc can be used as a complete replacement for the system Libc. It is planned to start with the support of x86-64 architecture, Linux and static binding (dynamic loading, packaging, and additional architectures will be implemented in the second place).

The project is still at the initial stage of development, but the basic goals have already been defined:

  • Modularity and development in accordance with the philosophy of supplying a granular library, rather than a monolithic set;
  • Static binding support in modes with PIE (Position-independent executables) and without PIE. Providing CRT (C runtime) and PIE loader for statically linked executable files;
  • Support for most of the functions of the standard C library with POSIX add-ons and some system-specific extensions in demand in existing applications;
  • Careful attitude to vendor-specific extensions and adding them only when necessary. For support for third-party extensions, it is proposed to use the Clang and libc ++ projects approach;
  • Using exemplary practices in development using LLVM tools, such as applying sanitizer and fuzzing testing from the start.

Get more info at the email.