RpcNode Toolkit

Home/Networks/Toncoin

ton

Toncoin full node

Run a Toncoin full node with mytonctrl — dump bootstrap, then live catch-up. One env per host.

Install ToolkitOfficial docs

Client

mytonctrl / validator + TON RPC

RPC

TON ADNL / HTTP API after bootstrap

History

Full dump then catch-up. One environment per host. OOM is not “at tip”.

TON is one_env_per_host in Toolkit. The agent installs mytonctrl and the catalog pin, then tracks dump percent until seqno > 0.

After the dump, sync is out-of-sync / lag-closed — an OOM kill is not treated as a healthy tip. Mainnet and testnet are the catalog envs.

Environments

mainnettestnet

Install

  1. On Ubuntu 24.04 LTS:
    bash
    curl -fsSL "https://toolkit.rpcnode.dev/install/agent.sh" | sudo bash
    Supported and recommended: Ubuntu 24.04 LTS (amd64 or arm64). Other operating systems have not been tested.
  2. Panel → Add server (Agent URL + token) → Add node → Toncoin → mainnet.
  3. Confirm ports, choose install options if this chain has them, install mytonctrl / validator + TON RPC, snapshot if required, start. Watch sync on the node page.

Operate from the panel

After the node is up you manage it in the same UI — Node Config (edit the live files and apply), client updates, restart, logs, public RPC. You do not need SSH to change conf. Install-time choices (snapshot flavor, history window, disk layout) are stored on that node.

FAQ

How do I run a Toncoin full node?
Install the host agent, add the server, then Add node → Toncoin. Toolkit provisions mytonctrl / validator + TON RPC.
Can I change the Toncoin config later?
Yes. Node page → Node Config. Edit and apply; restart from the same page. A different snapshot or history flavor is an Install choice — changing it later usually means wipe and Add node again.
Pruned or light?
Full dump then catch-up. One environment per host. OOM is not “at tip”.
Catalog
/clients/ton/ · catalog.json

Other networks