Express

Ripple CEO Brad Garlinghouse Responds To SEC Lawsuit

Emily Mason

Summary: Ripple CEO Brad Garlinghouse has responded to several questions surrounding the Securities and Exchange Commission's lawsuit against his firm in a recent tweet. His opening tweet notes that he will not be able to exhaust the conversation in a Twitter thread and that he is restrained somewhat by the litigation process. Garlinghouse assured followers that ...

Ripple CEO Brad Garlinghouse has responded to several questions surrounding the Securities and Exchange Commission's lawsuit against his firm in a recent tweet.

His opening tweet notes that he will not be able to exhaust the conversation in a Twitter thread and that he is restrained somewhat by the litigation process. Garlinghouse assured followers that Ripple attempted to the SEC, but was unable to strike a deal. He denied allegations that Ripple paid exchanges to list XRP, highlighting that "XRP is one of the most liquid (top 3-5) digital assets globally, and 95% is traded outside the US."

He assured followers that the firm was working on a response to the suit, but that the legal process moves slowly.

"We’ve moved from lack of regulatory clarity to regulatory chaos in the U.S," he wrote. "This is why regulation by enforcement is such bad public policy. With the new administration, we expect #DCEA to be reintroduced - common-sense legislation providing clarity to the entire industry."

By Emily Mason

Last Update:

Tags: ,,,
Link: Ripple CEO Brad Garlinghouse Responds To SEC Lawsuit   [Copy]
  • BTC Weekly Outlook: A Bullish Week, but Signs Point to a Shift to Defensive Play 11 hours ago
  • Figma's IPO Triumph and Crypto Bet: How a Design Disruptor Stunned Wall Street After a ... 11 days ago
  • When Stablecoins Tear Down Banks’ Interest Margin Moats — A Third Look at the U.S. “Ge... 13 days ago
  • Twitter Space Highlight: Is Altcoin Season Coming? Unpacking BTC, Institutions & RWA 14 days ago
  • BTC Weekly: Momentum Top Divergence Signals Potential Shift Lower 14 days ago
  • You need to login to comment.