Ripple has released 1 billion XRP from its escrow accounts for September 2026, continuing its established monthly token release schedule as the XRP price struggles to extend its recent recovery.
The unlock occurred through three transactions involving 500 million, 400 million and 100 million XRP. Ripple’s escrow system allows up to 1 billion tokens to become available at the beginning of each month as part of a supply management mechanism introduced nearly a decade ago.
Ripple initially placed 55 billion XRP into escrow in 2017 to provide greater transparency around the token’s supply. Tokens that are not needed following each monthly release can be returned to escrow and scheduled for future distribution.
Around 32.28 billion XRP remained locked in on-ledger escrow as of August 31. Following the September XRP unlock, the amount is estimated at approximately 31.14 billion tokens. That represents roughly 31% of XRP’s fixed maximum supply of 100 billion.
Importantly, the release of 1 billion XRP does not mean the entire amount will immediately enter circulation or be sold. Ripple has historically returned a significant portion of unlocked tokens to escrow, limiting the amount that ultimately reaches the broader cryptocurrency market.
The latest unlock comes as XRP trades near $1.36, down approximately 0.5% over the past 24 hours. XRP has lost about 8.2% over the past week after approaching $1.70 in August. Despite the pullback, the cryptocurrency remains up roughly 30.8% over the past 30 days and 14.5% over the last 90 days.
Volatility has also affected leveraged traders. About $3.32 million in XRP positions were liquidated during the past 24 hours, including approximately $2.13 million in long positions and $1.19 million in shorts.
XRP’s next move could depend partly on whether market demand can absorb any tokens entering circulation from Ripple’s September escrow release. Strong buying pressure could help XRP preserve its recent monthly gains, while increased supply and weaker demand may keep the token under pressure.
Comment 0