"Retirement only from Ripple"...David Schwartz, a signal for Ripple's return?

▲ David Schwartz, XRP / AI generated image

David Schwartz, Ripple's Honorary Chief Technology Officer, continues to participate in the XRP ecosystem even after stepping down from his day-to-day duties. His directly operated XRP Ledger node and development team meetings have been confirmed as connecting links.

According to U.Today on August 1 (local time), Schwartz recently responded to a user on X (formerly Twitter) who asked about his relationship with XRP. The user commented that Schwartz had only retired from Ripple, not from XRP. Schwartz stated, “It was fun working for a few hours like old times and having Zoom meetings with the team again.”

Schwartz announced in late September 2025 that he would step down from his day-to-day duties as Ripple's CTO at the end of the year. Prior to the announcement, Schwartz launched his own XRP Ledger node. This was a measure to publish node output data and research other uses for XRP. Schwartz is one of the original architects of the XRP Ledger.

On July 31, a network connection issue occurred in the hub operated by Schwartz. The node displayed an error indicating that it did not have the desired type of message during the connection negotiation process, then lost connection with other participating nodes. XRP Ledger analysis service xrpl.to also confirmed that the same issue appeared across the network.

The XRP Ledger deployed version 3.2.1 immediately after the issue occurred. The update fixed the mass manifest propagation issue observed on July 31. Existing nodes could receive, store, and re-propagate manifests sent from unknown validator keys without restriction. Version 3.2.1 added four restrictions to prevent the same issue.

Schwartz's remarks show that he continues to be involved in XRP Ledger-related activities even after stepping down from Ripple's day-to-day operations. Operating his own node, observing the network, and participating in development team meetings are his currently disclosed activities. XRP Ledger version 3.2.1 corrected the identified network issue by introducing manifest processing restrictions.

[Article Summary]

-David Schwartz, Ripple's Honorary Chief Technology Officer, stated that he continues to participate in XRP-related work and development team meetings.

-A network issue was observed in the XRP Ledger hub operated by Schwartz, where connections to other participating nodes were lost.

-XRP Ledger version 3.2.1 added four restrictions to prevent the mass propagation of manifests from unknown validator keys.

*Disclaimer: This article is for investment reference only and we are not responsible for any investment losses based on it. The content should be interpreted for informational purposes only.*