Home/Networks/TRON

tron

TRON full node

Install a java-tron full node for TRON mainnet, Nile, or Shasta — snapshot, sync, and public RPC from the Toolkit panel.

Client

java-tron (FullNode)

RPC

HTTP + gRPC via the Go proxy (wallet/getnowblock, getaccount, broadcasttransaction)

History

Full ledger. Snapshot is a first-class setup step; tip sync is not enough to call the node Synced.

TRON full nodes are java-tron FullNode processes, not a light API. Toolkit apt-installs Java, pulls the catalog jar and conf, and treats the official snapshot as a required setup step when the network ships one.

On mainnet Install you pick the official snapshot flavor: standard (no historical internal txs), internal transactions, or historical TRX balances — each is a different mirror and a matching java-tron conf. Nile and Shasta have a single official path. After start, Node Config edits the live HOCON.

Mainnet, Nile, and Shasta can share one host on separate ports. Clients talk to the Go proxy, not raw FullNode HTTP. Synced means snapshot plus a live tip — not a stale getnowblock.

Environments

mainnetnileshasta

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 → TRONmainnet.
  3. Confirm ports, choose install options if this chain has them, install java-tron (FullNode), 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 TRON full node?
Install the host agent, add the server, then Add node → TRON. Toolkit provisions java-tron (FullNode).
Can I change the TRON 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 ledger. Snapshot is a first-class setup step; tip sync is not enough to call the node Synced.
Catalog
/clients/tron/ · catalog.json

Other networks