diff --git a/docs.json b/docs.json index d18c8123d..d0bf4feae 100644 --- a/docs.json +++ b/docs.json @@ -40,6 +40,7 @@ "navigation": { "pages": [ "start-here", + "what-is-a-node", "get-support", "from-ethereum", "more-tutorials", diff --git a/resources/images/nodes/node-flow.svg b/resources/images/nodes/node-flow.svg new file mode 100644 index 000000000..b54d7eb66 --- /dev/null +++ b/resources/images/nodes/node-flow.svg @@ -0,0 +1,44 @@ + + + + + + + + + + + + + + + + + + User / Wallet + DApp + + + + API provider + Liteserver (gateway) + + + + TON nodes + (full nodes) + + + + Validators + (subset) + + diff --git a/what-is-a-node.mdx b/what-is-a-node.mdx new file mode 100644 index 000000000..f993a1f61 --- /dev/null +++ b/what-is-a-node.mdx @@ -0,0 +1,52 @@ +--- +title: "What is a node?" +description: "Overview of TON nodes, validator roles, and how apps connect to the network." +--- + +import { Image } from "/snippets/image.jsx"; + +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 + +- **Full node** — stores the latest state and propagates blocks and messages. See [Node roles and modes](/ecosystem/node/overview). +- **Archive node** — a full node that keeps the entire history for analytics and explorers. See [Node roles and modes](/ecosystem/node/overview). +- **Validator node** — produces blocks and participates in consensus. See [Running a validator](/ecosystem/node/run-validator). +- **Liteserver** — a mode that exposes a gateway for lite clients and APIs. See [Interacting with TON nodes](/ecosystem/node/overview#interacting-with-ton-nodes). + +## 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](/ecosystem/api/overview) 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. + +## 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. + +- [Set up a node with MyTonCtrl](/ecosystem/node/setup-mytonctrl) +- [Set up a local network with MyLocalTon](/ecosystem/node/setup-mylocalton) + +## See also + +- [Node roles and modes](/ecosystem/node/overview) +- [Running a validator](/ecosystem/node/run-validator) +- [Liteserver mode](/ecosystem/node/overview#interacting-with-ton-nodes)