Who Got the “Secret XRP Contracts”? Ripple Exec Addresses Viral Rumor
David Schwartz, Ripple’s CTO Emeritus, denies claims that he confirmed the existence of secret pre-allocated XRP (XRP) contracts for select investors. The denial came after an X post attributed the confirmation to Schwartz, triggering community backlash and renewed debate over misinformation within XRP-focused social media circles. What Sparked the Controversy Reports claimed that Schwartz had “officially confirmed pre-allocated XRP contracts are real,” with the majority of Ripple’s escrowed XRP already earmarked for undisclosed recipients. The claim spread quickly, drawing attention from both supporters and critics. However, David Schwartz, Ripple CTO emeritus, shut down the claim, noting that he never said that. You are correct. I absolutely never said that.— David 'JoelKatz' Schwartz (@JoelKatz) March 27, 2026 His response leaves no room for ambiguity, with the statement attributed to him having no basis in anything he had previously said or written. A Broader Pattern of Misinformation The incident did not occur in isolation, as there are many other instances where large XRP-focused accounts repeatedly spread false claims. “Stuff like this happens daily, each time a different liar,” one user highlighted. This pattern echoes prior episodes in the XRP community. In January 2026, a false memo attached to Ripple’s routine escrow unlock claimed the company had sold over $8 billion in XRP during 2025. The memo, which anyone could attach to an escrow release transaction, was initially mistaken for an official Ripple statement. Schwartz himself has addressed similar misattributions before. In recent weeks, he rejected claims that Ripple offers discounted XRP to institutional buyers. He has also pushed back against accusations that Ripple’s XRP sales unfairly benefit equity shareholders over token holders. XRP Price Performance. Source: BeInCrypto Why False Attribution Matters The “pre-allocated contracts” claim carried weight specifically because it was attributed to ...
Comments
Log in to comment