NewsCryptoRipple CEO Brad Garlinghouse Urged to Burn 31.1 Billion Escrowed XRP

Ripple CEO Brad Garlinghouse Urged to Burn 31.1 Billion Escrowed XRP

Author: Coincentral·

Key Takeaways

  • •XRP Insights recorded 31.1 billion XRP across 99 escrow objects linked to eight Ripple-related accounts on November 16.
  • •Ripple reported 31.7 billion XRP in escrow on September 30, and its November cycle reduced the balance by 300 million XRP after 700 million tokens were re-locked.
  • •The current schedule makes 1 billion XRP releasable monthly from December 2026 through March 2027, while 27.1 billion XRP would remain locked afterward.
  • •Escrowed XRP cannot be destroyed before its conditions are satisfied under existing XRP Ledger rules.
  • •No independently established Ripple authorization or implementation method exists for burning the targeted balance.
Ripple CEO Brad Garlinghouse Urged to Burn 31.1 Billion Escrowed XRP

An XRP commentator has publicly called on Ripple to destroy its entire escrow balance — 31.1 billion XRP — by the first quarter of 2027. The demand, set out in a letter published on November 16 and addressed to CEO Brad Garlinghouse, targets the company's time-locked holdings, which are released in monthly cycles with unused tokens returned to new contracts. The proposal runs into an immediate constraint: XRP Ledger rules bar holders from destroying assets while escrow conditions remain unsatisfied, meaning the demand collides with an existing release timetable.

The idea quickly drew skepticism on social media:

Imagine asking a company to destroy an asset valued at $30 billion, believe they would ever do it, and expect to be viewed as sane — bill morgan (@Belisarius2020) November 16, 2026

Tracker Data Shows 31.1 Billion XRP Still Locked

On November 16, XRP Insights recorded 31.1 billion XRP locked across 99 escrow objects, held by eight Ripple-linked accounts. The holdings amount to 31.1% of XRP's original 100 billion supply. Because escrow objects are recorded on the public XRP Ledger, locked balances can be verified directly by third parties rather than relying solely on company disclosures, though the tracker's figures capture a snapshot of ledger escrow objects rather than Ripple's most recent quarterly disclosure.

Ripple's own reporting put the escrow balance at 31.7 billion XRP as of September 30. On November 1, the company's monthly cycle released 1 billion XRP and returned 700 million to new escrows, a net decrease of 300 million XRP. A release does not by itself prove tokens were sold: the figures describe contract movements, not verified trading activity.

According to the tracker, another 1 billion XRP becomes releasable on December 1. January, February and March 2027 each carry an additional 1 billion, leaving just 4 billion XRP eligible for release across those four months under the current schedule. The re-lock mechanism is what keeps that calendar so gradual: as November's cycle showed, returned tokens extend the timetable instead of leaving the locked balance all at once.

Ledger Rules Complicate the Proposed Burn

XRPL documentation states that escrowed assets cannot be used or destroyed before their conditions are met. On that basis, 27.1 billion XRP are scheduled to remain locked beyond March 2027. That calculation assumes the present timetable and no new lockups, and it excludes any hypothetical protocol changes.

Burning and unlocking produce different outcomes. XRP transaction fees are destroyed permanently, reducing total supply, while unlocking simply transfers existing tokens from escrow to an account without reducing supply. A blackholed account renders XRP inaccessible without destroying tokens through transaction fees.

Ripple introduced the escrow structure in 2017, placing 55 billion XRP into time-locked contracts to make token releases more predictable. The stated design initially allowed 1 billion XRP per month, with unused tokens returned to later escrows — a distinction illustrated by November's 700 million re-lock.

The letter offers a deadline but not a confirmed implementation method, and no company decision authorizing a 31.1 billion XRP burn has been independently established. Under the current timetable, most of the targeted assets cannot become accessible by the requested quarter. Ripple would need to explain a different mechanism before the proposal could become executable. For now, the idea stands as commentary rather than an actionable plan. From here, the observable markers are the escrow schedule itself and any response from Ripple to the letter.

This article originally appeared on CoinCentral.