April 24, 2025
Blockchain

Bithumb and Upbit Allow Litecoin Removal After MimbleWimble Update

  • May 23, 2022
  • 0

Bithumb and Upbit, one of the largest crypto exchanges in South Korea, issued warnings to users about Litecoin (LTC) after the MimbleWimble Extension Block (MWEB) update. On May

Bithumb and Upbit Allow Litecoin Removal After MimbleWimble Update

Bithumb and Upbit, one of the largest crypto exchanges in South Korea, issued warnings to users about Litecoin (LTC) after the MimbleWimble Extension Block (MWEB) update.

On May 20, the Litecoin mainnet activated a protocol with broad scalability and increased privacy. It uses a variety of technologies, including confidential transactions and CoinJoin, which hides the inputs and outputs of senders and receivers and combines many transactions into a single transaction.

Exchanges emphasized that they operate in accordance with local legislation. It requires the implementation of measures to combat money laundering and terrorist financing.

According to Bithumb, its policy is to delist an asset if it “violates the law, government or financial regulations.” Upbit made a similar statement.

Big Four exchanges Korbit and Coinone have yet to issue warnings.

According to CoinGecko, at the time of this writing, LTC is ranked 18th in the ranking of the largest crypto assets by $5.1 billion capitalization.

In June 2021, Upbit delisted Paycoin, Maro, Observer, Solve.Care, and Quiztok. At the same time, Coinbit stopped circulation of eight “risky” assets and added 28 more to the list, with a warning to investors.

Previously, several trading platforms stopped trading privacy-focused coins. At the beginning of 2021, the Bittrex exchange announced the delisting of Zcash (ZEC), Dash (DASH) and Monero (XMR). A similar decision was made at ShapeShift.

Recall that Litecoin developers announced in February 2022 that MWEB is ready. In March, they placed a new version of the Litecoin Core 0.21.2 client on the testnet, which includes the MWEB and Taproot updates.

Source: Fork Log

Leave a Reply

Your email address will not be published. Required fields are marked *