Ripple CTO emeritus David Schwartz hints he stays concerned with $XRP in a current X dialog, regardless of stepping away from day-to-day duties at Ripple.
Schwartz revealed in late September 2025 that he’ll step down from his day-to-day actions as Ripple CTO on the finish of the yr. Forward of the announcement, he spun up his personal $XRP Ledger node to publish its output knowledge whereas researching different use instances for $XRP.
Now, the Ripple CTO emeritus’s current feedback trace that his retirement doesn’t indicate abandoning $XRP. Schwartz responded to an X person who pointed to his current statement concerning the $XRP Ledger community, derived from his hub, to counsel that he did not retire from $XRP.
“For those who had any doubt about whether or not David was retiring from simply Ripple or additionally from $XRP,” the X person wrote. Schwartz replied, saying, “It was enjoyable spending just a few hours working like I used to and having a Zoom name with the staff once more.”
It was enjoyable spending just a few hours working like I used to and having a Zoom name with the staff once more.
— David ‘JoelKatz’ Schwartz (@JoelKatz) July 31, 2026
Being an authentic architect of the $XRP Ledger, Schwartz’s feedback have reassured many $XRP supporters who questioned whether or not his retirement marked an entire departure from the $XRP ecosystem.
Ripple CTO emeritus statement results in XRPL repair
On Friday, Ripple CTO emeritus David Schwartz indicated that his hub was experiencing difficulties. The problem triggered the hub to lose friends with “onReadMessage: No message of desired sort” throughout negotiation, adopted by a connection loss.
The identical difficulty was confirmed by XRPL Analytics App, xrpl.to, which acknowledged that the issue was network-wide.
Schwartz’s contribution to fixing the problem could also be inferred from his point out of getting a Zoom name with the staff and dealing for a few hours, which one would possibly assume occurred on this context.
$XRP Ledger model 3.2.1 was launched shortly after, fixing the manifest flood noticed on Friday, July 31. Nodes had beforehand accepted, saved, and rebroadcast an infinite variety of manifests from unknown validator keys; model 3.2.1 provides 4 limits to repair the problem.
