Ripple's September XRP Escrow Cycle Released 1B, Then Re-Locked 700M

Direct answer: September's gross release was 1 billion XRP, while new escrow fell by 300 million

Direct answer: On September 1, validated XRP Ledger records show three Ripple escrow contracts finished for 500 million, 400 million, and 100 million XRP, releasing 1 billion in gross. Later that day, two new EscrowCreate transactions locked 700 million to May 1, 2029. The remaining 300 million moved to a Ripple-labeled wallet, not a proven sale. [1][6][7][8][9][10][11]

[Confirmed fact] That sequence creates three different numbers readers should keep separate: 1 billion XRP became available when the old escrows finished; 700 million became time-locked again in two new objects; and 300 million was transferred outside those two new escrows. The last number is a ledger delta, not a market-flow estimate. [1][4][9][10]

[Editorial boundary] The record does not establish that Ripple sold 300 million XRP, sent it to an exchange, distributed it to institutions, or changed the amount available to unrelated public holders. It establishes transaction types, amounts, accounts, ledger indices, and time-lock dates. Those distinctions are the substance of this report. [1][2][4][11][12]

Section sources[1][2][4][6][7][8][9][10][11][12]

What the validated XRP Ledger records show

[Method] To reconstruct the cycle, I queried Ripple's official s1.ripple.com public server with the tx, ledger, and account_objects methods. Ripple's machine-readable xrp-ledger.toml lists 20 accounts as Ripple Escrow Wallet #01 through #20. I queried each listed account for validated Escrow objects, then summed their Amount fields. This is an AAXRP ledger audit, not a Ripple financial statement. [1][2][3][14][15]

[Confirmed fact] At ledger 106,677,548, which closed at 00:00:02 UTC immediately before the release, 101 active objects contained 32.0 billion XRP. Three EscrowFinish transactions landed together in ledger 106,677,549, closed at 00:00:10 UTC, and removed three objects. The post-finish state therefore had 98 objects and 31.0 billion XRP before the later transfer and re-lock sequence. [1][2][4][6][7][8][14][15]

[Confirmed fact] At ledger 106,694,253, closed at 17:59:21 UTC, a 300 million XRP Payment moved from `r9NpyVfLfUG8hatuCCHKzosyDtKnBdsEN3` to `rBg2FuZT91C52Nny68houguJ4vt5x1o91m`. At ledgers 106,694,439 and 106,694,470, 200 million and 500 million XRP entered self-destination EscrowCreate transactions. Both new escrows carry FinishAfter for May 1, 2029, and each record returned `tesSUCCESS`. [1][9][10][11]

Section sources[1][2][14][15][3][4][6][7][8][9][10]

Why the 700 million re-lock matters more than the headline

[Confirmed fact] Ripple's 2017 announcement created 55 escrow contracts of 1 billion XRP scheduled to expire monthly and said unused XRP would return to the back of the rotation. The September transactions fit that mechanism: the ledger records two new time-based escrows, each with FinishAfter May 1, 2029, rather than another release. [4][5][9][10]

[Bounded inference] For a supply discussion, net escrow reduction is the more informative arithmetic: gross finishes of 1.0 billion minus new time locks of 0.7 billion equals 0.3 billion XRP no longer represented by those active escrow objects. That does not convert automatically into circulating supply because the 0.3 billion first moved to a labeled account whose economic use is not disclosed in the transaction itself. [1][2][3][9][10][11][13][15]

[Independent context] XORA's August 24 audit similarly distinguishes active escrow objects, total supply, Ripple-classified holdings, and estimated circulating supply. TheStreet's September 1 report also cautioned that an unlock alone is not proof of a sale. Those sources support the distinction, but neither can identify what Ripple did with every unit after release. [12][13]

Section sources[4][5][1][15][3][12][13]

What the 300 million transfer does and does not prove

[Confirmed fact] The 300 million transfer was a native XRP Payment from one address in Ripple's listed escrow registry, r9Npy..., to rBg2..., at 17:59:21 UTC. Bithomp labels the destination account Ripple and shows a large XRP balance, but that label is an explorer attribution rather than a new Ripple disclosure. [1][2][3][11]

[Unresolved uncertainty] The transaction does not include a memo naming a sale, market maker, customer, exchange, treasury use, or distribution purpose. On-chain movement can identify where XRP went, but not the commercial agreement behind an address. The most defensible description is 300 million XRP moved from a Ripple-identified escrow wallet to a Ripple-labeled account after the scheduled release. [1][11]

[Implication] Readers tracking supply should treat this as potentially available company-held XRP, not as confirmed public float or realized sell pressure. Traders may watch later transfers to exchanges or named counterparties, but timing alone cannot assign causality to XRP price movements. [3][11][12]

Section sources[1][2][3][11][12]

Why this is not a new XRP supply shock by itself

[Confirmed fact] The XRP Ledger's escrow model makes a gross release a protocol event with a defined lifecycle: EscrowFinish removes an escrow object and delivers its funds, while EscrowCreate establishes a new object with its own conditions. The official documentation does not define either transaction as an exchange sale or a market-order instruction. [4][9][10]

[Bounded inference] The September 1 sequence narrows, but does not eliminate, the supply question. A 300 million outside-escrow balance can support operations, liquidity, incentives, institutional transfers, or other uses. If later records show exchange deposits or disclosed sales, the market interpretation changes. Without that follow-on evidence, the ledger supports availability and custody movement, not realized demand or price impact. [1][3][11][12]

[What the latest snapshot shows] The current audit at validated ledger 106,710,112, closed at 11:06:12 UTC on September 2, found 100 active objects containing 31.7 billion XRP across Ripple's 20 listed escrow accounts. That is a dated snapshot of a labeled address set. It is not the same as Ripple's quarter-end holdings figure, XRP's total supply, or an estimate of public circulating supply. [1][2][3][13][15]

Section sources[4][1][2][3][15][12]

Implications for XRP holders, traders, and XRPL observers

[For XRP holders] The headline event is predictable and partly reversible. The gross 1 billion matters as a maximum scheduled release from three finished objects, while 700 million returned to time lock. Holder-facing risk is not that every unlocked unit must hit an exchange; it is that future use of the remaining 300 million cannot be known from this transaction alone. [4][5][9][10][12]

[For traders] The transaction record is evidence for a supply-monitoring checklist, not a standalone directional signal. A sale thesis would need a dated chain of subsequent transfers, identifiable venue or counterparty evidence, and a contemporaneous market record. A price move near September 1 could have multiple drivers, so this article makes no causal price claim. [1][11][12]

[For developers and researchers] The event demonstrates why account attribution and ledger-object accounting must remain separate. An integration that counts active Escrow objects should query all listed accounts, paginate deterministically, and record the ledger index. A dashboard that subtracts every wallet payment from escrow as if it were public circulation will overstate what the chain proves. [2][3][13][15]

Section sources[4][5][1][2][3][11][12]

Confirmed facts, bounded inference, and unresolved uncertainty

[Confirmed facts] Three validated EscrowFinish records at ledger 106,677,549 total 1 billion XRP. Two validated EscrowCreate records later the same day total 700 million XRP and use a May 1, 2029 FinishAfter. A separate validated Payment totals 300 million XRP. The current 20-account audit records 100 active escrow objects holding 31.7 billion XRP. [1][2][3][6][7][8][9][10][15]

[Bounded inference] The sequence is consistent with Ripple's long-running monthly recycling design and supports a 300 million net reduction in active escrow for this cycle. It does not show the economic destination or sale status of that amount. [4][5][9][10][12]

[Unresolved uncertainty] The reviewed records do not establish whether Ripple sold, distributed, retained, used as collateral, or otherwise allocated the 300 million. They also do not predict XRP price, future re-escrow ratios, or the next month's transaction split. Those questions require later ledger evidence and company disclosures. [1][11][12][13]

[Source precedence] When records conflict, use validated transaction metadata for transaction type, amount, ledger index, and time; Ripple's account registry for official escrow-wallet identification; and independent trackers for corroboration. Use Ripple's 2017 announcement for the original design, not for current holdings or current intent. [1][2][3][5][6][7][8][9][10][11][12][13][14][15]

Section sources[1][2][14][15][3][4][5][6][7][8][9][10][11][12][13]

What to watch next after the September 1 cycle

[Watch the destination] Monitor follow-on Payment transactions from `rBg2...`. A transfer to an identifiable exchange or named institution would change the factual description, but another wallet hop would still not prove a sale without counterparty evidence. [1][11]

[Watch actual escrow objects] Watch for new EscrowCreate records and their FinishAfter dates. For this cycle, only two re-lock records, 500 million and 200 million, were found at May 1, 2029. Counting every transfer to Ripple-labeled addresses as a new escrow would recreate the 1 billion versus 700 million error. [1][3][9][10]

[Watch disclosures] Watch Ripple's next holdings disclosure and next month's validated ledger snapshot. Company-reported distributed and held figures answer a different question from this active-escrow audit. Compare dates only after normalizing time zones and ledger cutoffs. [2][3][5][13][15]

[Watch market data separately] If XRP moves after an escrow event, that is correlation in time until order-book, flow, and macro evidence support a causal explanation. The defensible update path is release, re-lock, wallet use, disclosed sale, then market effect, each with its own record. [1][3][12]

Section sources[1][2][3][11][4][5][12]