USDT0

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

REJECTED ON A TERMS-VERSUS-CODE GAP THAT ADDS RISK WITHOUT ADDING BENEFIT. USDT0 is Tether’s omnichain USDT, built on LayerZero’s OFT standard and operated by Everdawn Labs Limited: canonical USDT locks in an Ethereum adapter contract and USDT0 mints 1:1 on the destination chain. It inherits every USDT issuer and jurisdiction risk while adding an operator whose corporate relationship to Tether is assumed, not confirmed, plus the LayerZero DVN messaging-layer dependency this registry separately rejects. Worse, USDT0’s own Terms of Service describe no blacklist or freeze power, yet the deployed contract on Ink Chain includes functions to block addresses and destroy their held funds — a real, code-level control point the user-facing terms do not disclose. And actual redemption rights are governed by Tether’s own ”verified customer” gate, not a permissionless unlock, so a USDT0 holder gets worse redemption certainty than a direct USDT holder, not better.

Kill criteria: the events that revoke this verdict
• Everdawn Labs’ corporate relationship to Tether Limited is confirmed via a primary filing or Tether’s own disclosure
• USDT0’s Terms of Service are amended to explicitly disclose the blacklist and fund-destruction authority present in the deployed contract code
• A named chain’s OFT deployment is audited independently of Tether and LayerZero’s own claims, with the report published
• A proposed-size redemption from burned USDT0 to unlocked Ethereum USDT is demonstrated end to end without invoking Tether’s verified-customer gate for an unaffiliated holder
• Any confirmed depeg, minting irregularity, or DVN-layer compromise affecting USDT0 specifically

The research file

Mechanism

USDT0 is a lock-and-mint design on top of LayerZero’s Omnichain Fungible Token standard, operated by Everdawn Labs Limited (usdt0.to): canonical USDT locks in an OAdapterUpgradeable contract on Ethereum mainnet, and an equivalent amount of USDT0 mints 1:1 on the destination chain. Moving USDT0 between non-Ethereum chains burns on the source and mints on the destination via LayerZero messaging; unlocking the original USDT requires bridging back to Ethereum and redeeming through the adapter. It is live on 14 or more chains including Arbitrum, Berachain, HyperEVM, Plasma, and TON, where TON alone carries roughly $152M of USDT0 supply per the protocol’s own analytics.

Control and the terms-versus-code gap

Everdawn Labs Limited administers the protocol and its Terms of Service; independent legal review states it can be assumed to be a Tether-affiliated entity, but no direct corporate relationship to Tether or any named parent is confirmed in public filings. Everdawn is stated as not registered with FinCEN, and USDT0’s terms do not address MiCA authorization, inheriting USDT’s existing EU non-compliance posture. Most materially: USDT0’s Terms of Service do not describe any blacklist or freeze power, but the deployed TetherTokenOFTExtension contract on Ink Chain includes functions to add or remove addresses from a blocked list and to destroy funds tied to a blocked address. A control this significant existing in code but absent from the terms a holder actually reads is a transparency failure independent of whether the power has been used.

Incident record

No USDT0-protocol-level exploit or depeg was identified. One application-level incident is adjacent but distinct: a HyperEVM DeFi exploit drained 214,125 USDT0 alongside USDC and USDH from an application holding those assets — a failure of that application, not of USDT0’s own mint, lock, or messaging mechanism; this detail was not independently confirmed against a primary post-mortem in this pass and should be treated as unverified. An Immunefi bug bounty has been active since 2025-01-30, explicitly scoped to vulnerabilities affecting USDT redemption on Ethereum.

Exit and redemption

USDT0’s own terms give no explicit redemption guarantee or procedure. Mechanically, a holder burns USDT0 on a supported chain to unlock the underlying USDT on the Ethereum adapter, but the actual right to redeem that USDT is governed by Tether’s own terms, which restrict redemption to ”verified customers.” A USDT0 holder’s ultimate cash-out path therefore runs through Tether’s KYC’d process regardless of how many chains the token has moved across, which is a narrower right than holding canonical Ethereum USDT directly provides no additional benefit for the extra dependency layers taken on.

Comparison

Against canonical Ethereum USDT, USDT0 adds LayerZero DVN messaging-layer trust (reviewed separately in this registry and rejected on the April 2026 infrastructure compromise), an unaccountable intermediate operator in Everdawn Labs, and an undisclosed-in-terms freeze and fund-destruction function — strictly more dependency layers for exposure to the same underlying issuer and the same eventual KYC-gated redemption right. There is no scenario in this review where USDT0 is preferable to canonical USDT for a client who could hold either.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• USDT0 technical documentation · primary · accessed 2026-08-17
  Supports: OFT mechanism, lock-and-mint flow, adapter architecture
• LlamaRisk — regulatory pressure on USDT and legal features of USDT0 · secondary · accessed 2026-08-17
  Supports: Everdawn Labs, freeze and blacklist code versus terms, redemption rights, BVI law
• Immunefi — USDT0 bug bounty · primary · accessed 2026-08-17
  Supports: bounty scope, live since 2025-01-30
• USDT0 analytics · primary · accessed 2026-08-17
  Supports: per-chain supply figures
• PR Newswire — Bybit expands USDT0 support to HyperEVM, Corn, and Berachain · secondary · accessed 2026-08-17
  Supports: chain expansion timeline

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.