TUSD is a redemption-gated float, not a “market cap” story

TrueUSD (TUSD) behaves like a high-frequency liability instrument, not a value-accrual token. The economic “design” is simple: the float expands when verified users bring in dollars, and it contracts when verified users redeem and burn. The interesting part is not the peg marketing. It is the liquidity structure around creation and redemption.

On the primary rails, TUSD is minted after a user wires funds to a banking partner, and the token is then transferred to the wallet address provided in the TrueUSD app. Redemptions route through the same portal, with KYC/AML controls and a stated minimum redemption size of $1,000. Those gates define who can actually arb the peg back to $1 when secondary market liquidity gets thin.

TUSD’s own 2026 whitepaper frames the token as redeemable by “eligible verified customers” and explicitly positions secondary-market stability as contingent on market conditions and redemption pathways.

Supply mechanics: mint authority, burn paths, and why FDV is pointless here

There is no meaningful “FDV narrative” for TUSD because supply is not a capped distribution with unlocks. It is a balance-sheet number that should move with deposits and redemptions. CoinGecko shows circulating supply and total supply as equal, reported as 494,515,083 TUSD on March 4, 2026.

On Ethereum mainnet, the core ERC-20 is upgradeable via a proxy at 0x0000000000085d4780B73119b644AE5ecd22b376. What matters for tokenomics is who can change supply. In the verified TrueUSD implementation contract, only the owner can mint.

Burning is structurally tied to redemption flows. The contract defines a large set of “redemption addresses” and makes transfers to those addresses trigger burns, with rounding to 1-cent precision (implemented via a CENT constant and a ROUNDING value of 2). Importantly, the same contract documentation notes that “redemptions are tracked off-chain.”

As a Liquidity Structure Realist, this is the headline: the peg is only as tight as the speed and capacity of off-chain redemption, plus the number of players who can access it.

For contrast with an emissions-and-unlocks tokenomics profile, compare this framework to our Blur tokenomics review.

Effective circulating supply: native vs bridged, and where “tradable float” breaks

TUSD markets itself as multi-chain, but the float is not one homogenous blob. TUSD lists “natively deployed” versions on Ethereum, TRON, Avalanche, and BNB Smart Chain, and “bridged” versions on Polygon, Arbitrum, Cronos, Optimism, and Aurora.

That split matters because redemption and risk management often live on the native issuance rails. TrueUSD’s transparency page explicitly notes that the TUSD app “currently only supports native versions of TUSD.” So even if a bridged TUSD unit trades at $1 on a DEX, your ability to turn it into bank USD depends on a chain of conversions, bridge solvency, and the availability of native liquidity.

This is where “circulating supply” can mislead. On-chain supply might be fully circulating, but the effective circulating supply under stress is the portion that can reach a verified redemption endpoint quickly. KYC onboarding time, wire timing, minimum redemption size, and which chain you are on all shape the real float.

If you want a compact framework for mapping these constraints, start with the design components that typically govern who can enter and exit a token’s economy.

Proof of Reserve as a mint circuit breaker

TUSD’s strongest on-chain tokenomics feature is that minting can be constrained by a Chainlink Proof of Reserve (PoR) feed. In the TrueCurrencyWithProofOfReserve logic, the internal mint path checks a configured PoR feed for (1) matching decimals, (2) a positive reserve value, (3) freshness via a heartbeat window, and (4) a hard constraint that totalSupply + amount <= reserves before allowing minting.

Mechanically, that can reduce one classic failure mode: “infinite mint” errors or operational over-issuance that shows up only after the fact. It is also not a silver bullet because the same contract gives the owner explicit admin controls to set the feed, set the heartbeat expectation, and enable or disable PoR enforcement.

On the Chainlink side, the public reserves feed on Ethereum shows a deviation threshold of 5% and names MooreHK as the data source. Chainlink is also explicit that the PoR “Answer” is only what the data source reports and “may not represent the actual present value” due to liquidity and timing effects.

The feed’s own disclaimer goes further on data quality. It states that Moore Hong Kong is engaged by Techteryx to aggregate Balance Data, that the standard reporting interval is once per day, and that the Balance Data is a “non-attest service” sourced from third parties with no attestation to accuracy by MooreHK or Chainlink service providers.

Net: PoR helps constrain issuance if it is enabled and the feed is fresh and reliable. It does not, on its own, guarantee redemption liquidity or fully modelable solvency.

Fiscal flows: “no fees” plus positive carry

TUSD claims it does not charge fees for minting and redemption. That is supply-positive for adoption because it lowers friction for market makers and treasury managers.

But “no fees” does not mean “no economics.” The 2026 whitepaper states that no interest is paid to users on funds held in their TUSD accounts and that TUSD assets are not insured. It also states that TUSD may collect interest or investment returns on fiat deposits held in TUSD escrow accounts and that balances held by banking partners may include cash equivalents and other investments that generate yield to support TUSD’s administrative and operational costs.

So the core fiscal flow is typical for centralized stablecoins: users get stability and transfer utility, while the operator captures the reserve carry to fund operations. The trade-off is structural. If the operator is yield-motivated, asset composition and counterparty selection become first-order risks for token holders, even if on-chain token mechanics look clean.

Control surface: blacklist, confiscation, and upgradeability

TUSD’s tokenomics are explicitly compliance-oriented. The verified Ethereum implementation includes owner-controlled blacklist functionality, and transfers and approvals check blacklist state. The owner can also destroy (“confiscate”) funds from blacklisted addresses via destroyBlackFunds.

Burning is permissioned at the address level. The owner can set burn bounds (min and max) and set which addresses are allowed to burn using setCanBurn.

Upgradeability is also part of the control surface. The mainnet TUSD address is a proxy, and the proxy contract exposes proxy ownership transfer and an upgrade function (upgradeTo) gated by the proxy owner. In plain terms, token holders are exposed not only to reserve management but also to smart contract governance risk via admin keys.

That centralized control is not automatically “bad.” It can be what makes large counterparties comfortable holding it. It does mean TUSD should be analyzed like a managed product where legal and operational decision-making is part of tokenomics.

If you want a quick orientation on the recurring concepts, our tokenomics FAQ covers the basics without assuming a DeFi-native background.

Risk analysis

Dominant risk: redemption liquidity is off-chain, partner-dependent, and gated.

TUSD’s on-chain design does two things well. It makes minting owner-controlled and it can enforce a PoR constraint at mint time. But the peg does not live or die on mint logic. It lives or dies on the market’s belief that a marginal TUSD unit can exit to bank USD quickly and predictably, at scale, through verified channels.

Three mechanisms make this the dominant risk.

First, redemption is structurally centralized and eligibility-gated. The public TrueUSD flow requires users to create and verify an account and then use wire transfers for minting and redemption. That is normal for fiat-backed stablecoins, but it narrows the set of arbitrageurs who can actively defend the peg during stress. When fewer participants can redeem, secondary market price can drift because selling pressure is not met by immediate redeem-driven demand.

Second, multi-chain “circulating supply” can overstate immediate redeemable float. The app supports native versions only, while bridged liquidity depends on bridge pathways and the ability to move into native TUSD before redemption. In stress, bridge capacity and exchange constraints become part of tokenomics, even though they are not expressed as protocol parameters.

Third, the transparency apparatus itself has explicit limitations. Chainlink’s PoR feed for TUSD flags that the answer is data-source reported and can diverge from “actual present value,” and its detailed disclaimer frames the Balance Data as third-party sourced and “non-attest,” with MooreHK aggregating information on behalf of Techteryx. If the market loses confidence in the reporting pipeline or the banking partners, you can get a reflexive liquidity unwind. The 2024 depeg episode is an example of how quickly this can happen in practice, with Cointelegraph’s depeg report describing TUSD trading down to about $0.984 on January 15, 2024 amid heavy selling and concerns around reserve attestations.

In other words, TUSD’s “float dynamics” are governed by off-chain throughput and trust. When that channel is smooth, TUSD trades like cash. When it is questioned, the tradable float effectively increases because holders stop treating TUSD as money and start treating it as inventory they want to exit.

We publish deeper write-ups on these failure modes (and how to monitor them) in our research reports.

Top 3 risks

  1. Redemption gating and banking-partner concentration. Trigger: a surge in redemptions, withdrawal delays, or new KYC/AML constraints. Mechanism: fewer verified arbitrageurs can redeem, so secondary market sellers overwhelm bid support and the peg softens. Who bears it: non-verified holders, DeFi users holding bridged TUSD, and LPs who wear the drawdown. Measurable indicators: widening CEX/DEX spreads, persistent sub-$1 prints, rising redemption backlog reports, and increased net outflows during sell events.

  2. Admin-key and contract-governance risk. Trigger: proxy upgrade, ownership compromise, or a policy-driven blacklist action. Mechanism: upgradeability can change contract behavior, and blacklist plus destroyBlackFunds can freeze or confiscate balances. Who bears it: any holder exposed to compliance actions or contract changes, including exchanges and protocols. Measurable indicators: proxy upgrades on the mainnet proxy, changes to owner addresses, and on-chain blacklist events.

  3. Proof-of-Reserve feed limitations and “false comfort”. Trigger: stale feed updates, reporting interruptions, or market skepticism about what the feed actually represents. Mechanism: mint constraints can be bypassed if PoR is disabled by the owner, and even when enabled the feed is only as good as the third-party reporting pipeline, which Chainlink notes may not represent actual present value and may be based on third-party sourced, non-attested Balance Data. Who bears it: anyone relying on PoR as a solvency guarantee, including DeFi risk managers and centralized venues. Measurable indicators: missing or delayed feed updates, heartbeat violations, unexplained discrepancies between supply and reserves feeds, and public changes to PoR configuration.

If you are integrating TUSD into a product, this is one of those cases where tokenomics consulting is mostly liquidity engineering. You are not optimizing emissions. You are modeling redemption throughput, chain routing, and the blast radius of admin controls.



This article is part of our Tokenomics Deep Dive series.