David Schwartz, Ripple CTO emeritus and one of the original architects of the XRP Ledger, recently signaled that he remains engaged with XRP projects despite stepping down from his previous role at Ripple.
Schwartz’s transition and continued engagement
In late September 2025, Schwartz announced that he would leave his day-to-day responsibilities as Ripple CTO by the end of the year. Before making this announcement public, he had already set up his own XRP Ledger node, focusing on publishing its output data and exploring additional XRP use cases.
Despite no longer handling routine duties at Ripple, Schwartz’s recent comments have made clear that his connection to the XRP ecosystem persists. Responding to an X user who referenced his ongoing observations of the XRP Ledger via his personal hub, Schwartz recounted his recent work and meetings with the Ripple team.
If you had any doubt about whether David was retiring from just Ripple or also from XRP, Schwartz’s response, “It was fun spending a few hours working like I used to and having a Zoom call with the team again,” clarified his enduring engagement.
These remarks from Schwartz have reassured community members who wondered whether his retirement indicated a total departure from the XRP project or simply a shift from his executive role at Ripple.
Ripple is a San Francisco-based technology company known for developing the XRP Ledger, a decentralized blockchain focusing on fast, low-cost cross-border payments. David Schwartz played a pivotal role as its chief technology officer and co-creator of the underlying technology.
Technical challenges and response
On Friday, Schwartz reported that his XRP Ledger hub encountered technical issues, specifically losing network peers due to a problem in the message negotiation process—which led to frequent connection losses flagged by the error “onReadMessage: No message of desired type.”
xrpl.to, an analytics platform for the XRP Ledger, verified that this issue affected the wider network, not just Schwartz’s individual node.
Schwartz’s mention of dedicating a few hours to collaborate with the Ripple team, including joining a Zoom call, suggests he actively participated in diagnosing or resolving the disruption.
Mini dictionary: xrpl.to is an independent analytics application that provides real-time data insights into the performance and activities on the XRP Ledger.
XRP Ledger upgrade and network stability
Shortly after the network-wide issue was detected, the XRP Ledger released version 3.2.1. This upgrade addressed a “manifest flood” bug observed earlier, where nodes indiscriminately accepted and rebroadcast unlimited manifests from unknown validator keys. The new version introduces four critical restrictions to prevent this problem and ensure network reliability.
| Feature | Before v3.2.1 | After v3.2.1 |
|---|---|---|
| Manifest flood vulnerability | Manifests from any validator could be rebroadcast without limit | Limits imposed to restrict manifest acceptance and rebroadcasting |
| Validator key acceptance | Unknown validator keys allowed unlimited activity | Activity restricted for unknown keys |
This update is expected to enhance the overall security and performance of the XRP Ledger, reducing the risk of network disruptions caused by uncontrolled manifest floods.
