OKX Explains UID Safeguard After Binance Froze 11,398.77 USDT

Binance froze 11,398.77 Tether (USDT) after a customer’s UID transfer reached the wrong account, according to Binance co-founder He Yi (何一). The customer had intended to send the funds to Binance Thailand. Binance co-founder He Yi said: “The transfer reached another account, and Binance froze 11,398.77 Tether (USDT).”

OKX founder Star Xu followed with an operational disclosure. Xu said: “OKX follows a rule requiring globally unique user IDs (UIDs) across its branded sites or blocking internal transfers based only on a UID.” He framed the policy as a safeguard against misdirected funds.

What happened in the Binance transfer?

Binance’s main platform assigns unique UIDs to its users, He Yi said. Its local platforms in Thailand, Turkey and the United States use separate account systems. The customer entered a UID on the main platform while trying to send funds to Binance Thailand. The transfer reached another account.

The customer used the number instead of a wallet address or QR code. The customer also confirmed the transfer without carefully checking the recipient details. The account number supplied the transfer instruction. The confirmation step did not include careful checking of the recipient details.

Neither statement establishes that a main-platform UID is unique across the local platforms. Neither explains how the entered number matched the unintended recipient. Both also leave open whether the frozen USDT was returned to the intended owner or when the freeze occurred.

How does OKX’s rule reduce the risk?

Xu said that if separate OKX sites assign the same UID to different accounts, a transfer using only that number could identify the wrong recipient and send funds to the wrong account. A UID identifies an account. The danger arises when one exchange site’s identifier does not resolve consistently across the exchange’s sites.

The rule has two forms. OKX can require globally unique UIDs across its branded sites. The exchange can also block internal transfers based only on a UID. Under the first approach, the same number does not point to different accounts on separate sites. Under the second, an internal transfer cannot proceed on the number alone.

The practical difference sits inside the transfer workflow. One approach establishes identifier consistency across sites before a customer acts. The other removes the number-only path instead of depending on that consistency.

What should users check before sending funds?

The practical question is simple: does the identifier belong to the platform and account being funded? In the Binance case, the customer used neither a wallet address nor a QR code and did not carefully check recipient details before confirming. OKX’s policy addresses platform-level ambiguity that can send a precise account number to the wrong destination.

Neither statement announces a blanket ban on UIDs. He Yi instead described different account systems across Binance’s main and local platforms. Xu described how OKX handles the same identifier problem. The distinction matters because a UID can be unique within one platform while carrying no guarantee of global uniqueness across separately administered sites.

A UID is an account identifier, not a substitute for reviewing the destination. The customer confirmed without carefully checking recipient details, and the funds reached another account.

Neither statement sets a deadline. The forward-looking market-structure test is concrete: OKX’s sites must either maintain globally unique UIDs or keep internal transfers from relying on a UID alone.