XRP's Custody Rollout, Patched Supply Cap and a Single-Fund ETF Inflow

Standard Chartered's DIFC branch holds RLUSD on the XRP Ledger for institutions, while RLUSD collateral use with LMAX stays conditional.

Standard Chartered's DIFC branch in Dubai has begun holding RLUSD on the XRP Ledger for institutional clients, a custody service the bank says operates under the supervision of the Dubai Financial Services Authority. The offering covers the stablecoin issued on Ripple's network — not XRP itself — and marks a further expansion of institutional infrastructure around the ledger.

Separately, the bank is working with Ripple and LMAX Group to make RLUSD usable as collateral for certain LMAX products. That arrangement remains conditional: documentation, testing, regulatory requirements and internal approvals all still have to be satisfied. For investors, the distinction matters. Custody is live; the collateral function is not. The news points to institutional build-out around the XRP Ledger and does not establish fresh demand for XRP, nor does it account for the token's move on the day.

A supply-cap flaw, patched fast

Developers of the XRP Ledger spent yesterday defending their emergency fix for a flaw in the payment system. According to media reports, they bypassed the usual two-week validator voting window to close the risk quickly. Exploiting it would have required deliberately constructed offers; ordinary trading would not have triggered it, the report said.

The vulnerability could have allowed the creation of usable XRP beyond the protocol's 100 billion token ceiling. RippleX fixed it on 25 September in software version xrpld 3.4.1. In a Friday disclosure, the XRP Ledger said it had found no evidence the flaw was exploited on a public network — a caveat that matters, since a technically possible breach of the supply limit is not the same as XRP actually being minted in excess. Security firm Veria Labs said it received Ripple's maximum bug bounty of $250,000 for the report.

The same disclosure covered two other security bugs that had already been remedied, involving the checking of inner batch transactions and the payment engine. Those corrections shipped in the emergency release of 25 September, with no indication of exploitation on a public network.

Batch feature goes live

On the technical front, the XRP Ledger activated its batch amendment on Friday. It allows up to eight transactions to be bundled into a single operation, with all-or-nothing execution available. No named commercial product was live on it at the time of activation.

ETF flows, concentrated in one fund

A demand signal tied directly to XRP came from the US fund market. Roughly $8 million flowed into US spot XRP ETFs on Thursday, according to media reports, with all reported inflows going to Franklin Templeton's XRPZ, which added about 6 million XRP. XRP funds were the only crypto ETF category to post net inflows that trading day, and the other XRP funds saw no money move — a sign of targeted rather than broad demand. Like the custody news, the flows have not been confirmed as the cause of the day's price action.

Macro pressure sets the backdrop

The broader tape was weak. XRP showed a daily change of -2.2% amid a soft crypto market, with media reports pointing to renewed Middle East tensions weighing on the sector the previous day. Coverage framed the selloff as market-wide, citing a sharp drop in South Korean equities alongside $253 million in liquidations of leveraged crypto positions. Other reports flagged rising US Treasury yields, a stronger dollar and uncertainty ahead of the US midterm elections as drags. Bitcoin and other major cryptocurrencies also came under pressure. No standalone XRP headline was identified as the trigger for the selling.

That leaves a split picture for holders: institutional services and network features are being built out, while pending approvals, the narrow base of fund demand and the absence of a confirmed link to the daily move limit what can be read into either the price or the headlines.