By Ekin Genç
2 min read
In its ongoing lawsuit with the US Securities and Exchange Commission (SEC), the crypto payments company Ripple has scored a partial win in its bid to keep its private email correspondence out of the public eye.
The lawsuit, filed against Ripple in December, alleges that Ripple raised $1.3 billion by selling XRP in ongoing unregistered securities offerings. Ripple is a payments company created in 2012 that holds a large reserve of the digital currency XRP, which it releases periodically from escrow.
On March 31, a New York judge granted Ripple’s motion to temporarily seal four documents and ordered Ripple and the SEC to agree on redactions by April 2. Ripple’s lawyers managed to convince the judge to grant redactions in two email exchanges.
The first redaction is an email between Ripple CEO Brad Garlinghouse and an anonymous person about Rippleworks, the company’s non-profit VC arm. The second is between anonymous parties discussing the public perception of XRP and Ripple’s control of it.
Ripple hasn’t reached an agreement over the other two documents according to Ripple’s counsel, Andrew Ceresney. The SEC doesn’t want Ripple to hide an email exchange that contains co-founder Chris Larsen's personal financial information, nor one that shared the company’s strategy with private investors.
Ripple’s lawyers still want them redacted, obviously. “All four documents are ‘discovery materials filed with the court in connection with the discovery-related disputes,’ and therefore not judicial documents and not entitled to a presumption of public access,” Ceresney said in a letter to the court yesterday.
The court case hasn’t stopped XRP, Ripple’s cryptocurrency, from rising in value amid the current bull run. As of yesterday, XRP became the 7th largest cryptocurrency, with a market cap of $27.9 billion. XRP’s price is up around 170% since the start of the year, currently worth $0.636178—higher than before the lawsuit.
The rising tide lifts all boats.
Decrypt-a-cookie
This website or its third-party tools use cookies. Cookie policy By clicking the accept button, you agree to the use of cookies.