Client
java-tron (FullNode)
tron
Install java-tron (FullNode) as a self-hosted TRON full node on your server. This guide covers the agent, network selection, setup, and sync.
java-tron (FullNode)
HTTP + gRPC via the Go proxy (wallet/getnowblock, getaccount, broadcasttransaction)
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.
mainnetnileshasta
Choose mainnet, nile, shasta in Toolkit, then follow these steps to provision and run a TRON full node.
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.