Upbit to End MANTRA Trading on December 14 at 3 p.m.
Key Facts
Bloomingbit’s automated brief, published on November 13, 2026 and linked to Upbit’s announcement, said the platform will end support for MANTRA trading on December 14 at 3 p.m. The date sets a deadline for trading on Upbit, according to the brief’s account of the platform’s announcement. The brief does not specify the time zone for 3 p.m. The published time therefore differs from 06:00 UTC, which appeared in a circulating version of the report. Bloomingbit’s brief gives the time as 3 p.m., without specifying the time zone. (Source: Bloomingbit automated brief on Upbit’s announcement)
Upbit’s policy states that its trading support review committee decides to end support for an asset if the reasons for its placement on the warning list are not addressed, or if the committee considers termination necessary to protect users. After announcing termination, the platform usually allows 30 days for liquidation trading, starting from the announcement date. Withdrawals are also usually supported for 30 days from the end of trading. These rules provide users with a time frame to deal with the asset after a termination decision. Practical details, including withdrawal deadlines for each asset, remain tied to the relevant platform notice. (Source: Upbit policy on ending trading support)
Upbit’s support page says outstanding buy and sell orders are canceled when trading support for a market ends. Withdrawals remain available during the period specified in the platform notice, according to the support center. This distinguishes the halt to trade execution from the continued availability of a withdrawal window after termination. MANTRA holders on the platform therefore need to review the notice details to learn the withdrawal arrangements for the token. The automated brief did not provide separate details on order cancellations or the withdrawal period in this case. (Source: Upbit Support Center and Bloomingbit brief)
The MANTRA announcement comes amid earlier tensions surrounding the security incident covered by TokenPost in a report published on November 7. The report cited a post-incident review saying an attacker exploited a vulnerability in a Cosmos EVM module and transferred about 721 million MANTRA tokens. It said about 121 million tokens of the transferred amount came from a multisignature address linked to an incentive campaign. In its official review, MANTRA attributed the flaw to the balance-accounting layer of an external software dependency used by the chain. The company estimated the total transferred at 720,923,967.99 tokens, worth about $3.6 million, calculated using a price of $0.005 per token at the end of the day on August 20 UTC. (Sources: TokenPost and MANTRA’s post-incident review)
MANTRA said the incident did not result in balances being deducted from customer accounts, customer balances held at trading platforms, deposit addresses or application contracts. In its update through August 28, the company said it had recovered no tokens and that about 37.96 million tokens remained in the attacker’s account, frozen because of the chain’s halt and account restrictions. The company’s review also warned that moving about 600 million tokens from the burn address could increase circulating supply as reported by some data providers, without meaning that new tokens had been created. These details place the questions of supply and frozen tokens in the background of the ongoing discussion around MANTRA. (Source: MANTRA’s post-incident review)
In a related governance development concerning the frozen tokens, TokenPost reported on November 7 that MANTRA Proposal No. 40 was open for a vote on a plan to recover 37.96 million tokens. The report set Friday, November 13, 2026, as the end date for voting. The proposal concerns the amount MANTRA said in its update through August 28 remained in the attacker’s account, linking the discussion of its recovery to the fallout from the security incident. Upbit’s decision sets the end of trading for December 14 at 3 p.m., according to Bloomingbit’s brief. (Sources: TokenPost and Bloomingbit brief)