A wallet whose first activator is a known testnet faucet is by definition a developer test wallet. A wallet that received the 2019 BTT airdrop while inactive was activated by it — TRC-10 transfers can do that on TRON. A wallet that received post-December-2021 BTT (TRC-20) cannot have been activated by that transfer. A wallet that holds SUN tokens has a signed transaction in its history confirming intent; a wallet that holds BTT, JST, WIN, or APENFT may have received the token passively, with no signed transaction to confirm anything.
These distinctions matter because the protocol-level activation mechanics (/learn/account-activation/ covers them in full) interact in specific ways with each kind of distribution program. An investigator who treats every airdrop arrival the same way will misread half of them. This article catalogs the deployed faucet and airdrop infrastructure on TRON and the on-chain signatures each one leaves.
Testnet faucets — Nile and Shasta
TRON operates two official testnets — Nile and Shasta — each with its own faucet. Per the TRON developer hub, both faucets dispense up to 5,000 TRX per wallet per 24 hours via a reCAPTCHA-gated web form, with no signup or social verification. The same per-request cap applies to testnet USDT, USDD, and USDC on both networks.
| Testnet | Faucet URL | Per-request cap | Code generally |
|---|---|---|---|
| Nile | https://nileex.io/join/getJoinPage | 5,000 testnet TRX / 24h | Ahead of mainnet (used to test new features) |
| Shasta | https://shasta.tronex.io | 5,000 testnet TRX / 24h | Parameters consistent with mainnet |
TRON also operates an official TronFAQBot on the project’s Telegram and Discord channels that dispenses testnet TRX, USDT, USDC, and USDD via chat commands (!nile <address>, !shasta_usdt <address>, and so on), subject to similar rate-limiting. Because the bot signs and broadcasts the funding transactions, its dispensing wallets will appear as the first activator for any previously inactive testnet address that requests funds via the bot.
Mainnet TRX faucets do not exist as official infrastructure. The TRON developer documentation publishes only the two testnet faucets. Third-party “free mainnet TRX” sites (Freetron.in, Free-Tron.com, Tronpick.io, FireFaucet, and similar) operate independently as advertising-driven microfaucets. None has a primary-source-citable payout history; their on-chain behavior should be treated as unaffiliated with TRON DAO. Investigators encountering a mainnet wallet whose first activator is a microfaucet address are looking at an ad-incentivized faucet user, not someone who interacted with TRON’s official infrastructure.
BTT — February 2019, passive, TRC-10
The BTT airdrop was the first major TRX-holder distribution on TRON. BitTorrent Foundation announced the program in early 2019 and executed the first airdrop on February 11, 2019, with a snapshot at TRON block height 6,600,000. The initial distribution was 10,890,000,000 BTT (~1% of the 1 trillion total supply), at a ratio of 0.1097681177 BTT per TRX.
Two structural details matter for attribution.
First — distribution was passive. Per BitTorrent’s own announcement: “Airdrops will be automatically distributed to the TRON (TRX) holders, regardless of whether TRX are frozen. If you control the secret key of your TRX, you don’t need to do anything to receive BTT airdrop.” Recipients did not sign a claim transaction. Their on-chain history shows BTT arriving as an inbound TRC-10 transfer with no corresponding outbound to any airdrop contract. No signature, no proof of intent.
Second — the original BTT was a TRC-10 token (token ID 1002000), and TRC-10 transfers can activate inactive TRON accounts. A wallet that had been generated but never activated when the February 2019 snapshot was taken would have been activated by the BTT airdrop transfer itself. This is the only token-distribution event on TRON that produces this exact attribution signal.
On December 12, 2021, BTT was upgraded from TRC-10 to TRC-20 at contract address TAFjULxiVgT4qWk6UZwjqwZXTSaGaqnVp4, with a 1:1000 redenomination — every legacy BTT became 1,000 new BTT. The legacy TRC-10 token was renamed BTTOLD (still at token ID 1002000). Post-December-2021 BTT (TRC-20) cannot activate inactive accounts. A wallet whose first inbound transaction is post-2021 BTT must have been activated by a separate, earlier TRX or TRC-10 transfer.
JST — May 2020, passive, TRX-holder eligibility
The JST airdrop ran from May 2020 through October 2022 in four phases. Per the TRON DAO Foundation’s announcement, eligibility required holding ≥100 TRX; distribution was passive (no claim transaction). The schedule:
| Phase | Period | Distribution |
|---|---|---|
| Initial | May 20, 2020 | 217,800,000 JST (2.2% of supply) |
| Phase 1 | June 20, 2020 → May 20, 2021 (12 months) | 237,600,000 JST |
| Phase 2 | June 20, 2021 → May 20, 2022 (12 months) | 257,400,000 JST |
| Phase 3 | June 20, 2022 → October 20, 2022 (5 months) | 277,200,000 JST |
The snapshot was taken at 00:00 UTC on May 20 each year. A wallet that held ≥100 TRX on the right dates would have received JST inflows without signing any transaction.
JST contract address: TCFLL5dx5ZJdKnWuesXxi1VPwjLVmWZZy9 (per the public TRON token registry). JST is a TRC-20 token, so JST airdrops did NOT activate inactive accounts — recipients had to already be active TRX holders (the ≥100 TRX requirement made this implicit). The attribution signature is therefore weaker than BTT: a JST inflow tells you the recipient was an active TRX holder on the snapshot date, nothing more.
SUN — September 2020, claim-based via Genesis Mining
SUN is the consistent exception to the “TRON-era airdrops were passive” pattern. SUN was not airdropped. The SUN Genesis Mining program launched September 2, 2020 required active participation: users deposited TRX into the SUN.io mining smart contract, locked it for 14 days, and could later withdraw both their TRX and the earned SUN tokens.
The on-chain footprint is fundamentally different from BTT or JST. SUN recipients have:
- A signed deposit transaction to the SUN.io Genesis Mining contract
- A signed withdrawal transaction after the lock period
- An attributable interaction trail with named contracts
Per the Genesis Mining mining rules, SUN was distributed across multiple pools — TRX (30%), JST (10%), USDJ (10%), BTT (5%), WIN (5%), and community/liquidity projects (40%). Each pool had its own deposit contract; a wallet’s SUN history is partially reconstructable from which pools it deposited into.
For attribution: a wallet holding SUN has explicit on-chain proof of intent. A wallet holding BTT, JST, WIN, or APENFT has no such proof — the token may have been passively delivered.
Subsequent SUN.io airdrop programs (notably the veCRV-style distribution tied to the Curve partnership) are also claim-based. Per SUN.io’s own documentation, addresses must actively claim within a defined window; “if an eligible address hasn’t claimed their SUN airdrops from the previous four airdrops, no SUN rewards will be sent to that address in subsequent airdrops.” Inactivity forfeits future eligibility. This claim-based pattern leaves a transaction trail the investigator can use.
WIN — August 2019, passive, three years
The WIN airdrop (WINk Foundation) launched August 28, 2019, with a snapshot at TRON block height 12,226,666 (Unix timestamp 1566921600000). Initial distribution was 10,989,000,000 WIN (1.1% of total supply) at a ratio of approximately TRX/WIN = 9.046392. The program continued monthly through August 28, 2022, distributing 49,950,000,000 WIN total (5% of supply) to TRX holders.
Distribution was passive. Per WINk Foundation: “If you control the secret key of your TRX, you don’t need to do anything to receive WIN airdrop.” Snapshot frequency was monthly. A long-lived TRX-holding wallet would have accumulated WIN inflows from dozens of monthly snapshots between August 2019 and August 2022 without signing any related transaction.
WIN contract: TLa2f6VPqDgRE67v1736s7bJ8Ray5wYjU7 (per the public TRON token registry). WIN is a TRC-20 token, so WIN airdrops did NOT activate inactive accounts.
APENFT — June 2021 through June 2023, passive
APENFT (NFT token) was distributed monthly to holders of TRX, BTT, JST, and WIN between June 2021 and June 2023. Snapshots ran at 12:00 UTC on the 10th of each month. Per APENFT’s own announcement, recipients were “not required to take any additional action” — the distribution was passive in the same pattern as BTT/JST/WIN.
One structural difference: APENFT’s foundation explicitly excluded exchange hot wallets that had not declared support for the airdrop. This was a contrast to BTT/JST/WIN distributions, which went to declared-supporting exchanges. A wallet’s APENFT receipt history therefore carries an additional inference: the wallet was not on APENFT’s exchange-exclusion list at the time of each monthly snapshot, which is mild evidence it was not treated as an exchange-controlled custodial address.
USDD is not an airdrop
USDD (/learn/stablecoins-beyond-usdt/ covers its history and design in full) has never been distributed via airdrop. From its May 2022 launch through the January 2025 USDD 2.0 redesign and beyond, USDD has entered circulation through TRON DAO Reserve-controlled issuance mechanisms — first an algorithmic TRX-backed mint-and-burn system, later an overcollateralized mint-and-redeem system — never through a snapshot-based or claim-based distribution to TRX holders. A wallet receiving USDD received it either via issuance from a Reserve-controlled minter or via TRC-20 transfer from another holder.
TRC-10 vs TRC-20 — the activation distinction made specific
The protocol rule is straightforward: TRX and TRC-10 token transfers can activate inactive TRON accounts at a 1 TRX account-creation fee (with an additional 0.1 TRX fee when the sender’s Bandwidth is insufficient). TRC-20 token transfers cannot activate accounts.
For airdrop analysis, this rule applies as follows:
| Token | Standard | Activation behavior |
|---|---|---|
| Original BTT (Feb 2019 → Dec 2021) | TRC-10 (ID 1002000) | Activates inactive wallets |
| BTTOLD (post-Dec 2021 legacy) | TRC-10 | Still TRC-10; can technically activate, but no new BTTOLD is distributed |
| BTT (post-Dec 2021) | TRC-20 (contract TAFjUL…) | Cannot activate |
| JST | TRC-20 | Cannot activate (eligibility was ≥100 TRX, so recipient already active) |
| WIN | TRC-20 | Cannot activate (eligibility was TRX holder, so recipient already active) |
| APENFT | TRC-20 | Cannot activate |
| SUN | TRC-20 (and claim-based, not airdropped) | Cannot activate; recipient already active by definition |
The asymmetry creates a clean attribution rule: a wallet whose very first inbound transaction is a 2019-era BTT airdrop with the wallet previously inactive was brought into existence by that airdrop. No other TRC-20-era airdrop has this property.
Investigator interpretation patterns
First activator = testnet faucet (Nile or Shasta dispenser). Developer test wallet. Testnet TRX has no economic value; faucets exist solely to bootstrap development work. No attribution should attach beyond “this is a developer’s test fixture.” See /learn/account-activation/ for activation-by-EOA mechanics.
First inbound = original BTT (2019) on a previously inactive wallet. The wallet was activated by the BTT airdrop. Attribution implication: the holder of the underlying TRX private key passively received the airdrop without signing any transaction. Such a wallet may have remained dormant for years between activation and any subsequent user-driven activity. The 2019 BTT airdrop activation does NOT signal user intent — it signals only that someone held that TRX address’s keys at the right moment.
Recurring BTT / JST / WIN / APENFT inflows without corresponding outbounds to airdrop contracts. Passive recipient pattern. The wallet held qualifying TRX (or other token) balances across multiple snapshots. Most useful when reconstructing wallet activity timelines: the snapshots are predictable, so an investigator can date when a wallet must have been active relative to each snapshot.
Signed SUN Genesis Mining deposit/withdrawal pair. Active participant signal. The wallet’s owner deposited TRX, waited the lock period, and withdrew with SUN earnings. This is direct on-chain evidence of user intent and SUN.io ecosystem participation — qualitatively different from passive token receipt.
Signed claim transactions to a SUN.io veCRV airdrop contract or any other claim-based program. Active participant signal with intent. The wallet’s owner read the airdrop documentation, navigated to the claim UI, and signed a transaction to receive the tokens.
Faucet-style microfaucet first activation (third-party mainnet “TRX faucets”). Ad-incentivized faucet user pattern. Often paired with bot-like behavior — small recurring TRX inflows from many faucet addresses, low outbound diversity, no other ecosystem activity. The wallet’s owner is most likely either an individual chasing ad-funded crypto microincome or a bot operating across many such accounts.
Ecosystem grants — the post-airdrop incentive layer
TRON DAO operates an Ecosystem Fund that the Foundation has publicly described as a $1 billion commitment (per the trondao.org ecosystem-fund page), supporting hackathons (HackaTRON) and a range of grant programs. As of May 2026 the most recent independently-verifiable HackaTRON edition is Season 6 (February 2024), which ran with a $650,000 prize pool per Blockworks and Decrypt coverage. Grant-program recipient wallets do not follow the passive airdrop pattern — they receive TRX or token disbursements via direct TRON Foundation-controlled transfers, with explicit recipient agreements off-chain.
For attribution purposes, a wallet receiving repeated TRX transfers from a known TRON Foundation grant-program address has a documented institutional relationship. The Foundation’s grant-disbursement wallets are catalog candidates worth maintaining in an investigator’s allowlist if grant-related attribution is in scope.
Sources
- TRON Developer Hub — Networks — primary; Nile and Shasta testnet specifications and faucet URLs.
- TRON Developer Hub — Getting Testnet Tokens — primary; faucet caps, claim mechanisms, and TronFAQBot bot commands.
- TRON Developer Hub — Account — primary; activation mechanics and 25,000 Energy cost for smart-contract activation.
- BitTorrent Foundation — BTT Airdrop Program Initiated (Jan 2019) — primary, BitTorrent Inc.; BTT airdrop announcement and snapshot block height.
- BitTorrent Foundation — More Details on BTT Airdrops — primary; passive distribution mechanism.
- BitTorrent Foundation — Launch of BTTC Mainnet and BTT Redenomination Plan (Dec 2021) — primary; TRC-10 → TRC-20 upgrade, 1:1000 redenomination, BTTOLD.
- TRON DAO Foundation — JUST (JST) Airdrops for TRX Holders — primary; JST airdrop schedule, eligibility threshold, snapshot timing.
- TRON Foundation — SUN Genesis Mining Rules — primary; SUN Genesis Mining mechanics, pool allocations, deposit/withdrawal flow.
- WINk Foundation — WINk (WIN) Airdrop Program Initiated — primary; WIN airdrop snapshot block height, ratio, passive mechanism.
- APENFT Foundation — APENFT NFT Airdrop to TRON Token Holders Concluded — primary; APENFT snapshot schedule, exchange-hot-wallet exclusion.
- TRONORIGIN HEURISTIC_SPEC.md — project’s spec; FAUCET category (-15 weight) and protocol-context activation rules.
- TRONORIGIN RESEARCH_FINDINGS.md — project’s research; TRC-10 vs TRC-20 activation distinction.