Need verifiable oracle data for your project?
DIA provides transparent, customizable price feeds across 50+ chains with fully auditable methodology.
Issued by Techteryx (TrueUSD)
Market cap
DIA price
Total supply
Holders
494.5M TUSD
347,313holders
Measured on Ethereum. Shares are of the Ethereum supply, not the multi-chain total.
$0since Fri, Aug 28 UTC
Change in the supply DIA reads across this coin’s chains, between two daily snapshots. Not mints minus redeems: DIA does not publish issuance flow.
Market data · CoinGecko
Market data · CoinGecko
Circulating supply · DeFiLlama
Aggregator figure, not a contract read. DIA’s own onchain supply is the separate series below.
Percentage change in TUSD's circulating supply as reported by DeFiLlama, measured against that source's own past. It is not a change in the onchain supply above, which DIA reads from the contracts directly and which is a different measurement of the same coin. A dash means the map has no reading close enough to the start of the window, a stretch inside it where supply was not reported at all, or a starting figure too small for a percentage to describe. Hover a dash for which.
$359K
deployed across 3 markets on 3 protocols
Lower bound: TUSD's balance inside lending markets DIA reads on-chain directly. Excludes DEX liquidity, CDP collateral, and any market on a chain or protocol DIA does not yet track.
DIA price
$0.9994
Peg deviation
-6 bps
Peg currency
USD
Launched
Primary use
—
Last snapshot
Fri, Sep 4 UTC
TrueUSD is a fiat-collateralised stablecoin pegged to the US dollar and tracked in the map's global region. The issuer is Techteryx.
Supply and price on this page are DIA first-party registry data. The registry records 494.5 million TUSD outstanding across Ethereum, Tron, BNB Chain and Avalanche. Ethereum carries 315.1 million of that float. Tron carries 168.5 million.
Sources: TrueUSD white paper, last updated 2 February 2026 (tusd.io)
What is published
Moore Hong Kong runs an automated attestation system called VeriNumus that publishes a live reserve dashboard for TUSD, linked from the tusd.io transparency page. The standard reporting interval for the TUSD installation is daily. The dashboard treats a ripcord as a precondition: if one fires, no new attestation report is generated and the displayed balances stop updating. The dashboard values render in the browser and are not readable from the page source, so no ratio or balance is quoted here.
What it leaves out
The dashboard names no bank, no custodian and no reserve instrument. The transparency page describes daily attestation reports and a reserve breakdown without displaying either. The whitepaper says the USD balance held by banking partners "may include cash, cash equivalents and other investments that may generate yield to support TUSD's administrative, operational and related costs, fees and charges".
Sources: VeriNumus real-time reserve dashboard for TrueUSD, operated by Moore Hong Kong, TUSD transparency page (tusd.io), TrueUSD white paper, last updated 2 February 2026 (tusd.io)
No licence or registration is claimed on the TUSD site or in the whitepaper. The whitepaper says TUSD tokens "are not bank deposits, are not legal tender, and are not financial instruments, and TUSD services may not constitute regulated financial services or activities in some jurisdictions". Minting and redemption run through verified customers subject to KYC and AML screening.
Sources: TrueUSD white paper, last updated 2 February 2026 (tusd.io)
The reserve litigation
Dubai's Digital Economy Court continued a proprietary injunction and a worldwide freezing order over USD 456,000,000 transferred to Aria Commodities DMCC. The order supports Hong Kong proceedings brought by Techteryx. The judgment of H.E. Justice Michael Black KC issued on 16 September 2025 and was re-issued on 17 October 2025. Techteryx alleges the invested reserves were fraudulently misappropriated. Aria's Matthew Brittain rejects the claims. The allegations have not been tried.
What the map reads
The Global Stablecoin Map tracks TUSD on the four chains where DIA reads supply. Supply comes from the contracts at 0x0000000000085d4780B73119b644AE5ecd22b376 on Ethereum, TUpMhErZL2fhh4sVNULAbNKLokS4GjC1F4 on Tron, 0x40af3827f39d0eacbf4a168f8d4ee67c121d11c9 on BNB Chain and 0x1c20e891bab6b1727d14da358fae2984ed9b59eb on Avalanche. Per-chain splits sit in the stablecoin explorer.
What it does not read
The map does not read the fiat reserves. Those sit with banking partners the issuer does not name and reach the public only through the daily VeriNumus report.
Sources: VeriNumus real-time reserve dashboard for TrueUSD, operated by Moore Hong Kong, TUSD transparency page (tusd.io)
Techteryx.
No audit opinion is published. Moore Hong Kong operates an automated attestation system called VeriNumus that publishes a live reserve dashboard for TUSD on a daily reporting interval.
The whitepaper places TUSD in the fiat-collateralised category and says the USD balance held by banking partners may include cash, cash equivalents and other investments that may generate yield. No bank, custodian or specific reserve instrument is named on the site, in the whitepaper or on the attestation dashboard.
The Global Stablecoin Map reads TUSD supply on Ethereum, Tron, BNB Chain and Avalanche.
Techteryx brought Hong Kong proceedings alleging that reserves were fraudulently misappropriated after being transferred to Aria Commodities DMCC. In support of those proceedings, Dubai's Digital Economy Court continued a proprietary injunction and a worldwide freezing order over USD 456,000,000, in a judgment issued on 16 September 2025 and re-issued on 17 October 2025. The allegations have not been tried, and Aria's Matthew Brittain rejects them.
0x1c20e891…ed9b59ebExplorer ↗0x40af3827…121d11c9Explorer ↗0x00000000…cd22b376Explorer ↗TUpMhErZL2…S4GjC1F4Explorer ↗Supply on this page is read from these contracts. Addresses are verified by DIA against the issuer’s own published documentation.
0x1c20e891…ed9b59ebupgradeTo(address)0x40af3827…121d11c9upgradeTo(address)0x00000000…cd22b376destroyBlackFunds(address)mint(address,uint256)Not read on Tron. no RPC config.
Read from the deployed contract. “Not determined” means the contract’s full function set could not be enumerated, not that the capability is absent: a bytecode scan can confirm that a function exists and can never prove that one does not.