Upbit and Bithumb to Delist STORJ, JASMY and TT After Warning Reviews

Upbit and Bithumb, South Korea’s two largest crypto exchanges, will end trading support for Storj (STORJ), JasmyCoin (JASMY) and ThunderCore (TT) at 15:00 KST on September 14, according to notices posted directly on each exchange. Withdrawals stay open a month longer, until October 14, before access closes for good. The three tokens have almost nothing in common. Storj’s parent company is mid-bankruptcy. ThunderCore spent two weeks publicly arguing with the exchanges before dropping the fight. Upbit X PostTwo Warning Dates, One Deadline Upbit flagged Storj as a trading caution item on July 28. Three days later, on July 31, both Upbit and Bithumb separately designated Jasmy and ThunderCore the same way. Despite the staggered start, the review period for all three converged on the same minute seven weeks later. That matches how Upbit and Bithumb have handled joint delistings before: once DAXA, the industry group the two exchanges use to standardize listing decisions, puts a token on notice, the two platforms tend to move together, reaching independent conclusions on their own schedules rarely enters into it. The Timeline Behind the Delistings July 26: Storj Labs files for Chapter 11 protection. July 28: Upbit designates STORJ as a trading caution item. July 31: Upbit and Bithumb designate JASMY and TT as caution items. August 1: ThunderCore disputes the characterization behind its caution designation. August 14: ThunderCore publishes a follow-up acknowledging that trading support will end. September 14, 15:00 KST: Trading support for STORJ, JASMY and TT ends. October 14: Withdrawal support ends. A Familiar Pattern for Korean Exchanges This sequence has run before. Upbit and Bithumb removed RESOLV within about two weeks of its May warning after the project’s response failed to satisfy reviewers. Flow, Drift, Loopring, Oasys, IoTeX, Groestlcoin and BONK delisting Upbit have each gone through a version of the same warning-then-delisting track over the past year. Wemix has been through it twice: once in December 2022 over disclosure issues, then again in May 2025 after a bridge hack the project was slow to explain, with DAXA saying at the time that the foundation’s response was insufficient to resolve its concerns. Against that history, three tokens hitting the same deadline is routine. ThunderCore Fought the Ruling, Then Accepted It ThunderCore pushed back immediately. In an August 1 statement, the company said it was “surprised and disappointed that certain incorrect public characterizations were made” and that its network “continues to produce blocks normally, validators are operating as expected.” Chief executive Scott Tsai said the team was working to clarify the situation with both exchanges directly. By August 14, the tone had changed.