Ripple CTO emeritus David Schwartz hints he stays concerned with XRP in a latest 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 latest feedback trace that his retirement doesn’t suggest abandoning XRP. Schwartz responded to an X person who pointed to his latest commentary in regards to the XRP Ledger community, derived from his hub, to recommend that he did not retire from XRP.
Dogecoin (DOGE), Zcash (ZEC), Cardano (ADA) and Solana (SOL) Worth Evaluation For August 1: Outsiders Enter the Stage
Democrats Hate Crypto Extra Than Oil Corporations and Knowledge Facilities, Ballot Exhibits
You May Additionally Like
“If you happen to 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 a number of hours working like I used to and having a Zoom name with the crew once more.”
Being an authentic architect of the XRP Ledger, Schwartz’s feedback have reassured many XRP supporters who questioned whether or not his retirement marked a whole departure from the XRP ecosystem.
Ripple CTO emeritus commentary 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 kind” throughout negotiation, adopted by a connection loss.
You May Additionally Like
The identical concern was confirmed by XRPL Analytics App, xrpl.to, which said that the issue was network-wide.
Schwartz’s contribution to fixing the difficulty could also be inferred from his point out of getting a Zoom name with the crew and dealing for a few hours, which one may 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 difficulty.