News Blockchain and technology
STONfi opens Tongrid: Rust libraries for TON data services
Code developed for STONfi's indexing infrastructure is now available to TON developers. It supplies reusable components, but does not include an entire production service ready to run.
Checked on 21 November 2026.
What developers can now inspect
STONfi Dev has opened Tongrid, a collection of open-source Rust libraries for building applications and services on TON. The Coindar events calendar dates the publication to 20 November 2026. STONfi's official Telegram announcement links to a public repository and says the components grew out of the company's indexing and backend systems. Other teams can now inspect the code and incorporate parts into their own infrastructure.
The official Tongrid repository (Opens in a new tab) describes a collection for querying, indexing and serving TON data. Indexing organises network information so an application can search and display it. Building that layer is a separate job from designing the wallet screen or data page a user sees.
STONfi's announcement lists monitoring network activity, synchronising data, reading accounts and smart contracts, and retrieving information about jettons, the tokens used in the TON ecosystem. It also identifies an API client for connecting applications to Tongrid endpoints. These are developer tools; the publication is not a new coin launch.
Open code is not a server operated for you
The repository uses the Apache-2.0 licence and distinguishes the public libraries from components maintained separately: application binaries, deployment configuration, credentials and orchestration of live systems. That boundary matters for a small team estimating what it can take from the repository and what it still needs to establish itself.
STONfi presents a mainnet synchronisation demo for experimentation. A demo can show how components fit together, but it is not a commitment on availability, throughput or suitability for a particular system. We have not conducted a comparative performance test, and the words open source do not mean that your deployment has already passed a security review.
The data source remains part of the decision. A service displaying blockchain records depends on how it collects and updates them. Our blockchain guide provides a starting point for understanding the distinction between a network record and an application's interpretation of information.
Evaluate components against a defined task
Start with a specific requirement: which account data must appear, how recent it needs to be, and what should happen when an endpoint is unavailable. Then choose the components needed. This makes it easier to distinguish a library that solves a defined problem from copying an entire system without understanding its assumptions.
The repository documentation recommends pinning a dependency to a reviewed code revision instead of pulling an uncontrolled change into every build. A team adopting the libraries remains responsible for secrets management, testing, monitoring and its upgrade process. Opening the code enables inspection and reuse; it does not transfer operational responsibility back to STONfi.
For an Israeli developer working with TON, this is a global infrastructure option to assess through an ordinary development process. The announcement does not establish a special Israeli offering, a new service price or a measured saving. The potential benefit is reducing repeated engineering work and making it easier to understand how a data service is built.