22 Coins That Require a Memo or Tag Right Now (Live List From Our Data Engine)

Bottom line first: on one major exchange's public coin API, 22 coin–network pairs currently have the "tag required" flag set (snapshot below). For those coins, sending the right amount to the right address without the memo is the most common way funds go uncredited — the money arrives, but nobody can tell it's yours. This page is the list, dated, with a note on what the list can and cannot tell you.

1. The live list (as of 2026-10-14T14:06:01Z, Bitget public coin API)

Coins whose withdrawal/deposit flow marks a memo (a.k.a. tag / destination / payment ID) as required:

Group	Coins (network)
Major L1s that use shared deposit addresses	XRP (XRP network), XLM (Stellar), EOS, HBAR (Hedera), NEM (XEM), IOST
Stablecoin riding a memo-required chain	RLUSD (on the XRP network)
Smaller / app-chain assets	TLOS (Telos), ABBC, JUNO, WAXP, XPR (Proton), POLYX (Polymesh), XDB, HIVE, BIZA, NADA / PACK / SAUCE (on HBAR), CC (Canton), A (Vaulta)

Three reading notes, in our usual style:

• A stablecoin can still need a memo. RLUSD on the XRP network is the trap in this table: people copy the "USDT-like, no memo" reflex onto a token whose chain (XRP Ledger) identifies accounts by tag. The requirement comes from the chain's deposit-address design, not the token's brand.
• Multiple tokens can share one memo-required chain (NADA, PACK, SAUCE all on Hedera here) — so "my other HBAR token worked without a memo" is not a safe precedent if one of them behaves differently; check per coin.
• HBAR appears four times in the flag set: the base coin plus three tokens on the same chain. If you touch the Hedera network at all, assume a memo until the tool says otherwise.

2. What this list does not say

• It is one exchange's flags (Bitget, from the public coin endpoint). Exchanges occasionally set the requirement differently on their rails — what another exchange requires is not measured here. Use the tool below for the exchange you're actually using once we have its data; until then, treat the chain-level design (section 1) as the default and verify on the deposit screen.
• It is a dated snapshot, not a permanent property. These flags flip when exchanges migrate deposit infrastructure. Our change feed has logged thousands of rule changes in two days; a list without a timestamp is a rumor with good typography — that's why this one is dated and versioned in git.
• needTag = true means the exchange expects a memo; it is not a claim that funds without one are unrecoverable, and it is not a claim that funds with one always arrive. Both directions are the exchange's handling decision. Missing memo — what actually happens and the right recovery order is the honest version of that story, including that recovery is never guaranteed.

3. The process that makes this list unnecessary to memorise

1. Copy the memo from the deposit screen, every time — never reconstruct it from memory or an old transaction. Tags on these chains are typically 7–8 digits (per OKX's help documentation fetched below); a digit typed from memory is a digit that can be wrong.
2. Let the pre-flight check catch it: the transfer self-check flags a missing-tag chain before you sign — the memo error is one of the four fatal categories it exists to intercept (Four things to check before any transfer).
3. First time, to a new destination, send a small test amount before the full transfer. On memo-required chains the test also proves the counterparty's credit process, not just your address.

4. Why this page exists on a site that doesn't hold your money

Because the fee lost to a missing memo is the most avoidable kind: the chain confirms your transfer, nobody disputes it, and it still never becomes yours. The entire defense is a field most people paste in a hurry. If it already happened to you: follow the recovery-order page above, then contact the exchange with the transaction ID, the correct tag, the tag you entered and the amount. We do not promise outcomes.

Next steps

• Mechanism + recovery order: Missing Memo/Tag and Address Poisoning
• The other three fatal pre-transfer errors: Four things to check before any transfer
• Which networks can move your USDT today, and what each costs: USDT withdrawal fees, compared for real

---

Data source and fetch time: the 22-coin flag list, RLUSD-on-XRP grouping, and Hedera token set are from Bitget's public coin API (/api/v2/spot/public/coins, field marking memo requirement per coin–network, fetched 2026-10-14T14:06:01Z; endpoint reachability re-verified live this day). The "7–8 digits, copy exactly as shown, contact support with TxID and both tags" recovery process is from OKX's public help center (fetched 2026-10-12T15:32:51Z). Requirement differences across exchanges: not collected — stated as not measured, not guessed.

Disclaimer: This site provides education and tools, is not investment advice, and we do not guarantee any exchange's crediting or recovery decisions.