USDD

USDD entered circulation on 30 April 2022. The white paper began with 999 billion pre-issued TRC-10 units, while whitelisted TRON DAO Reserve members moved issuance through authorized contracts and a seven-member multisig that required five signatures.

The design connected creation and contraction to TRX and placed reserves under TDR custody. It was marketed as decentralized, but access to the issuance channel belonged to approved institutions rather than every wallet. That distinction mattered because USDD was a token on TRON, not TRX itself. TRON supplied the ledger and gas; TDR members ran the stablecoin's monetary doorway.

Less than two months after launch, the wider crypto sell-off reached USDD. CNBC recorded it around $0.93 on 19 June 2022 while TRON DAO Reserve added capital and Justin Sun defended the system.

The price later moved back toward one dollar, but the episode showed that reserve headlines did not give holders an automatic par redemption order. The issuer's own 2022 answers also said USDD was not bound like a centralized issuer to redeem real dollars.

The useful lesson is narrower than a comparison with Terra: arbitrage works only when traders trust the assets, counterparties and route on the other side of the trade. USDD's first version asked the market to trust a committee-managed defense.

In January 2025, USDD 2.0 went live on TRON as a new token. The old TPYm… contract became USDDOLD, and a migration contract offered equivalent new units without a deadline.

The replacement adopted a modified Maker/Sky design.

A borrower locks approved collateral, mints USDD debt, pays stability fees to close, and risks liquidation if the vault falls below its configured ratio. Dutch auctions sell liquidated collateral.

This changed who could create supply and how bad positions were handled. It did not turn every token holder into an owner of the collateral: repayment releases a vault owner's assets, while a holder owns transferable USDD.

The Peg Stability Module accepts supported stablecoins and mints USDD, or burns USDD and releases the requested stablecoin. The interface advertises a fixed 1:1 rate, no service fee and no slippage; users still pay network gas.

The guide tells users to inspect “Available” before swapping and prevents an order larger than the output inventory. This is an on-chain token conversion, not a standing instruction to a bank to wire dollars.

The distinction defines the holder's present right. A wallet can transfer USDD and attempt the PSM route where supported, but the reviewed terms do not grant title to a named reserve account or guarantee a fiat payout.

ChainSecurity's 24 January 2025 assessment described an admin multisig, not token-holder governance. It found that the admin could trigger privileged system actions, oracle wards could use an emergency price path, and the debt-auction operator could withdraw pre-deposited JST.

The audit also recorded a zero governance delay and a plan to move toward governance-token control. In the TRON state reviewed in September 2026, Pause still returned zero delay, PauseProxy was owned by Pause, and GovActionsProxy was owned by TSF2…. That owner account exposes one native key at threshold 1; public records do not name its real-world controller or show a transfer to token holders.

Yield follows a similar boundary. USDD itself pays nothing automatically. Depositors receive separate sUSDD, whose exchange rate is meant to reflect rewards and whose exit returns USDD. Smart Allocator says old rewards relied on TRON DAO subsidies and newer investments are selected and monitored by the USDD and JUST DAO teams.

The current deployment table identifies TXDk8mbtRbXeYuMNS83CfKPaYYT8XWv9Hz as TRON USDD, and Tronscan indexes it as the 18-decimal token created on 20 January 2025. The legacy TPYm… address is separately labeled USDDOLD. Repository history shows that on 11 May 2026 the team replaced TCrEVahRbhDFB6uRXEWUg7wkptXvg47GKs with TXDk… in the deployment row. A collateral-address page still calls that TCr… address “USDD,” although the reviewed Tronscan contract endpoint returned no contract record for it.

This documentation fault does not erase the chain evidence, but it raises the cost of verification. A holder should resolve addresses from the current deployment registry and explorer before signing, rather than assuming every official page has been synchronized.