> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mpcvault.com/llms.txt
> Use this file to discover all available pages before exploring further.

# TRON

> Transfer TRX, TRC-10 and TRC-20 tokens with the MPCVault API.

Examples use [API client signing](https://docs.mpcvault.com/api-reference/overview.md#preparation).

## Signing request types

| Payload | Use |
| - | - |
| [`tronSendNative`](https://docs.mpcvault.com/api-reference/rest/create-signing-request) | Transfer TRX. |
| [`tronSendTrc10`](https://docs.mpcvault.com/api-reference/rest/create-signing-request) | Transfer TRC-10 tokens. |
| [`tronSendTrc20`](https://docs.mpcvault.com/api-reference/rest/create-signing-request) | Transfer TRC-20 tokens. |

To sign transactions you build yourself or messages you format yourself, use [raw signing](https://docs.mpcvault.com/api-reference/overview.md#raw-signing).

## Wallet

[Create a wallet](https://docs.mpcvault.com/api-reference/rest/create-wallet.md) with `networkType: "NETWORK_TYPE_TRON"`. [Activate the address](https://developers.tron.network/docs/account) by receiving TRX or a TRC-10 token from an existing account; receiving a TRC-20 token does not activate it.

Fund it with TRX for fees and the asset being sent. Transactions consume [Bandwidth](https://developers.tron.network/docs/bandwidth-and-energy); TRC-20 transfers also consume Energy. TRX pays when available resources are insufficient.

## Send TRX

This TRON Mainnet example sends `1 TRX`.

```bash theme={null}
curl -X POST https://api.mpcvault.com/v1/createSigningRequest \
  -H "Content-Type: application/json" \
  -H "x-mtoken: <API_TOKEN>" \
  -d '{
    "vaultUuid": "<VAULT_UUID>",
    "callbackClientSignerPublicKey": "<CLIENT_SIGNER_OPENSSH_PUBLIC_KEY>",
    "broadcastTx": true,
    "tronSendNative": {
      "from": "<YOUR_TRON_ADDRESS>",
      "to": "<RECIPIENT_TRON_ADDRESS>",
      "value": "1000000"
    }
  }'
```

`value` is an integer string in sun: `1 TRX = 1,000,000 sun`. Use base58check addresses starting with `T`; `from` and `to` are different addresses.

## Send BTTOLD (TRC-10)

Replace `tronSendNative` with this payload in the same request:

```json theme={null}
{
  "tronSendTrc10": {
    "from": "<YOUR_TRON_ADDRESS>",
    "to": "<RECIPIENT_TRON_ADDRESS>",
    "assetName": "1002000",
    "amount": "1000000"
  }
}
```

This example sends `1 BTTOLD`, the legacy BitTorrent TRC-10 token (`assetName: "1002000"`, six decimals). The newer BTT token uses TRC-20. See [BitTorrent's migration notice](https://bttc.zendesk.com/hc/en-us/articles/4409343014937-Launch-of-BTTC-Mainnet-and-BTT-Redenomination-Plan).

## Send USDT (TRC-20)

Replace `tronSendNative` with this payload in the same request:

```json theme={null}
{
  "tronSendTrc20": {
    "from": "<YOUR_TRON_ADDRESS>",
    "to": "<RECIPIENT_TRON_ADDRESS>",
    "contractAddress": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t",
    "amount": "1000000"
  }
}
```

This example sends `1 USDT` on TRON Mainnet (six decimals). `contractAddress` is [Tether's TRON Mainnet USDT contract](https://tether.to/en/supported-protocols/). Optional `feeLimit` is a positive integer string in sun that limits contract execution fees; omit it to use MPCVault's default.

## Sign and track

[Sign the request](https://docs.mpcvault.com/api-reference/overview.md#sign-the-request). MPCVault broadcasts by default; `txHash` is the TRON transaction ID (`txID`).

For TRX and TRC-10, query the [solidified transaction body](https://developers.tron.network/reference/gettransactionbyid). Match the recipient and amount, plus the asset ID for TRC-10; check `ret[0].contractRet: "SUCCESS"` when present.

For USDT and other TRC-20 tokens, query the solidified receipt:

```bash theme={null}
curl -X POST "<TRON_MAINNET_NODE_URL>/walletsolidity/gettransactioninfobyid" \
  -H "Content-Type: application/json" \
  -d '{"value":"<TX_HASH>"}'
```

Check `receipt.result: "SUCCESS"`, no top-level `result: "FAILED"`, and a `Transfer` event matching the token contract, sender, recipient and amount.

An empty response is not a failure result; keep tracking the original `txID`. See [TRON confirmation semantics](https://developers.tron.network/docs/confirmation-semantics).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.