Bankruptcy Court Publishes 14,000 Pages of Celsius Customer Usernames and Trade History – Bitcoin News

News

Bankruptcy Court Publishes 14,000 Pages of Celsius Customer Usernames and Trade History

The crypto community is upset about a recent discovery stemming from the Celsius bankruptcy case as a court filing has revealed over 14,000 pages of the usernames and trading histories of the company’s customers. While the file does not disclose personal information tied to the user’s finance providers or the customer’s residential address, the crypto community believes there are other ways these identities can be doxxed.

Crypto Community Is Appalled by Celsius Username and Trading History Court Filing

The embattled crypto lender Celsius is dealing with controversy again as a court filing has been discovered by the news outlet Gizmodo. The 14,000-page filing reveals the usernames and trading histories tied to Celsius clients.

The data release has caused an uproar within the crypto community as many believe high-net-worth traders could be doxxed. While the list only shows usernames and trades, it is alleged that more information tethered to the identities of the users can be discovered by heuristics and blockchain parsing tools.

“This Celsius dox is one of the [most] egregious privacy violations in crypto history,” one individual wrote. “Many on this list may have their safety at risk. It’s more important than ever to maximize your digital security.”

The addresses of each user have been redacted and names were allegedly supposed to be redacted but the U.S. bankruptcy court trustee William Harrington objected to the requests that pressed for the customer’s names to be redacted as well.

Harrington claims that the bankruptcy case needs to be “open and transparent” and he also remarked that Celsius need to “demonstrate extraordinary circumstances and a compelling need to obtain protection to justify any such request.”

The filing is roughly 18.6 gigabytes of user data and in addition to a large number of customers, Celsius executives Alex Mashinsky’s, Dan Leon’s, and Nuke Goldstein’s trades are also present in the filing. The news follows the third-party data leak that took place on July 28 when Celsius disclosed a third party had access to customer data.

The latest court filing disclosure of 18.6 gigabytes of user data follows the finalized schedule for the Celsius bankruptcy sale. While the names of the customers are redacted, the crypto community is not pleased with Celsius and the bankruptcy court trustee’s decision.

“Typically, when you dox you don’t get rugged. And on the other hand, when you get rugged you don’t get doxxed,” one user stressed on Twitter. “Celsius tier 1 sh** storm.”

Tags in this story
Alex Mashinsky, Bankruptcy, Bankruptcy Court, Celsius, Celsius CEO Alex Mashinsky, Celsius crypto lender, Celsius usernames, Chapter 11 Bankruptcy, court examiner, Court Filings, Court trustee, Crypto lender, Dan Leon, examiner, Finalized Sale, FTX CEO, Insolvency, judge Martin Glenn, Nuke Goldstein, reorganizing, Sale Hearing, Southern District of New York, William Harrington

What do you think about the court publishing the usernames and trading history stemming from Celsius customers? Let us know what you think about this subject in the comments section below.

Jamie Redman

Jamie Redman is the News Lead at Bitcoin.com News and a financial tech journalist living in Florida. Redman has been an active member of the cryptocurrency community since 2011. He has a passion for Bitcoin, open-source code, and decentralized applications. Since September 2015, Redman has written more than 6,000 articles for Bitcoin.com News about the disruptive protocols emerging today.

Image Credits: Shutterstock, Pixabay, Wiki Commons

Disclaimer: This article is for informational purposes only. It is not a direct offer or solicitation of an offer to buy or sell, or a recommendation or endorsement of any products, services, or companies. Bitcoin.com does not provide investment, tax, legal, or accounting advice. Neither the company nor the author is responsible, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any content, goods or services mentioned in this article.

Read disclaimer
Show comments