TON Full Node: Complete Guide

What is a TON full node?

A TON full node keeps a verified view of chain state and serves the network’s native RPC surface used by wallets, indexers, and backend services.

RpcNode lists TON in the public network catalog and targets managed Full Node RPC so you can integrate native token flows without becoming an infrastructure team first.

Why TON full nodes matter

Every wallet balance, payment confirmation, and contract read ultimately depends on nodes that agree on TON state. Public endpoints rate-limit and flake; your product’s reliability tracks the quality of the full nodes behind your RPC URL.

TON in the RpcNode catalog: TON.

• Native asset: native token
• Environments:
• API family: TON HTTP API / ADNL
• Listed in the RpcNode network catalog

When to run your own TON node

Self-hosting a TON full node makes sense when you need custom indexing, ultra-low latency next to your app, or compliance constraints that forbid third-party RPC. For most product teams, managed Full Node RPC is faster to ship and cheaper to operate.

• Building wallets, payments, or address watchers that need reliable TON reads and writes
• Avoiding multi-terabyte disks, peer tuning, and 24/7 pager duty for chain upgrades
• Preferring HTTPS JSON-RPC with allowlists, keys, and usage metering
• Evaluating TON before dedicating hardware — start on RpcNode, or self-host with Toolkit in a few clicks

TON full node server requirements

TON full node server requirements vary with mytonctrl / validator vs liteserver-oriented setups. For API traffic, size CPU/RAM generously and put databases on NVMe.

Looking up "TON server requirements", "TON hardware requirements", or "TON minimum specs"? Use the checklist below as the planning baseline for a self-hosted full node.

TON is in the RpcNode catalog. Until you need custom indexing or on-prem constraints, prefer managed Full Node RPC when available rather than buying this class of server “just in case”.

• CPU: 8+ cores
• RAM: 32 GB+
• Disk: 1+ TB SSD/NVMe
• Bandwidth: 1 Gbps recommended
• OS: Ubuntu 22.04/24.04 LTS

Install a TON full node in a few clicks

TON is in the free RpcNode Toolkit catalog (mainnet, testnet). Skip the manual binary hunt: the self-hosted panel walks Add server → Add node → the node page.

On Linux (amd64/arm64) you install the host agent once, register the server, pick TON and an environment, then the node page handles ports, install, snapshot when the chain supports it, sync, logs, and the public RPC endpoint.

1. Install the host agent on the Linux server (curl one-liner from rpcnode.dev).
2. Add server: paste IP and AGENT_API_TOKEN, Check connection, then add.
3. Add node: network TON → environment (mainnet, testnet) → that server.
4. Open the node page — install, sync %, logs, restart, client update, fullnode RPC.

Self-host TON with Toolkit

How to run a TON full node

How to run a TON full node: follow TON docs / mytonctrl for the node role you need, then place HTTP API or liteserver access behind controlled networking.

TON is in the RpcNode catalog. Until you need custom indexing or on-prem constraints, prefer managed Full Node RPC when available rather than buying this class of server “just in case”.

1. Provision Ubuntu 24.04 LTS (or the OS your client documents) on bare metal or a dedicated VM. Create a system user such as `nodeop` — do not run the node as root.
2. Attach fast SSD/NVMe for TON databases. Mount it away from the root filesystem and give ownership to the operator user.
3. Apply OS hygiene: unattended-upgrades or a patch cadence, fail2ban/SSH keys, and raise file-descriptor limits if the client docs require it.
4. Install the supported node tooling; sync; expose APIs only via allowlists.
5. Verify with the project’s recommended status tools before production traffic.

• Separate validator operation from public API exposure

Using TON RPC without self-hosting

RpcNode exposes managed TON HTTP API / ADNL for TON. Create an endpoint in the cabinet, restrict IPs if needed, and call the same methods your stack already uses.

Catalog environments for TON: . Create an endpoint in the RpcNode cabinet for the environment you need, or use this guide to plan a self-hosted deployment.

Typical methods teams start with: chain tip, account/balance reads, transaction broadcast.

Self-hosting vs managed Full Node RPC

Self-hosting gives maximum control and can reduce per-request cost at huge scale, but you own upgrades, peers, disk growth, and incident response. RpcNode Toolkit cuts the install to a few clicks (agent → Add server → Add node → node page) while you still run the hardware.

Managed RpcNode Full Node RPC trades that ops burden for a stable HTTPS endpoint, usage visibility, and the same method surface your SDK already speaks. If you are comparing providers, also see RpcNode’s comparison page.

TON integration checklist

Use this short checklist when wiring TON into production.

• Pick the correct environment () — never mix testnet keys with mainnet funds
• Store RPC URLs and keys in secrets management; rotate on staff changes
• Add IP allowlisting for server-side backends
• Alert on tip lag / getHealth (or equivalent) failures
• Load-test eth_getLogs / getProgramAccounts-style heavy calls before launch
• Decide full vs archive needs early — RpcNode is Full Node oriented
• Confirm TON server requirements (CPU/RAM/disk) before self-hosting
• Or install with RpcNode Toolkit in a few clicks — free self-hosted panel

TON full node FAQ