Reserve to Pull LCAP, CMC20 Liquidity From MEXC After FinCEN Order

By Elena Vasquez

Reserve said it plans to withdraw liquidity support for LCAP and CMC20 from MEXC Global after the U.S. Financial Crimes Enforcement Network (FinCEN) alleged in an order that the exchange facilitated at least $16 billion in illicit transactions. The withdrawal covers Reserve and its market-making partners and applies only to the exchange.

Reserve did not disclose the amount of liquidity involved, the size of its market-making exposure or a fixed withdrawal date. It also said the change does not amount to a broader halt for either token.

Takeaway: Reserve is removing its own exchange-specific liquidity rather than abandoning support for LCAP or CMC20 across the market.

What does the FinCEN order cover?

FinCEN’s order alleges that MEXC Global facilitated at least $16 billion in illicit transactions. Reserve cited that order as the reason for its planned withdrawal and said the action “effectively cuts the exchange off from the U.S. financial system.”

The allegation includes activity related to evading Iran sanctions, according to Reserve’s account of the order. The announcement did not reproduce the order, specify its statutory basis or identify any monetary penalty, compliance deadline or final finding of liability.

Reserve based its withdrawal plan on that interpretation without disclosing further legal details. The omission prevents readers from determining the full scope or duration of FinCEN’s action from the source.

Takeaway: The $16 billion figure is an allegation stated in the order, not a Reserve estimate or an amount the announcement calculates as illicit proceeds.

What changes on MEXC?

Reserve and its market-making partners will stop supporting the two tokens on MEXC and soon withdraw the funds connected to that activity. Reserve said: “The planned change is specific to MEXC.”

The direct operational consequence is the removal of Reserve-backed liquidity for both token pairs on that venue. Reserve did not say whether other providers would remain, how deep the exchange’s order book would become or by how much trading activity could change.

The source also did not identify the blockchains, token contracts or token standards underlying LCAP and CMC20. It therefore supports no conclusion about on-chain mechanics or contract-level effects, and it offers no order-book or trading-volume data from which to calculate the immediate consequence.

Takeaway: The announcement removes named market-making support from one exchange, not from other venues or from the tokens themselves.

Will other venues be unaffected?

Reserve said: “Liquidity for LCAP and CMC20 on other venues, including on-chain markets, will not be affected.” That statement confines the announced action to MEXC; it does not announce a broader suspension of Reserve’s support for either asset.

The assurance remains a company statement. Reserve supplied no exchange-by-exchange liquidity figures, trading-volume comparison or independent confirmation of remaining support, so the source cannot show how much liquidity would remain available if MEXC activity changed.

Without those data, the announcement cannot establish whether participants would redirect orders, whether other venues could absorb any change in trading flow or how the withdrawal would affect price discovery. Reserve offered no evidence for any of those outcomes.

Takeaway: Other venues appear unaffected by design, but the announcement does not quantify the liquidity remaining there or the market effect of the MEXC withdrawal.

What is still unknown?

The source leaves several material questions unanswered:

• How much liquidity Reserve and its partners supplied for LCAP and CMC20 on MEXC.
• When the connected funds will leave, beyond Reserve’s statement that the withdrawal will happen soon.
• Whether FinCEN imposed a specific deadline, penalty or set of compliance conditions.
• How MEXC responded to the order and Reserve’s decision.
• Whether other venues will retain the same trading depth after activity changes on MEXC.

These omissions do not negate the announced plan, but they constrain any assessment of its scale. Reserve described a withdrawal of its liquidity program, while the order alleges broader misconduct at MEXC; the source does not establish that the private pullback measures the alleged activity.

Takeaway: The announcement establishes a planned venue-specific pullback, not a completed withdrawal or a measured market impact.

What should readers watch?\n

Readers should watch for the actual fund removal, any FinCEN publication that clarifies the order and any MEXC response or change in third-party liquidity. The announcement provides no schedule beyond its promise of a soon withdrawal, so execution will carry more evidentiary weight than the initial plan.

Takeaway: The next verifiable checkpoint is the promised near-term withdrawal, because Reserve disclosed neither a calendar deadline nor evidence that connected funds had already left MEXC.