David Schwartz, Honorary Chief Technology Officer of Ripple, confirmed his continued participation in the XRP project
David Schwartz, Honorary Chief Technology Officer of Ripple and one of the original architects of the XRP ledger, recently stated that although he has resigned from his original position at Ripple, he is still actively involved in the XRP project.
Schwartz's Job Transformation and Continued Participation
In late September 2025, Schwartz announced that he would resign his day-to-day duties as Ripple's Chief Technology Officer before the end of the year. Before making this news public, he had built his own XRP ledger node, focusing on publishing its output data and exploring more application scenarios of XRP.
Although he no longer handles Ripple's day-to-day affairs, Schwartz's recent remarks made it clear that his connection with the XRP ecosystem has not been interrupted. In response to an X platform user who mentioned that he continued to observe XRP ledgers through personal nodes, Schwartz shared his recent work and his meeting with Ripple's team.
If you have ever wondered whether Schwartz is just retiring from Ripple or also withdrawing from the XRP project, his response-"It's fun to work for a few hours as before and have video conferencing with the team again"-clarifies his continued engagement.
Schwartz's statement relieved community members. Previously, there were concerns that his retirement would mean leaving the XRP project completely, when in fact it was just a transformation of his executive role at Ripple.
Ripple is a San Francisco-based technology company known for developing XRP ledgers. XRP Ledger is a decentralized blockchain focused on fast, low-cost cross-border payments. Schwartz played a key role as chief technology officer and co-creator of the underlying technology.
Technical Challenges and Countermeasures
On Friday, Schwartz reported that his XRP ledger node was experiencing technical problems, manifested in the loss of network peers due to problems during the message negotiation process, which led to frequent connection interruptions, with the error message "onReadMessage: No message of desired type."
XRP ledger analysis platform xrpl.to confirmed that the issue affects the entire network, not just Schwartz's personal nodes. Schwartz mentioned that he spent hours working with Ripple's team, including participating in video conferences, indicating that he was actively involved in diagnosing or resolving the fault.
XRP ledger upgrades and network stability
XRP ledger version 3.2.1 was released shortly after the network-wide problem was discovered. The upgrade fixes a previously observed "manifest flood" vulnerability that caused nodes to indiscriminately accept and rebroadcast an unlimited number of lists from unknown verifier keys. The new version introduces four key restrictions to prevent such issues and ensure network reliability.
The upgrade includes: Prior to version 3.2.1, lists from any verifier could be rebroadcast without restrictions; after the upgrade, restrictions were imposed on the acceptance and rebroadcast of lists. In addition, previously unknown verifier keys allowed unlimited activities, but their activities were restricted after the upgrade.
This update is expected to improve the overall security and performance of XRP ledgers and reduce the risk of network outages due to uncontrolled inventory proliferation.

Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
XRP