Skip to main content

Multichain Stablecoin Support Matrix: Chains by Provider 2026

Multichain stablecoin support by chain: CCTP, Tether, USDT0 and Legacy Mesh coverage from each provider's own pages.

Written by Eco
Multichain Stablecoin Support Matrix: Chains by Provider 2026

A multichain stablecoin support matrix shows, chain by chain, which issuers and transfer providers list support for USDC or USDT there. It answers a planning question before any route comparison: can the asset exist natively on both ends, and which mechanism connects them? Coverage differs sharply. Circle's CCTP lists 31 blockchains in its supported-chains table, while USDT0 lists 24 native networks and a six-chain Legacy Mesh, and Tron appears on Tether's list but not on CCTP's (Circle CCTP supported blockchains, USDT0 deployments).
​

Last reviewed: Nov 2026. Every cell comes from the provider's own deployment or chain page. "Not listed" means the provider's page did not list the chain when fetched, nothing more.
​

How the Matrix Is Built

The matrix uses one rule: a chain counts as supported only if the provider's own documentation lists it. Marketing pages, third-party trackers and announcements of future support are excluded. Each provider column links to the exact page used, so a reader can recheck any cell.

  • Circle CCTP: the supported-chains table with Standard and Fast source columns (Circle).

  • Tether native USDT: Tether's supported protocols page (Tether).

  • USDT0 native: the OFT deployment list (USDT0 deployments).

  • USDT0 Legacy Mesh: the connected-chains list (USDT0 Legacy Mesh).

  • Eco Routes: chain types from the Routes API reference; the live chain list is served by the API (Eco Routes API).

Which Chains Does Each Provider List?

The matrix covers fifteen chains that hold most stablecoin supply or appear in common routing questions. USDC coverage through CCTP is broad across EVM chains plus Solana. USDT coverage splits between Tether's native deployments, USDT0's OFT network, and the Legacy Mesh that joins them.
​

Chain

CCTP (USDC)

Tether native USDT

USDT0 native

USDT0 Legacy Mesh

Sources

Ethereum

Listed, Fast source

Listed

OFT adapter

Listed

Tron

Not listed

Listed (TRC-20)

Not listed

Listed

Solana

Listed, Fast source

Listed

Not listed

Listed

Base

Listed, Fast source

Not listed

Not listed

Not listed

Arbitrum

Listed, Fast source

Not listed

Listed

Hub

OP Mainnet

Listed, Fast source

Not listed

Listed

Via USDT0

Polygon PoS

Listed

Not listed

Listed

Via USDT0

BNB Smart Chain

USYC only

Not listed for USDT

Not listed

Not listed

Avalanche

Listed

Listed

Not listed

Not listed

Plasma

Listed

Not listed

Listed

Via USDT0

HyperEVM

Listed

Not listed

Listed

Via USDT0

Unichain

Listed, Fast source

Not listed

Listed

Via USDT0

Ink

Listed, Fast source

Not listed

Listed

Via USDT0

Celo

Not listed

Listed

Not listed

Listed

TON

Not listed

Listed

Not listed

Listed

"Via USDT0" means the chain has a native USDT0 deployment, which the Legacy Mesh documentation says it can reach through the Arbitrum hub (USDT0 Legacy Mesh).
​

Provider Blocks

Each provider below is described with the same three fields. Order follows the matrix columns, with routing layers after the issuer and token rails. The point is coverage, not ranking.
​

Circle CCTP

Best for: native USDC across EVM chains, Solana and several non-EVM chains. Pros: 31 chains in the table, with a Fast Transfer column. Cons: USDC only; no Tron (Circle).
​

USDT0 (OFT and Legacy Mesh)

Best for: USDT across EVM chains, plus Tron, Solana and TON through the mesh. Pros: 24 native networks. Cons: Legacy Mesh transfers carry a 0.03% fee (USDT0 Legacy Mesh).
​

Across

Best for: relayer fills between major chains. Pros: states support for 24 chains and native USDC and USDT0. Cons: the chain list sits in its API docs rather than one table (Across docs).
​

Eco Routes

Best for: one API across EVM, Solana and Tron chain types. Pros: the chain object's type field covers evm, svm and tvm (Eco Routes API). Cons: no static public chain list; the live list requires an API call.
​

How to Read Gaps in the Matrix

A gap usually means the asset reaches that chain by another mechanism, not that it is absent. USDC on Tron is the exception: Circle's status page says it is discontinuing USDC support on Tron in a phased transition (Circle status). A gap in both USDT columns, as on Base, means any USDT found there was not issued through Tether's or USDT0's listed deployments.
​

Is the asset native on both chains?
 |-- USDC: both chains in CCTP table? -> CCTP or a router using it
 |-- USDT: both Tether-native?        -> Legacy Mesh, exchange, or solver route
 |          both USDT0-native?        -> USDT0 OFT transfer
 |          one of each?              -> Legacy Mesh via Arbitrum hub
 '-- Not native on the destination    -> expect a bridged token; check the contract

For chain-level supply behind these rows, see the related data page; for wallets that span these chains, see multi-chain stablecoin wallets.
​

Where This Falls Short

The matrix shows listing, not liquidity or quality of service. A chain listed by a provider can still have thin liquidity, paused routes or pending upgrades. Providers add chains often, so a monthly recheck is the minimum.

  • Listing is not liquidity. Supply by chain is on the data page linked below.

  • Eco and Across rows are summaries because neither publishes one static chain table.

  • BNB Smart Chain: Tether's page lists only an XAUt contract there, and CCTP lists the chain for USYC only (Tether, Circle).

Frequently Asked Questions

These answers cover the most common questions about stablecoin chain coverage.
​

Does CCTP support Tron?

No. Tron is not in Circle's CCTP table (Circle).
​

Is USDT on Polygon USDT0?

USDT0's deployment page lists the Polygon PoS token at 0xc2132D05D31c914a87C6611C10748AEb04B58e8F as a USDT0 deployment (USDT0 deployments).
​

Which provider covers the most chains?

By listed count on the pages reviewed, CCTP with 31.
​

Related Reading

Sources and Methodology

Every cell was taken from the provider pages below, fetched on November 11, 2026. No secondary trackers were used.

Did this answer your question?