TON ADNL API
There are different ways to connect to blockchain:
- RPC data provider or another API: in most cases, you have to rely on its stability and security.
- ADNL connection: you're connecting to a liteserver. They might be inaccessible, but with a certain level of validation (implemented in the library), cannot lie.
- Tonlib binary: you're connecting to liteserver as well, so all benefits and downsides apply, but your application also contains a dynamic-loading library compiled outside.
- Offchain-only. Such SDKs allow to create and serialize cells, which you can then send to APIs.
Clients connect directly to Liteservers (nodes) using a binary protocol.
The client downloads keyblocks, the current state of the account, and their Merkle proofs, which guarantees the validity of the received data.
Read operations (like get-method calls) are made by launching a local TVM with a downloaded and verified state. It's worth noting that there is no need to download the full state of the blockchain, the client downloads only what is needed for the operation.
You can connect to public liteservers from the global config (Mainnet or Testnet) or run your own Liteserver and handle this with ADNL SDKs.
Read more about Merkle proofs at TON Whitepaper 2.3.10, 2.3.11.
Public liteservers (from the global config) exist to get you started with TON quickly. It can be used for learning to program in TON, or for applications and scripts that do not require 100% uptime.
For building production infrastructure - it is suggested use well prepared infrastructure:
- set up own liteserver,
- use Liteserver premium providers @liteserver_bot
Pros & Cons
✅ Reliable. Uses API with Merkle proof hashes to verify incoming binary data.
✅ Secure. Since it checks Merkle proofs, you can even use untrusted liteservers.
✅ Fast. Connects directly to TON Blockchain nodes, instead of using HTTP middleware.
❌ Complicated. More time is required to figure things out.
❌ Back-end first. Not compatible with web frontends (built for non-HTTP protocol), or requires HTTP-ADNL proxy.
API reference
Requests and responses to the server are described by the TL schema that allows you to generate a typed interface for a certain programming language.