Loading prices…
〽️NEUTRAL

Revolut App Briefly Shows BTC Near 2 Cents as Users Report Glitch

The wick never printed on CoinGecko or CoinMarketCap, so the question for traders isn't whether BTC fell — it's whether a single retail venue filled orders at a price no other exchange ever saw.

Revolut App Briefly Shows BTC Near 2 Cents as Users Report Glitch
Revolut App Briefly Shows BTC Near 2 Cents as Users Report Glitch
Revolut App Briefly Shows BTC Near 2 Cents as Users Report Glitch
Revolut App Briefly Shows BTC Near 2 Cents as Users Report Glitch

Revolut users briefly saw bitcoin trade far below global market levels on Friday, with some screenshots showing the app marking BTC around £29,400 and others claiming near-zero prints as low as 2 cents before the display snapped back near £58,600. Spot bitcoin on major venues tracked by CoinGecko and CoinMarketCap held just over $79,000 during Asian afternoon hours, with no anomaly registering on any aggregated feed. Revolut had not responded to a request for comment by publication time, leaving unconfirmed user reports of filled buy orders at the aberrant levels in limbo.

Why it matters

A wick on one retail app that no other exchange ever printed is the textbook signature of a venue-side dislocation rather than a market move. The most common causes are thin internal liquidity, a stale quote from an upstream pricing rail, or a display bug that decouples the chart from the matching engine. Revolut's official one-day chart showed a single sharp dip to roughly £29,400 before recovering — half of the spot level on the same time axis — which is consistent with a brief quote refresh failure rather than a real order sweeping a book. Similar dislocations have hit Binance's USD1 pair in December and South Korean venues during the 2024 martial-law shock, where thin local books broke from global pricing for minutes at a time.

Market impact

The tradable read is narrow: no cross-exchange arbitrage opened because no other venue ever saw the price, so the dislocation did not move spot, futures, or ETF flows. The unresolved question is execution-side — if Revolut's matching engine actually filled buy orders at sub-market levels, the platform will need to decide whether those prints are honoured, reversed, or settled at a reference price, and that decision will set a precedent for every other retail-brokerage pricing anomaly that follows.

Related tokens
$BTC

Frequently asked questions

  1. Did bitcoin's price really drop to 2 cents on Revolut?

    No. Spot bitcoin on CoinGecko and CoinMarketCap held just over $79,000 during the same window, and no aggregated feed registered any anomaly. The near-zero prints appeared only on the Revolut app and were never independently verified by CoinDesk.

  2. Why did Revolut show such a low BTC price if no other exchange did?

    Isolated single-venue wicks are typically caused by a stale upstream quote, a thin internal liquidity rail, or a display bug that decouples the chart from the matching engine. Revolut's official one-day chart showed BTC briefly at ~£29,400 before snapping back near £58,600, half of spot on the same time axis.

  3. Did any trades actually execute at the glitched prices?

    Unconfirmed user posts on X claimed buy orders were filled at the aberrant levels, but CoinDesk could not independently verify the claims. Revolut had not commented on the incident by publication time, so execution status remains unconfirmed.

  4. Has this kind of pricing glitch happened before on other platforms?

    Yes. Binance's USD1 pair briefly printed far below market in December, and South Korean exchanges saw sharp local wicks during the country's 2024 martial-law shock when order books broke from global pricing for minutes.

  5. What happens if Revolut filled orders at the wrong price?

    The platform will need to decide whether to honour those prints, reverse them, or settle at a reference spot price. That decision will set a precedent for how future retail-brokerage pricing anomalies are handled.

Source attribution
Aggregated from CoinDesk · Verified · Last refreshed 48d ago
Open original →