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]
  • From Data Rights to Digital Property: Whistleblower Brittany Kaiser on Blockchain, RWA,... 3 days ago
  • The Base Chain's Ascent: How Deep Coinbase Integration and JPMorgan's Pilot Are Reshapi... 9 days ago
  • Tether in Trouble? U.S. Senate Just Passed a Law That Could Dethrone the $155B Stableco... 12 days ago
  • Justin Sun's Nasdaq Gamble: How Six Years Forged Ties with the Trump Family 13 days ago
  • The Crypto IPO Wave: From Fringe to Front Page 16 days ago
  • You need to login to comment.