Guides
  1. Getting Started

Getting testnet tokens

Request free TRX and TRC-20 test tokens through the Shasta and Nile faucets or the TronFAQBot on Telegram and Discord.

📘

Prerequisites

This guide walks through getting testnet tokens (TRX and TRC-20 tokens) on the TRON Shasta and Nile testnets. These free tokens let you test smart contracts and DApps at zero cost.

Methods for getting testnet tokens

Faucet websites

The most direct way. Steps:

  1. Prepare your wallet address. In your TRON wallet (such as TronLink), switch to the Shasta or Nile testnet and copy your wallet address. To create a new wallet:

  2. Open a faucet website. In your browser:

  3. Request tokens. Paste your wallet address into the input field, complete the reCAPTCHA, and click Obtain.

  4. Read the status response. The faucet replies with a popup. The three common responses:

    • Success — "Successful acquisition of test tokens." The faucet broadcasts the transfer; allow a few seconds for confirmation.
    • Already claimed — "You have acquired test tokens today and cannot be retrieved repeatedly!" You hit the 24-hour cooldown for this token. Wait for it to reset.
    • Invalid address — "Failed to get test tokens, please enter the address in the correct format!" The address is not a valid TRON Base58 address. Double-check what you pasted.

Important notes

  • Daily limits. Each wallet and IP address can request once per 24 hours per token. The amount per request varies; check the faucet page for current values.
  • Verify URLs. Faucet domains can change over time. Always reach the faucet from official documentation or a verified developer community — never from a forwarded link.

TronFAQBot on Telegram and Discord

You can also request testnet tokens through the TronFAQBot in TRON developer chat groups.

  1. Join a developer community. TronFAQBot lives in the following groups:

  2. List bot commands. In the group chat, send !help:

    TronFAQBot Help:

The following commands start with "!" (without quotes), for example: !help

    !help shows this.
    !ping shows the latency.
    !check ADDR checks if the given ADDR is a valid TRON address.
    !balance shows the balances of the faucet.
    !balance ADDR shows the balances of the given ADDR (TRX, USDT, USDC, USDD).

    !nile ADDR sends 5000 nile TRX to ADDR (max 5000 in 24 hours).
    !nile_usdt ADDR sends 5000 USDT to ADDR (max 5000 in 24 hours).
    !nile_usdd ADDR sends 5000 USDD to ADDR (max 5000 in 24 hours).
    !nile_usdc ADDR sends 5000 USDC to ADDR (max 5000 in 24 hours).

    !shasta ADDR sends 5000 shasta TRX to ADDR (max 5000 in 24 hours).
    !shasta_usdt ADDR sends 5000 USDT to ADDR (max 5000 in 24 hours).
    !shasta_usdd ADDR sends 5000 USDD to ADDR (max 5000 in 24 hours).
    !shasta_usdc ADDR sends 5000 USDC to ADDR (max 5000 in 24 hours).

  3. Request tokens. Send a command in the format !<command> <your_wallet_address>. For example:

    # Request 5000 TRX on Nile testnet
!nile TA5wVDny...1k8PvfYZ

# Request 5000 USDT on Shasta testnet
!shasta_usdt TA5wVDny...1k8PvfYZ

    TronFAQBot replies with a confirmation message such as <username> will receive 5000 TRX (Shasta) soon. Thank you! Verify the transaction by checking your wallet balance.

Security best practices

Whatever method you use, follow these principles:

  • Use a dedicated test wallet. Create a fresh wallet for testing only. Never import a Mainnet private key or mnemonic phrase into a test environment — testnet tooling is sometimes less hardened than Mainnet, and a leaked key on Mainnet would mean real losses.
  • Treat testnet keys carefully too. Even though testnet tokens have no value, careless habits with testnet keys carry into Mainnet behavior. Practice good key hygiene from day one.
  • Use testnet tokens for testing only. Testnet tokens have no financial value and should never be traded.
  • Verify transactions on-chain. Use the testnet TronScan to confirm balances, transaction details, and contract behavior:

Need more testnet tokens?

The 5,000-per-token daily limit covers most testing if you use what you already have efficiently. Before assuming you need a larger allocation, work through the strategies below — they are repeatable, free, and improve your test infrastructure rather than depending on a one-off handout.

Use the precision you already have

Every TRC token has at least 6 decimal places (TRX, USDT, and USDC all use 6; USDD uses 18). 5,000 tokens at 6 decimals is 5,000,000,000 atomic units — five billion. Most "I ran out of tokens" stories trace back to using whole-unit amounts in test cases when fractional amounts would have worked just as well.

Reduce per-test amounts: 0.001 TRX is still 1,000 sun, plenty for exercising a transfer flow. Audit your test fixtures and replace transfer(1000) style calls with transfer(0.001) where the test logic does not require a specific magnitude.

Recycle TRC-20 tokens after each test run

TRX is consumed when it burns to pay Bandwidth or Energy. TRC-20 tokens — including the USDT, USDC, and USDD on Nile and Shasta — only move between addresses; they do not disappear unless the contract has an explicit burn function and your test calls it.

Build a teardown step into your test harness: at the end of a test, sweep all test-output addresses back to a treasury address you control. The same 5,000 USDT can support thousands of test cycles when reused this way.

Stake TRX to reduce per-transaction burn

Staking TRX on testnet grants the address Bandwidth and Energy, which regenerate over time. Transactions covered by these staked resources do not burn TRX; only the overflow burns.

A small stake on a test address quickly pays for itself in extended test runs. Stake 2.0 works the same on Nile and Shasta as on Mainnet — see Stake and delegate resources for the recipe, and Resource model for the math behind Bandwidth and Energy.

Deploy your own test token

For custom amounts, custom token economics, or supply that does not fit the faucet's allocation, deploy a TRC-20 (or TRC-10 / TRC-721) of your own on testnet. You choose the total supply at deployment and you own all of it from minute one.

See Token standards overview for the standards and Deploy a TRC-20 token for a copy-paste deployment recipe.

Estimate Energy before broadcasting

Failed contract calls still burn Energy — and so burn TRX. Use triggerconstantcontract or estimateenergy to predict Energy consumption before broadcasting a real transaction. Catching a misconfigured fee_limit or a contract revert before spending costs nothing; doing it after is paid in burned TRX.

For the full debugging endpoint catalog, see Errors and debugging.

Run a private testnet

For long-term, high-volume, or fully controlled testing — running thousands of transactions per minute, simulating a market, testing chain forks, or doing chaos-engineering experiments — deploy your own private TRON network. You set the genesis allocation and every chain parameter, so token supply is no constraint.

See Building a TRON private chain.

Related resources

Updated 13 days ago