Node

TL;DR – A TON node is a server that stores blockchain data, validates transactions, and creates new blocks. Nodes come in several types, each with specific roles and hardware requirements, enabling the network’s decentralization and scalability.

Overview of node responsibilities#

Data storage – Nodes keep a copy of all transactions, blocks, and the current state of the network.
Transaction processing – Incoming transactions are checked for validity before being added to a block.
Block creation – Nodes participate in forming new blocks and signing them.
Work allocation – Nodes distribute processing tasks among themselves to improve throughput.
Consensus participation – Nodes run the consensus algorithm to ensure a single, agreed‑upon network state.
Error detection – Nodes identify and help correct inconsistencies in their local copies of the blockchain.
Support for decentralization – By operating without a central authority, nodes keep the network resilient.
Scalability – Adding more nodes increases the network’s capacity to handle transactions.
Privacy – Nodes employ encryption and anonymity mechanisms to protect user data.

Types of TON nodes#

Full nodes

Full nodes store the complete blockchain ledger and are responsible for creating new blocks. They communicate via a peer‑to‑peer network to stay synchronized.

Validator nodes

Validator nodes verify transactions, create and validate new blocks, and require staking of TON tokens. They are run by validator pools or private operators.

Liteserver nodes

Liteserver nodes hold only the portion of the blockchain needed for their specific services (e.g., TON APIs). They rely on full nodes for full verification and are optimized for fast, lightweight operation.

Archive nodes

Archive nodes retain the entire history of the blockchain from genesis onward. They provide the only reliable source for historical transaction queries and demand substantial storage capacity.

Functional nodes

Proxy nodes – Offer Web3 access and anonymity for users.
TON Storage providers – Serve files and other content over the network.

How to become a node operator#

Prepare hardware that meets the minimum specifications:
Archive nodes additionally require 8 TB of persistent storage with ZFS compression on at least 4 TB.
Follow the official setup guide from the TON Foundation, which varies by node type.
Deploy MyTonCtrl, the CLI tool for managing TON nodes.