Skip to main content
A node is a server running TON blockchain software. It stores the chain state, verifies blocks and transactions, and propagates new data to other nodes and clients. This matters when deciding whether to rely on a public API or run infrastructure, and when tracing how a wallet action becomes an on-chain transaction.

​
What a node does

A full node keeps the latest blockchain state and relays blocks and messages across the peer-to-peer network. A validator is a full node that participates in consensus and produces blocks. Many full nodes also expose a liteserver endpoint so wallets and apps can query data or submit messages without running a full node themselves. TON also has lite clients. They do not store chain state locally. Instead, they request the data they need from liteserver-enabled full nodes.

​
Node types and roles

​
Who runs nodes

  • Validators — stake Toncoin, participate in consensus, and produce blocks.
  • Infrastructure providers — run full nodes and liteservers to back APIs.
  • Explorers and indexers — run archive nodes to serve historical data.
  • Community operators — add connectivity and redundancy to the network.

​
How apps reach the network

Wallets and dApps act as lite clients: they do not keep chain state locally and instead connect to an API provider or a liteserver gateway. The gateway forwards requests to full nodes. Validators are the subset of nodes that finalize new blocks, and the results propagate back through the network. Flow from a user wallet or dApp through an API or liteserver gateway to TON full nodes and validators.Flow from a user wallet or dApp through an API or liteserver gateway to TON full nodes and validators.

​
Run your own node (optional)

Use public APIs for prototypes and light workloads. Full nodes typically back apps that require stricter uptime targets or direct access to the network.

​
See also