Observing the potential for duplicate UIDs across Binance's global and multiple local sites, I've come to the conclusion that from a product designer's perspective, a good product architecture leaves no room for user error. This issue indeed stems from a lack of rigor in Binance's product design. Simply changing from "two confirmations" to "three confirmations" won't fundamentally solve the problem unless the underlying issue of non-unique UIDs across sites is addressed. Once someone has already gone down the wrong path, reminders along the way are useless. Similarly, from a company management perspective, good risk control and access management mean denying frontline employees, especially those with transfer permissions, the opportunity and space to make mistakes. When someone makes their first transfer via UID, I send a screenshot (as shown in the image) containing the UID, username, and avatar to the recipient for confirmation before proceeding. If the provided UID is from Binance US or the Binance TH independent site, the avatar and username will be different, which helps identify problems during the confirmation process. Binance Square's in-app promotion of user-generated content (UGC) has had some effect on popularizing customizable avatars and nicknames. However, its impact is limited; I've noticed many users still use the default avatars and nicknames. If I transfer money to a friend and find their nickname in the default format (User-8fc6e), I'll suggest they change it to something more easily identifiable. After one transfer, they can easily find the nickname in the chat list next time, without needing to enter the UID again.