Tron

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, client (java-tron), and version. The wizard offers exactly what your executor declares.

​

Networks and resources

nile is Tron’s public testnet. Defaults are pre-filled in the deploy wizard; lower them with caution.

​

Ports

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

​

Node type

Tron offers a single Full node type. It keeps complete block and transaction history and, on first deploy, seeds from a compressed snapshot rather than syncing from genesis (see Snapshot bootstrap).

​

Config overrides

Tron config keys are edited the same way as any node — see Edit configuration. 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. 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

• Deploy a node
• Edit configuration
• Provision on bare metal · Provision on Kubernetes