> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/reference/networks/tron.md).
# 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.
For the protocol itself, see the [Tron developer documentation](https://developers.tron.network/).
## Token coverage
Ledger Enterprise supports **TRX and TRC-20 tokens**.
## Recipient Account activation
Sending to a new/inactive Tron address burns a one-time \~1.1 TRX activation fee.
## 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 & 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**](/help-center-v2/guides/accounts/finding-accounts-and-balances.md).
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.
## Related
* [**Sending assets**](/help-center-v2/guides/transactions/sending-assets.md)
* [**Finding Accounts and balances**](/help-center-v2/guides/accounts/finding-accounts-and-balances.md)
* [**Networks**](/help-center-v2/reference/networks.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.enterprise.ledger.com/help-center-v2/reference/networks/tron.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.