For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tron (TRX)

Tron on Ledger Enterprise: TRC-20 tokens, and the bandwidth and energy an Account needs to transact.

How Tron differs

Tron uses an Account model like Ethereum, but it does not charge a fee in the ordinary sense. An Account earns two renewable resources, bandwidth and energy, and spends those first. TRX is burned only when the resources run short.

A second difference concerns new addresses. A transfer to an address that does not yet exist creates it. That creation is paid for by burning TRX.

You cannot send TRX to the Account's own address. The interface and the API both refuse it. A TRC-20 token transfer to the Account's own address is allowed.

For the protocol itself, see the Tron developer documentation.

Token coverage

Ledger Enterprise supports TRX and TRC-20 tokens.

A token Account can exist only for a token in Ledger's asset catalog. See Networks and tokens in your Workspace.

Recipient Account activation

A transfer to a Tron address that is not active yet burns a one-time activation fee. The fee is 1 TRX, plus 0.1 TRX when the sending Account does not have enough bandwidth. The total is at most 1.1 TRX.

Note: These amounts were checked against the Tron documentation on accounts on 7 October 2026. The network can change them.

Bandwidth and energy

Most networks charge a fee in their own asset. Tron uses two resources instead, and your Account page shows both:

Resource
What it pays for

Bandwidth

The size of a transaction on the network

Energy

The computation a smart contract needs, including token transfers

Bandwidth and Energy are earned by locking up TRX. The locking feature is not available on Ledger Enterprise. Renting Bandwidth and Energy is not supported either.

When an Account has enough of a resource, the transaction fee is paid in bandwidth and energy, and costs no TRX. When it does not, the network takes TRX instead.

Note: This is why two identical Tron transfers can show different fees. The first may be covered by available bandwidth. The second may not.

Check both figures on the Account page before a large batch of transfers. An Account that has run out of energy pays TRX for every token transfer.

TRC-20 tokens

Tron supports TRC-20 tokens.

A token Account attaches to a parent Tron Account. The parent holds the TRX and covers the resources for every token Account beneath it. This is the standard parent and token Account model described in Finding Accounts and balances.

Token transfers use energy, so they cost more than a plain TRX transfer.

Important: If a token transfer fails because of fees, add TRX to the parent Account, not to the token Account.

Last updated