Tether’s USDT Went Live on Algorand’s New Asset Layer

Algorand Foundation announced on February 10, 2020 that Tether’s USDT was live on Algorand 2.0, making it the first stablecoin deployed through the network’s recently introduced Algorand Standard Asset system.

The launch completed a plan Tether had disclosed on July 17, 2019, when the issuer described an upcoming Algorand deployment alongside its existing implementations on Omni, Ethereum, Tron and EOS. The February 10 announcement therefore marked the transition from a proposed integration to an officially launched asset.

That distinction mattered for Algorand. A blockchain could advertise fast settlement and native tokenization, but financial applications also required assets with recognizable units of account and liquidity outside the network. Adding the dominant dollar-linked token gave developers a potential settlement asset that did not require users to take the price risk of ALGO, Algorand’s native token.

The announcement did not establish how much USDT had been issued on Algorand, how many users could access it or whether exchanges had enabled deposits and withdrawals. It verified availability, not adoption.

A stablecoin built as a native asset

USDT used the Algorand Standard Asset, or ASA, functionality introduced with Algorand 2.0. Algorand’s November 27, 2019 developer documentation described ASAs as layer-one assets that could represent fungible or non-fungible instruments without requiring a separate smart-contract implementation.

The protocol supplied transaction types for creating, transferring, freezing, revoking and destroying assets. Accounts had to opt in before receiving a particular ASA. The documentation also said every asset holding increased an account’s minimum balance requirement by 100,000 microAlgos.

Those mechanics were institutionally relevant because they placed asset controls and transfers inside Algorand’s base protocol. Tether and Algorand claimed the implementation would benefit from block confirmation in under four seconds and transaction fees amounting to a fraction of a percent. Those were contemporaneous platform claims, not results from an independent February 10 performance study.

The integration also preserved issuer control. ASA documentation allowed an asset creator to configure management, freeze and clawback addresses. Consequently, describing USDT as operating on a permissionless blockchain did not mean the token itself lacked centralized issuance or administrative controls.

Tether brought meaningful market scale

CoinMarketCap’s historical snapshot labeled February 10, 2020 listed USDT at $1.0006, with 4,642,367,414 tokens in circulating supply and a market capitalization of approximately $4.645 billion. The provider ranked it eighth among all listed cryptoassets.

CoinMarketCap also displayed approximately $48.784 billion in trailing 24-hour volume. That figure showed USDT’s reported importance as a trading intermediary, but it was an exchange-aggregated estimate rather than audited settlement volume. It could include duplicated turnover, venue-specific methodology and reporting from markets with uneven data quality.

The market snapshot supports the scale of the asset Algorand was adding; it does not measure activity on Algorand itself. No defensible event-day record reviewed for this reconstruction separates Algorand-based USDT supply, transfer volume or active holders from Tether’s totals across other networks.

What February 10 established

The defensible conclusion is narrow: on February 10, 2020, Tether and Algorand represented USDT as live through Algorand’s native asset layer, completing a previously announced integration. The launch expanded Tether’s multi-network strategy and gave Algorand its first stablecoin, but immediate exchange support, circulation and user demand remained unverified.

Later context

Tether stopped minting USDT on Algorand on June 24, 2024, citing its periodic assessment of community usage and maintainability. That later decision does not alter the February 10 launch record, but it shows why technical availability should not be treated retrospectively as proof of lasting adoption.