Dynamic sharding of TON delivers high throughput, but node setup requires expertise with TVM and ADNL. Clients often come to us with synchronization errors, disk space shortages, or misconfigured Lite Server. We deploy full, validator, and lite-server nodes turnkey, giving you independent access to the blockchain without public RPC delays.
When You Need Your Own TON Node
If your dApp processes latency-sensitive transactions, public RPC endpoints may be overloaded, offering up to 5-second delays. A custom full node provides direct blockchain access, while a validator node opens the path to staking and network governance.
How to Choose the Right Node Type?
A full node downloads and verifies all blocks, storing current state. This is sufficient for most tasks: data reading, transaction sending, monitoring. An archive node stores the full history—needed for historical data indexing. A lite node trusts other nodes, suitable for lightweight clients. A validator node requires stake (100,000 TON, approximately $150,000) and constant uptime. Full nodes synchronize 5x faster on NVMe than on SATA SSD.
System Requirements
| Node type | CPU | RAM | Disk | Network |
|---|---|---|---|---|
| Full node | 8+ cores | 16 GB | 500 GB NVMe SSD | 100 Mbps |
| Archive node | 16+ cores | 32–64 GB | 4+ TB NVMe | 1 Gbps |
| Validator | 16+ cores | 64 GB | 1 TB NVMe | 1 Gbps (stable) |
NVMe is mandatory—SATA SSD lags 10x in I/O, critical during synchronization. HDD is ruled out.
Time and Disk Cost Comparison
| Node type | Synchronization time | Disk usage | Setup complexity |
|---|---|---|---|
| Full node | 6–12 hours | 500 GB | Medium |
| Archive node | 2–5 days | 4+ TB | High |
| Validator | 6–12 hours + stake | 1 TB | High (elections) |
Step-by-Step Installation and Initial Setup
- Server preparation: Ubuntu 20.04/22.04, update packages.
- Download script:
wget https://raw.githubusercontent.com/ton-blockchain/mytonctrl/master/scripts/install.sh. - Run installation:
sudo bash install.sh -m full(or-m validatorfor validator). The script compiles TON from source (30–60 minutes). - Check status: run
mytonctrl, executestatusandgetmasterchaininfo.
Initial synchronization of a full node takes from a few hours to several days. Configuration files reside in /var/ton-work/db/. Important parameters: liteservers and validator.adnl_id.
How to Configure Lite Server for Applications?
To connect dApps to the node, add to config.json:
{ "liteservers": [ { "@type": "liteserver.desc", "id": { "@type": "pub.ed25519", "key": "YOUR_LITE_SERVER_PUBLIC_KEY" }, "port": 43678 } ] } Key generation: generate-random-id -m keys -n liteserver. Connection via JavaScript SDK:
import { LiteSingleEngine, LiteClient } from 'ton-lite-client'; const engine = new LiteSingleEngine({ host: `tcp://YOUR_SERVER_IP:43678`, publicKey: Buffer.from('YOUR_LITE_SERVER_PUBLIC_KEY', 'base64'), }); const client = new LiteClient({ engine }); const masterInfo = await client.getMasterchainInfo(); Typical Problems and Solutions
Common issues include out of disk space—TON writes data aggressively, so ensure at least 500 GB free before syncing. ADNL connectivity problems: open UDP port 30303 with sudo ufw allow 30303/udp. Compilation failures require cmake >= 3.16 and clang-14+ or gcc-10+. For validator downtime penalties: TON imposes a fine of 0.5 to 2% of stake per missed round (TON Whitepaper). To avoid, use a fault-tolerant architecture with redundancy and at least two servers. Bring the node online 3 days before elections.
Why Does a Validator Need Monitoring?
Additional steps in mytonctrl:
> new_key > add_validator_key KEY_HASH > send AMOUNT # minimum ~100k TON > participate_in_elections > setup_monitoring TON holds elections every ~36 hours. On success, the validator receives a reward; on errors, a penalty. Key alerts: node unsynchronized >5 minutes, missed >2 rounds, RAM >80%. Monitoring with SMS and Telegram notification is mandatory.
Deliverables
- Turnkey full/validator node deployment
- Lite Server configuration for your applications
- Monitoring and alert setup
- Parameter optimization for your hardware
- Access and maintenance documentation
- 30 days of support after launch
We deliver documentation with configuration parameters, server access, alert configuration, and 30 days of support. Full node deployment takes 1 day (installation + synchronization), validator with monitoring takes 2–3 days. Our team of certified TON engineers with proven track record in TON, Ethereum, and Solana has helped 10+ projects launch production nodes. Contact us for a project assessment—we'll prepare a quote and timeline. Order your TON node deployment—get a stable node without the headache. Running your own validator node can save over $1,000 per month compared to relying on public RPC services.