Skip to main content
A Tron node runs a single java-tron process. On the first deploy, the node seeds from a recent community snapshot to cut sync time. To deploy one, open Deploy Node, pick an executor that supports Tron, then choose the network, node type, client (java-tron), and version. The wizard offers exactly what your executor declares.

​
Networks and resources

Tron runs on mainnet. Defaults are pre-filled in the deploy wizard per node type; lower them with caution.

​
Clients

4.8.1 → 4.8.1.1 is a blessed in-place upgrade step marked security-urgent — see Update a node’s version.

​
Ports

Ports are managed for you and aren’t user-overridable.

​
Node types

Tron offers Full and Lite, and the choice is really a choice of snapshot:
  • Full — seeds from the full compressed snapshot and keeps deep block and transaction history. Heaviest on disk.
  • Lite — seeds from the lite snapshot, so the node starts at a recent block instead of carrying history back toward genesis. Roughly a quarter of the disk on mainnet, and it serves current chain state and transactions the same way.
Both types serve the same APIs and both bootstrap from a snapshot rather than syncing from genesis (see Snapshot bootstrap). A Lite node answers history queries for the blocks it actually holds and returns empty for the range it doesn’t — including for transactions you broadcast through it, so the usual build → sign → broadcast → poll-the-receipt flow works on either type.

​
Config overrides

Tron config keys are set the same way as on any node, at deploy time — see Edit a running node. Settings that control networking, ports, and the data directory are managed and rejected if you try to set them. The keys you can override are: The rest of the node config stays intact; your overrides are merged on top.

​
Snapshot bootstrap

On the first deploy, the node seeds from a recent compressed snapshot on a pinned mirror instead of syncing block-by-block from genesis, which cuts sync time sharply. The archive it pulls depends on the node type you chose. If the data directory already holds a synced database, the snapshot step is skipped.

​
Metrics

Block height, peer count, and last-block age are surfaced in the node view — see Node monitoring. java-tron exposes no sync-progress ratio, so Novacula judges sync from head freshness instead: while the node’s latest block is older than the freshness threshold, it reports Syncing, and it flips to Running only once the head catches up to the network tip.

​
Where to next