Choose the exact USDT or USDC network and understand token identity, fees and recipient support before sending.
Choose the asset and receiving network together.
A multichain service advertises several separate deposit routes. It does not make USDT or USDC transferable between chains by an ordinary send. A cross-chain route needs a documented bridge, issuer transfer or exchange operation, with an accepted output token and separate costs.
No network is inherently the best for mixing. Match the recipient first; then compare custody, complete fees, timing and token provenance. StableScope explains these checks but does not operate a mixer, accept deposits or verify a provider’s live supported-network list.
Match the asset against issuer records, then confirm what the recipient accepts. Token identifiers below come from the cited registry snapshots reviewed September 20–21, 2026; recheck the live registry before sending. They are not deposit addresses.
TON: a USDT ticker is not a route
USDT on TON is a Jetton. Tether’s registry identifies its master contract as EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs. That identifies the token, not a mixer or a deposit address.
Compare the Jetton master with Tether’s live registry; a holder’s Jetton wallet address is a different object.
Confirm USDT on TON with the recipient, including any required comment or memo. Never send funds to a token master as a substitute for deposit instructions.
Allow for TON-denominated network costs and the recipient’s account requirements. Service charges and any privacy promise require separate evidence.
Circle lists native Arbitrum USDC at 0xaf88d065e77c8cC2239327C5EDb3A432268e5831. A USDT-labelled Arbitrum balance needs its own contract and issuer or bridge evidence; the USDC address establishes nothing about USDT.
Confirm Arbitrum One and the exact asset contract with the recipient. Do not substitute an Ethereum address or a bridged USDC variant.
For USDT, native issuance is not established by the Tether registry snapshot used here. Obtain the representation’s official contract and bridge or issuer documentation before treating it as supported.
Arbitrum fees include execution and a parent-chain data component. Use the wallet’s complete ETH estimate; an advertised low fee is not a mixer privacy or delivery guarantee.
Circle lists OP Mainnet USDC at 0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85. USDT and bridged USDC require separate provenance checks; an OP Mainnet USDC entry is not proof of either.
Ask the recipient for OP Mainnet support and the exact contract. A same-looking Ethereum address is not a deposit-network confirmation.
The Tether registry snapshot does not establish native USDT on this route. Verify the actual USDT representation through its issuer or bridge documentation.
Use the full ETH fee estimate, including execution, L1 data and any applicable operator fee. A swap or mixer label does not establish unlinkability or recipient credit.
Avalanche C-Chain: network support is not token proof
On Avalanche C-Chain, Tether lists USDT at 0x9702230a8ea53601f5cd2dc00fdbc13d4df4a8c7; Circle lists USDC at 0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E. These are different token contracts, not recipient addresses.
Confirm C-Chain, not another Avalanche chain, and match the accepted contract. A bridged asset with a similar symbol can be a different deposit.
Use the wallet’s current AVAX gas estimate for the actual token operation. A network estimate does not include every service charge.
The issuer entries verify token identity only. No Avalanche mixer, custody model, payout or refund has been tested here.
Circle’s mainnet USDC entry for Algorand is asset ID 31566704. An ASA ID identifies the asset; a familiar name or logo does not. This USDC entry must not be used as evidence of current USDT support.
Compare the asset ID with Circle’s current registry and ask the recipient to confirm that ASA.
The receiving account must satisfy the asset’s opt-in requirements. Check the recipient’s address, minimum balance conditions and any platform-specific deposit instructions.
Algorand transaction fees are paid in ALGO; a provider may charge separately. Neither the fee nor the ASA model proves a mixer mechanism, privacy or refund availability.
Tether identifies Solana USDT by mint Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB. A wallet address, token account and mint serve different purposes. This mint is not a destination for sending funds.
Confirm the recipient accepts USDT on Solana and that exact mint, not Solana USDC.
Check the recipient token-account requirements and the wallet’s SOL fee estimate. Account creation can add cost beyond the transaction fee.
No Solana USDT mixer was transaction-tested. A low-fee network does not prove custody, refund or privacy claims.
The Tether registry snapshot used here does not establish a native Polygon USDT deployment. A Polygon USDT balance therefore needs evidence for its specific contract and issuer or bridge. Circle’s Polygon USDC documentation cannot verify a USDT token.
Obtain the token contract from the representation’s official documentation and match the recipient’s Polygon PoS deposit instructions. No Polygon USDT contract is certified here.
Check the current Polygon native-gas quote and any conversion or provider fee; do not reuse an Ethereum fee estimate.
A provider advertising a Polygon mixer still needs evidence of custody, mechanism, records and refunds. StableScope supplies no transactional route.
The Tether registry snapshot used here does not establish a native Base USDT deployment. A USDT-labelled token on Base requires its own official contract and provenance evidence. Native USDC and USDbC do not answer that question.
Ask for the exact Base token contract and the issuer or bridge documentation. No Base USDT contract or mixer support is certified here.
Confirm that the recipient accepts the same representation on Base. An Ethereum USDT deposit policy does not cover it.
Base fees include L2 execution and L1 data costs, paid through the network fee model; any exchange or service charge is separate. A cross-chain transfer is not a privacy guarantee.
The Circle mainnet registry snapshot used here has no BNB Chain USDC entry. A token called USDC on BSC or BEP-20 may be a pegged or bridged representation; its contract and backing must be established separately. No BNB USDC contract is certified by this guide.
Identify the exact BNB Smart Chain contract and its issuer or bridge records. Do not borrow a native USDC address from another chain.
Confirm the receiving service accepts that contract and keep BNB for the wallet’s current gas estimate. Provider charges and deposit minimums are separate.
No KYC is an operator policy, not a BEP-20 feature. A mixer label does not verify records, custody, refunds or privacy, and StableScope does not process the transfer.
