Key Takeaways
- • Bitwise Asset Management's XRP position has surpassed $500 million according to an SEC filing, placing the firm among the largest institutional holders of the token through a regulated fund structure.
- • The spot structure requires funds to hold actual tokens rather than derivatives, so rising AUM translates directly into real token demand from institutional vehicles.
- • The $500 million figure is a point-in-time valuation that moves with XRP price and net flows, and it does not by itself confirm sustained net inflows.
- • Bitwise's Solana staking ETF (BSOL) was the first product in its category to top $1 billion in assets under management.
- • Separately, ACINQ released Eclair v0.14.4, a security patch for its Lightning Network node that blocks cross-origin request forgery attacks; no exploitation has been publicly reported.
Summary
The milestone arrives as the broader category of spot Ripple ETFs has sustained momentum through 2026. Because spot products must hold actual tokens rather than derivatives, the structure broadens the buyer pool to include pension funds, registered investment advisors, and brokerage account holders who cannot or will not custody crypto directly. Bitwise has followed a similar pattern across other Layer 1 assets. Its Solana staking ETF, trading as BSOL, became the first product in its category to top $1 billion in assets under management. The firm has also filed products tracking Chainlink and NEAR, and its NEAR ETF began trading on NYSE Arca. Institutional participants including UBS and Jane Street have taken positions in crypto ETF products at scale. Spot Bitcoin ETFs recorded $685 million in a single day of inflows earlier in 2026, according to the same coverage.
Separately, ACINQ released Eclair v0.14.4, a security update to its Bitcoin Lightning Network node implementation. The release addresses cross-origin request forgery at the API layer, which could allow a malicious webpage to send commands to a locally accessible Eclair API endpoint. An attacker could potentially open or close payment channels, probe channel balances, or manipulate routing policy, depending on which endpoints are reachable, without needing to steal private keys. Operators who expose their API on a non-loopback interface face higher risk. ACINQ reports the issue is patched and there is no confirmed public report of exploitation in the wild. Operators and developers with browser-facing integrations should review their deployed version against the v0.14.4 release notes on GitHub. ACINQ signs its releases and provides PGP verification material.
Go deeper than the headline
Research every firm in this story, track the ones that matter and get the daily briefing — free for 7 days.