Ju Withdrawal Delays Spark ZachXBT Warning As Reserve Questions Grow
Ju is facing renewed user scrutiny after withdrawal complaints, delayed service resumption and fresh questions around the centralized exchange’s reserve structure.
Multiple Ju users reported withdrawal issues over the past week, bringing the East Asian-focused exchange back into the spotlight after earlier warnings around its ownership, sponsorship activity and ecosystem history. The alert did not prove insolvency, but it raised the kind of questions that matter most when a centralized exchange interrupts withdrawals: who controls the platform, what backs user balances, and whether users can exit into liquid assets without friction.
Ju delayed deposits and withdrawals until 12:00 UTC+8 on June 7, 2026, with asset transfers scheduled for the same time and JU/USDT trading set for 16:00 UTC+8. The delay was tied to asset reconciliation, data verification, system security testing and work on a Merkle Tree asset verification mechanism.
The platform had previously planned to restore all services at 20:00 UTC+8 on June 6, after announcing that the first phase of its platform audit had been completed. The revised schedule gave users a new test: whether withdrawals actually resume at scale after the additional verification window.
Reserve Figures Leave Key Backing Questions
Ju currently displays a 123.81% total reserve ratio, $511.64 million in total reserve funds and $413.26 million in customer assets. The same reserve page marks its user verification tool as “Verify (Coming Soon),” which leaves users without a complete public verification path for the claim.
That gap matters because a high reserve ratio is only useful if the reserves are liquid, externally verifiable and backed by assets users can actually withdraw. A separate reserve analysis on X alleged that Ju’s self-reported reserve position may be overstated because a large share appears tied to USDC, USDT and other mapped assets issued on JuChain, without enough public evidence of backing on established chains.
CoinMarketCap’s Ju.com exchange page also lists reserve data as reported directly by the exchange, placing the burden back on Ju to provide clearer custody addresses, backing mechanics, bridge details and independent verification.
For users, the practical question is not whether Ju can display a reserve table. It is whether JuChain-mapped stablecoin balances can be redeemed into widely accepted assets, whether the custody wallets match the liability snapshot, and whether withdrawals keep working under stress.
ZachXBT Revives Earlier Ju Red Flags
ZachXBT first raised concern around Ju in 2025 after JuCoin appeared on TOKEN2049 Singapore’s 2025 Platinum sponsor list. His broader warning was that paid sponsorship status should not be treated as proof of exchange credibility.
That concern now looks more relevant because Ju’s public identity has changed several times. Jubi was rebranded into Joy Universe in 2024, while JuCoin later rebranded into Ju.com in 2025. Rebrands do not prove wrongdoing, but they do increase the need for clear ownership, legal-entity disclosure and custody accountability.
Transparent control is a basic exchange-risk test. Users should be able to identify the operating entity, jurisdiction, management team, custody responsibilities and legal recourse. Ju’s ownership and ultimate control remain hard to verify from public materials, while the alert alleged that the publicly listed team may not represent the actual control structure.
JuDAO And Bybit Links Add To The Risk Narrative
Ju’s wider ecosystem history has also become part of the user-risk discussion. JUDAO suffered an April 2026 exploit on BNB Chain, with Verichains estimating the loss at about $228,000 and tying the root cause to customized liquidity and balance update logic. That incident was separate from Ju.com withdrawals, but it adds context around ecosystem security controls.
The alert also alleged that at least $5 million tied to the Bybit DPRK exploit moved through Ju in 2025. The FBI separately attributed the $1.5 billion Bybit theft to North Korean TraderTraitor actors, while the movement through Ju remains an allegation from the community alert unless confirmed by law enforcement, Ju, or independent blockchain intelligence firms.
JuCoin had previously been reported to have offered 1,000 BTC in industry support for Bybit after the hack. That makes the alleged laundering route especially sensitive, although the two claims should be kept separate unless more direct evidence connects them.
The immediate test is now operational. Ju needs withdrawals to resume cleanly, reserve claims to become independently verifiable, and JuChain-mapped assets to show clear backing. Without that, the withdrawal complaints, reserve questions and ownership concerns will continue to sit inside the same market-risk frame: users are being asked to trust a centralized exchange at the exact moment when trust has become the issue.




Post Comment
You must be logged in to post a comment.