XRP Declines Despite $3.14 Million Inflows Into U.S. Spot ETFs
XRP fell from about $1.52 to $1.46 on Oct. 6 as cumulative ETF inflows reached approximately $1.794 billion.

XRP traded near $1.45 on Oct. 7 after falling from about $1.52 to $1.46 on Oct. 6, even as U.S. spot XRP exchange-traded funds recorded $3.1404 million in net inflows during the session.
The move from $1.52 to $1.46 at about 10 p.m. ET (2 a.m. UTC on Oct. 7) represented an approximately 3.9% decline. The percentage can vary depending on the measurement window and timestamp. XRP had closed around $1.50 on Oct. 6 in daily data recorded in UTC.
Bitwise’s XRP fund led the daily ETF flows with $10.5514 million in inflows. Franklin’s XRPZ recorded a $4.0702 million outflow, while other funds accounted for the remaining withdrawals.
U.S. spot XRP ETFs had accumulated approximately $1.794 billion in net inflows, with total net assets of about $1.697 billion as of the Oct. 6 data. The timing shows that positive fund flows and XRP’s subsequent decline occurred during the same period, but it does not establish that ETF activity caused the price move.
Spot XRP ETFs provide exchange-traded exposure to XRP without requiring investors to hold the asset directly. Daily net-flow figures reflect creations and redemptions across the funds, and positive aggregate flows do not guarantee a rise in XRP’s market price.
EGRAG Crypto identified $1.40 as support and $1.4850 as resistance in a technical scenario. “$1.40 holds + daily close back above $1.4850 → strong chance this breakdown becomes a FAKEOUT,” EGRAG Crypto wrote Oct. 7. The levels are analyst scenarios, not confirmed price targets.
A separate institutional-market event is planned for later this month. Evernorth Holdings expects its business combination with Armada Acquisition Corp. II to close on or about Oct. 9, subject to closing conditions and listing requirements. Trading under the ticker XRPN on Nasdaq is expected to begin on or about Oct. 12.
The XRP Ledger’s version 3.4.1 upgrade introduced the fixBatchV1_2 amendment, which is expected to activate on Oct. 9 if validator support remains above the required threshold. The amendment had already gained support from a supermajority of validators.