Skip to content
Independent XRP reference
Our standards

Source verification required

XRP escrow tracker and schedule reference

Ripple's original escrow program placed 55 billion XRP into time-based contracts and scheduled up to 1 billion XRP to become available each month. An unlock does not prove that XRP was sold. This reference shows how to verify the actual ledger events without presenting estimates as live data.

Reviewed

Current reference status

This is not a live balance tracker.

The previous version relied on a hard-coded 2025–2026 table and an unverified balance. Those figures have been removed. This reference now stays useful by showing the published schedule, the next calendar boundary, and the primary records needed to verify actual ledger events without inventing a live remaining balance.

XRP escrow in brief

Initially placed in escrow
55 billion XRP
Published monthly structure
Up to 1 billion XRP
What an unlock proves
Availability, not a sale

How the schedule works

Ripple placed 55 billion XRP into on-ledger escrow in 2017. The published structure used monthly escrow expirations, with up to 1 billion XRP becoming available at the start of a month. Unused amounts could be placed into new escrows at the end of the queue.

The next calendar month starts on October 1, 2026. That date is a schedule reference, not confirmation of a particular transaction or net release. Verify actual escrow finishes and subsequent transfers on the ledger.

An escrow finishing is not the same as XRP entering circulating supply or being sold. Establishing that requires tracing the destination and later transactions; a monthly unlock figure alone cannot support the claim.

How to verify a monthly release

  1. 1. Locate the validated EscrowFinish transaction. Use an XRP Ledger explorer or API and confirm the transaction is in a validated ledger.
  2. 2. Match the escrow object. Check the Owner and OfferSequence fields so the finish can be tied to the original EscrowCreate transaction.
  3. 3. Confirm the amount and destination. Read the original escrow object and trace the account that received the finished escrow.
  4. 4. Look for new EscrowCreate transactions. XRP that is not used may be returned to the end of the escrow queue in new contracts.
  5. 5. Keep unlocks separate from sales. A sale claim requires evidence from subsequent transactions or current reporting, not only an EscrowFinish.

Escrow questions

When is the next XRP escrow release?

Ripple's published structure uses escrow finishes at the start of each calendar month. The exact finish time, amount made available, and amount later returned to escrow must be verified from current XRP Ledger transactions.

Is this a live XRP escrow balance?

No. This page explains Ripple’s published monthly escrow schedule. It does not currently query every escrow object on the XRP Ledger, so it intentionally does not display a live remaining balance.

What happens to XRP that Ripple does not use?

Ripple has stated that unused XRP from a monthly release is returned to new escrow contracts. The exact amounts should be verified from ledger transactions or Ripple’s current reporting rather than assumed from a historical average.

Does an escrow release automatically enter the market?

No. An escrow finishing makes XRP available to its destination, but that event alone does not show whether the XRP was sold, transferred, held, or placed into another escrow.

How much XRP remains in Ripple escrow?

This page does not publish a fixed current balance because a reliable total requires identifying the relevant accounts and summing current ledger escrow objects. Verify the ledger and Ripple's latest reporting instead of relying on a stale estimate.

How do I verify an XRP escrow release?

Find the validated EscrowFinish transaction, confirm its owner account and offer sequence, trace the destination, and then look for related EscrowCreate transactions if XRP was placed back into escrow. A finish alone does not prove a sale.

Primary sources

Use these first-party references to verify protocol details and time-sensitive platform information.