> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/cryptos/tron.md).

# Tron

Tron in Cake Wallet: one T address, BIP39 seed, how bandwidth and energy fees burn TRX, TRC-20 tokens like USDT, and TronGrid transaction history.

Official Website: [tron.network](https://tron.network/)

Tron `(TRX)` is a blockchain-based digital platform aimed at decentralizing the entertainment industry by allowing content creators to publish, store, and own data in a decentralized ecosystem. Founded by Justin Sun in 2017, Tron leverages its own cryptocurrency, TRX, for transactions within its ecosystem. The platform seeks to empower creators by cutting out middlemen, ensuring fair distribution of earnings through smart contracts, and providing high scalability and throughput for content sharing and digital asset transfers.

## Addresses

In Cake Wallet's Tron wallet, there is only one address per wallet, which is standard for the Tron ecosystem. Keep in mind that this will have lesser privacy compared to some other assets, where new addresses are automatically generated.

Your Tron address will start with `T` followed by a series of alphanumeric characters.

![Tron receive screen in Cake Wallet](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/tron_01_receive.png)

## Seed Format

A 12-word BIP39 seed is generated for Tron wallets by default. Under `Advanced Settings` on the wallet creation screen you can choose a **24-word** BIP39 seed instead. The same screen has an optional seed passphrase. Most people should leave it empty: a passphrase creates a completely different wallet, and if you forget it, your seed alone can't restore your funds. When creating or restoring a wallet, you can use the seed phrase or the private key.

## Fees

Tron handles fees differently from most other networks. Every transaction consumes network resources called *bandwidth* and *energy*. If your account doesn't hold enough of these resources (most wallets don't), the network automatically burns a small amount of TRX to cover them instead.

In practice this means:

* You always need some TRX in your wallet to pay fees — even when you're only sending TRC-20 tokens like USDT.
* Sending TRC-20 tokens consumes much more energy than sending TRX itself, so token transfers usually cost noticeably more than plain TRX transfers.
* Sending tokens to an address that has never been used before costs extra, because the network charges for activating a new account.

If a token transfer fails or won't send, the most common cause is not having enough TRX to cover the fee. Top up a small amount of TRX and try again.

If your address already has energy — staked, delegated to you, or rented from an energy service outside Cake Wallet — token sends use it first, and the estimated fee only covers the part your energy doesn't. Cake Wallet doesn't rent or buy energy for you.

Because the network sets the cost, Cake Wallet has **no Slow / Medium / Fast fee selector for Tron**.

{% hint style="info" %}
A `Fees` row does still appear under `Advanced Settings` on the send screen, showing the estimated fee. Tapping that row does nothing on Tron — there is no fee picker to open. This is expected, not a bug.
{% endhint %}

## WalletConnect

Tron wallets can connect to dApps with WalletConnect: open `Settings` → `Tron Settings` → `WalletConnect`. Only Tron mainnet is supported, and the dApp broadcasts the transactions you sign. See [WalletConnect](https://docs.cakewallet.com/features/basic/walletconnect).

## Tokens

Cake Wallet's Tron wallet can store TRC-20 tokens (Tron's token standard) in addition to TRX. Some common tokens such as USDT, USDC, DOGE, and WBTC are displayed by default. To show other tokens, open the `Assets` tab on your home screen, tap the `Tokens` button, and enable them.

![Managing TRC-20 tokens for a Tron wallet in Cake Wallet](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/tron_02_tokens_hl.png)

Other token types, as well as NFTs, are not currently supported; expanded support is planned for the future.

### Adding a new token

You can add a new TRC-20 token from the same `Tokens` screen: search for your desired token, then tap to enable it.

If the token does not appear, then you can add the token by contract address. Paste the address of the custom token you wish to add, then click the `+` button.

![Adding a custom TRC-20 token by contract address in Cake Wallet](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/tron_03_add-token.png)

## Transaction history

Transaction history is populated using the TronGrid API. You can enable or disable this API lookup with the `TronGrid history` toggle under `Settings` → `Connections`. Tron is the only non-EVM chain in Cake Wallet with a history-API toggle of its own.

Only TRC-20 token transfers appear as token movements in History. Token approvals and other smart-contract interactions show as TRX transactions to the contract, with the TRX actually sent (often 0) plus the fee. If TronGrid is slow or returns something the app can't read, your balance still syncs and History catches up on the next refresh.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cakewallet.com/cryptos/tron.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
