Three separate events have pushed XRP's supply into the spotlight in the same week. Blockchain investigators traced about $296 million in XRP stolen from Binance on 29 October. Over the same days, the exchange's XRP balance fell to its lowest level since 2022. Then, on 1 November, Ripple's scheduled monthly unlock released 1 billion XRP from escrow. Each event affects how much XRP could reach the market, but in quite different ways, and the headline numbers can mislead if you read them in isolation.

How the XRP theft unfolded

According to transaction tracing by TRM Labs reported by Bitcoin.com News, XRP was the first asset taken in the Binance breach. Between 20:05 and 20:09 UTC on 29 October, five Binance wallets sent a combined 233.46 million XRP to one attacker address.

Each wallet was left holding only its account reserve. This is the minimum XRP an XRP Ledger account must keep, and it cannot be moved with an ordinary payment. Xrplwin, an XRP Ledger explorer, timed the sequence at four minutes and 20 seconds. The first transfer alone made up about 79% of the total.

Glassnode and Arkham agree that XRP came first. Arkham says the attacker then moved about $6 billion in 141 transfers across nine blockchains between 20:10 and 23:05 UTC. TRM found the XRP transfers were ordinary signed transactions, which points to compromised signing keys rather than a flaw in the XRP Ledger itself.

Ripple could freeze RLUSD, but not XRP

Ripple's dollar-backed stablecoin, RLUSD, was also stolen. Stablecoin issuers can block transfers at specific addresses, and Ripple used that power. TRM confirmed that Ripple froze 40.5 million RLUSD on Ethereum at 22:01 UTC on 29 October. It also restricted RLUSD held in the compromised Binance wallet to stop further transfers out.

The freeze came too late for part of the haul. The attacker had already sold 48 million of the 88.5 million RLUSD taken.

XRP works differently. It is the ledger's native asset, and no issuer can freeze it. Getting it back depends on tracing the funds and on exchanges or other services blocking them if the attacker tries to cash out. Blockchain analytics firm Elliptic reported that the stolen XRP had not moved as of 05:00 UTC on 31 October.

Binance says it has set aside more than $6.34 billion from its user protection fund and corporate treasury to cover losses. In an 31 October update, it said XRP and nine other assets were "fully backed 100%", with 90% of losses replenished overall. It kept 1 November as its target date for reopening withdrawals.

Binance's XRP balance hit a 2022 low, but the timing matters

U.Today, citing CryptoQuant data, reported that Binance's XRP reserve fell from 2.69 billion on 28 October to 2.47 billion on 30 October. That is a drop of about 220 million XRP, or roughly 8.2%, and the lowest level since December 2022. Smaller declines appeared at Bybit (306 million to 286 million) and Bithumb (1.847 billion to 1.837 billion).

Falling exchange balances are often read as a sign that buyers are moving coins into their own wallets, leaving less available to sell. U.Today presented the data that way, but also warned that lower balances do not always mean investors are accumulating.

That warning matters here. The two-day window includes the hack. Binance lost 233.46 million XRP on 29 October, which is close to the 220 million fall in its reserve. Neither source connects the two figures, and the CryptoQuant numbers as reported don't separate stolen coins from customer withdrawals. Binance has also said withdrawals were paused while it restored its systems. Taken together, much of the drop may reflect the theft rather than demand. If Binance replenishes its XRP holdings, the reserve figure could rise again.

What the 1 billion XRP escrow release does

Ripple first locked 55 billion XRP in escrow and releases it on a set schedule so that supply enters the market predictably. Whale Alert recorded two unlocks of 500 million XRP each in the early hours of 1 November. U.Today's report valued each at about $626.4 million. Bitcoinist put the total at about $1.25 billion.

An unlock does not mean 1 billion XRP is sold. In past months, Ripple has returned about 700 million XRP to escrow. It keeps the rest for operations, liquidity and ecosystem activities. Bitcoinist also notes that the net effect on circulating supply depends on how much is locked back up.

Putting the supply picture together

The three stories pull in different directions, and none settles the question of selling pressure.

  • Stolen XRP: 233.46 million XRP is held by one attacker and cannot be frozen. It is a potential source of sudden selling if it moves to services that don't block it. For now, it has been reported as unmoved.
  • Exchange reserves: The lower Binance balance looks like less supply on offer. But the overlap with the theft and the withdrawal pause make it a weak signal of buying this week.
  • Escrow: The gross 1 billion unlock overstates the likely addition to circulation. Past practice suggests around 300 million XRP stays out, but this month's actual figure is not yet known.

U.Today also notes that XRP's price has stayed volatile and has not reacted to the shrinking exchange supply. That fits with a market treating these signals with caution.

What to watch

  • Binance withdrawals: whether the 1 November reopening target holds and whether XRP flows out sharply once withdrawals resume.
  • Proof of reserves by 3 November: Binance expects to publish a full zero-knowledge proof for ten assets, including XRP and RLUSD. These proofs let users confirm their balances are included in the reported totals without revealing anyone else's details.
  • The attacker's XRP address: any movement of the 233.46 million XRP, and whether exchanges intercept it.
  • Escrow re-lock: how much of the 1 billion XRP Ripple returns to escrow this month compared with the roughly 700 million seen before.
  • XRP Ledger upgrade: the fixCleanup3_4_0 amendment could activate at 14:46 UTC on 4 November at the earliest. Validator support must stay above 80% for two weeks, or the timer resets.