9dd2be61-a
XRP Holders Seek 31.1 Billion Token Burn From Ripple
XRP holders want Ripple to burn 31.1 billion escrowed tokens by March 2027, but no company commitment and existing ledger conditions leave the proposal unexecuted.

Outputs
A Nov. 16 open letter seeks a permanent burn of 31.1 billion XRP by March 31, 2027.
Ripple locked 55 billion XRP into escrow in December 2017, with releases of up to 1 billion XRP monthly.
Ripple disclosed 31.7 billion XRP in escrow as of Sept. 30.
Ripple released 1 billion XRP on Nov. 1 and returned 700 million tokens to escrow.
Bill Morgan values the proposed burn at approximately $30 billion and questions its feasibility.
XRP holders have asked Ripple to permanently burn 31.1 billion escrowed XRP by March 31, 2027, according to a Nov. 16 open letter from the Make XRP Great Again movement. The proposal seeks a lower supply and addresses complaints that Ripple’s corporate growth has not produced meaningful gains for token holders. Ripple has made no commitment to the request.
Addressed to Ripple CEO Brad Garlinghouse, the letter also demands a public response from Garlinghouse and Ripple’s leadership. It requires a verifiable execution plan covering the legal and technical steps needed to meet the deadline, rather than another temporary release-and-re-escrow cycle.
What does the campaign want from Ripple?
The group said XRP holders supported Ripple through years of regulatory uncertainty, including its legal battle with the U.S. Securities and Exchange Commission. The letter also pointed to expanding partnerships, acquisitions and international operations, arguing that the escrowed balance remains a source of investor frustration despite those developments.
The campaign stated: “We are asking for a decisive and permanent action that directly aligns Ripple’s ongoing success with the interests of XRP holders.” Its earlier Nov. 10 open letter had sought greater transparency on how Ripple’s commercial success could benefit investors.
In plain terms, the campaign wants a written company commitment, not merely another statement of intent.
Why has the proposal drawn resistance?
Australian lawyer and longtime XRP commentator Bill Morgan opposed the idea, questioning why Ripple would voluntarily destroy assets worth approximately $30 billion. He wrote on X: “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.”
Concerns about insider holdings form part of that backdrop. Earlier this year, crypto.news reported that Ripple and its executives had sold or distributed approximately 58.5 billion XRP since 2012, based on an analysis of historical allocations and on-chain holdings. Ripple CTO Emeritus David Schwartz later disclosed that his personal holdings fell from about 26 million XRP to 3 million.
The letter did not establish a causal link between those sales, escrow balances and XRP’s value. Nor did it address why holders should accept destruction of company assets without contractual or governance terms.
Takeaway: The demand rests on investor dissatisfaction, while its central economic assumption remains unproven.
Can Ripple meet the March 2027 deadline?
Ripple introduced its escrow system in December 2017, locking 55 billion XRP into time-based contracts. Under the arrangement, up to 1 billion XRP becomes available each month, and Ripple regularly returns a large portion of released tokens to new escrow contracts.
On Nov. 1, Ripple unlocked 1 billion XRP through two transactions of 500 million tokens each. It then returned 700 million XRP to escrow, continuing the established release pattern. Ripple’s official holdings disclosure listed 31.7 billion XRP in escrow as of Sept. 30, while the campaign letter used a lower remaining balance of 31.1 billion; the letter did not reconcile the difference.
XRP Ledger documentation states that escrowed tokens remain locked until specified release conditions are met. Ripple cannot simply withdraw the entire balance ahead of schedule and destroy it, which makes the proposed March 2027 completion dependent on how existing contracts run.
The company could stop returning newly released XRP to escrow, but that step would not immediately eliminate tokens already locked under later release dates. A previous XRP ETF filing raised similar release questions, with Morgan challenging claims that Ripple might change distribution practices following regulatory developments. The source identifies no contract amendment or other executable route to an early burn.
Takeaway: The March deadline lacks a disclosed burn mechanism under the stated escrow rules.
Does Ripple’s institutional expansion change the calculation?
The campaign arrived while Ripple continued building institutional services around XRP, its RLUSD stablecoin and the XRP Ledger. On Nov. 10, Ripple expanded its BNY partnership to support institutional custody of XRP and RLUSD, while working with C2FO on tokenized trade finance.
Ripple’s Nov. 16 recap of its Swell 2026 conference highlighted tokenized money market funds, settlement infrastructure and institutional blockchain adoption. Those developments do not answer the escrow question: the source records no public response from Garlinghouse, no burn authorization and no timetable for changing existing contracts.
Market conditions supplied additional context rather than a technical answer. XRP traded near $0.95 on Nov. 15 after falling more than 15% over the preceding week and slipping below $1, despite the company’s broader expansion. No cited document connects that decline to the proposed burn or escrow releases.
Takeaway: Institutional expansion continues, while token supply remains governed by contracts Ripple cannot simply cancel.
The next verifiable checkpoint is a public Ripple response before March 31, 2027. Without a credible legal and technical execution plan, the 31.1 billion XRP burn remains an investor demand, not a scheduled market-structure change.
via crypto.news (Source)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,576 articles