May 2, 2025

Ripple Locks Up 700 Million XRP with No Escrow Release in Sight

3 min read

Ripple has once again undertaken its monthly rebalancing operation, moving 1 billion XRP across its wallet ecosystem on May 1, 2025. However, what’s drawing attention this time isn’t just the transfer scale— none of these tokens have been released from escrow for the month, echoing an identical pattern seen just a month prior in April. Strategic Token Distribution Through Ripple Wallets The company initiated the transfer by dispatching 500 million XRP via its Ripple (26) wallet in coordinated movements involving six Ripple-managed addresses. This tranche was split between two internal destinations: 300 million XRP landed in Ripple (1), and 200 million XRP went to Ripple (14), within one minute. Shortly afterward, Ripple (27) activated the second half of the maneuver. At 22:56, it moved 300 million XRP to Ripple (14), reinforcing that wallet’s total with an additional transfer on top of what it had just received. Within minutes, Ripple (27) also sent 30 million XRP to Ripple (15) and allocated another 170 million to Ripple (51), completing the 1 billion XRP distribution. To summarize: Ripple (1) received 300 million XRP, Ripple (14) collected 500 million in two segments, Ripple (15) gained 30 million, and Ripple (51) acquired 170 million. These allocations were finalized within a tight timeframe on the evening of May 1. Escrow Lock Reinforces Token Management Discipline Ripple then took decisive action to secure most of the moved tokens. At 23:01, Ripple (14) locked its entire 500 million XRP into escrow , followed closely by Ripple (15), which placed its full 30 million XRP into escrow a minute later. Ripple (51) mirrored this action at 23:04, sealing away its 170 million tokens. In total, these escrow operations locked up 700 million XRP. Interestingly, Ripple (1), the address that received 300 million XRP, has not transferred its share to escrow—at least not as of press time—leaving room for speculation about its intended use. We are on twitter, follow us to connect with us :- @TimesTabloid1 — TimesTabloid (@TimesTabloid1) July 15, 2023 Pattern Repeats Without May Escrow Unlock Notably, no XRP tokens have been released from escrow for May 2025. This mirrors Ripple’s conduct in April when the company similarly moved 1 billion XRP and re-escrowed 700 million before any scheduled release occurred. In that case, the escrow release followed two days later. Whether this month will follow suit remains to be seen. The re-escrowed 700 million XRP is worth approximately $1.547 billion, based on XRP’s current trading value of $2.21. The entire 1 billion XRP involved in these operations is valued at roughly $2.21 billion. XRP Battles Resistance Despite Broader Market Recovery As the wider crypto market surges, XRP faces resistance near $2.20, amidst Ripple’s current token management efforts. Bitcoin has reclaimed ground above $97,000, signaling a macro-level rebound. Yet XRP’s price has slipped marginally, down 0.08% over the past 24 hours. Ripple’s decision to hold XRP tokens in escrow without a May release might indicate a change in strategy or an attempt to reduce supply and support prices during consolidation. Either way, the firm’s calculated management of its vast token reserves continues to shape market sentiment and supply dynamics. Disclaimer : This content is meant to inform and should not be considered financial advice. The views expressed in this article may include the author’s personal opinions and do not represent Times Tabloid’s opinion. Readers are urged to do in-depth research before making any investment decisions. Any action taken by the reader is strictly at their own risk. Times Tabloid is not responsible for any financial losses. Follow us on Twitter , Facebook , Telegram , and Google News The post Ripple Locks Up 700 Million XRP with No Escrow Release in Sight appeared first on Times Tabloid .

TimesTabloid logo

Source: TimesTabloid

Leave a Reply

Your email address will not be published. Required fields are marked *

You may have missed