Get a low-latency RPC endpoint to TON

The Open Network (TON) is Telegram’s community-revived sharded L1 whose “workchains” and “shardchains” scale horizontally while integrating directly with the messenger’s 800 M users.

TON relies on LiteClient/gRPC rather than native JSON-RPC, but public gateways translate common calls like getTransactions into JSON over HTTP. Responses carry TON’s unique Bag-of-Cells data structure, so SDKs perform TL-B encoding. WebSocket feeds stream shard-block proofs for real-time integrations.

TON requires specialized binaries and high IO; expect US $150-300 / month plus the hassle of LiteClient peers. Those numbers rise if you keep multiple shard archives. Using an RPC provider such as Chainstack is the most cost-effective shortcut.

Community TON Lite-Server proxies are free but unstable and require TL-B decoding hacks. Chainstack’s free tier ships 3 million robust TON calls out of the box.

Grab the TON HTTPS endpoint from Chainstack Console. Add it to your Tonkeeper connection settings or set it inside your SDK client to query the blockchain via Chainstack.

ADNL (Abstract Datagram Network Layer) is the low-level networking protocol used in TON to handle peer-to-peer communication. It defines how nodes in the TON network identify each other, exchange encrypted datagrams, and establish secure channels. Chainstack supports ADNL on Dedicated TON Nodes

TON uses ADNL because it is optimized for decentralized environments. Unlike traditional TCP/IP, ADNL is designed for fast, encrypted message delivery between dynamically changing peers. It also supports multiple overlay networks, which is critical for TON’s scalability and flexibility.

ADNL improves security by using public keys as node identifiers and establishing encrypted sessions for all communication. It boosts performance through lightweight datagrams and direct peer-to-peer messaging, which reduces latency compared to conventional client-server networking. Build secure TON app on Chainstack Dedicated Nodes with ADNL support.