Binance CEO, CZ, Under Fire for “Not Acting in Good Faith”

Written by legalpdf | Published 2023/09/08
Tech Story Tags: tech-companies | binance | changpeng-zhao | ftc-v-binance | binance-lawsuit | binance-lawsuit-explained | ftc-v-binance-defendants | hackernoon-top-story

TLDRIn Count VI of this legal complaint, Binance Holdings and its affiliates are accused of violating Regulation 42.2, 17 C.F.R. § 42.2 (2022), by failing to implement essential financial regulations, including a Customer Information Program, Know-Your-Customer policies, and Anti-Money Laundering procedures. The complaint also highlights the alleged involvement and liabilities of key individuals, including Zhao and Lim, in these violations during the Relevant Period.via the TL;DR App

FTC v. Binance Court Filing, retrieved on March 27, 2023 is part of HackerNoon’s Legal PDF Series. You can jump to any part in this filing here. This is part 28 of 31.

VI. VIOLATIONS OF THE COMMODITY EXCHANGE ACT AND REGULATIONS

COUNT VI

Violations of Regulation 42.2, 17 C.F.R. § 42.2 (2022)

Failure to Implement Customer Information Program, and Failure to Implement Know Your Customer and Anti-Money Laundering Procedures

225. Paragraphs 1 through 186 of this Complaint are re-alleged and incorporated herein by reference.

226. During the Relevant Period, Defendants Binance Holdings, Binance IE, and Binance Services, all acting as a common enterprise and doing business as Binance, and through their officers, employees, and agents, violated and are continuing to violate 17 C.F.R. § 42.2 by failing to implement a Customer Information Program, failing to implement Know-YourCustomer policies and procedures, failing to implement an Anti-Money Laundering program, failing to retain required customer information, and failing to implement procedures to determine whether a customer appears on lists of known or suspected terrorists or terrorist organizations such as those issued by OFAC.

227. Each act in violation of 17 C.F.R. § 42.2, including, but not limited to, those specifically alleged herein, is alleged as a separate and distinct violation.

228. During the Relevant Period, Zhao directly or indirectly controlled Binance, and did not act in good faith or knowingly induced, directly or indirectly, the acts constituting Binance’s violations described in this Count. Therefore, pursuant to 7 U.S.C. § 13c(b), Zhao is liable as a control person for Binance’s violations described in this Count.

229. The acts and omissions of Zhao, Lim, and other officers, employees, or agents acting for Binance described in this Complaint were done within the scope of their office, employment, or agency with Binance. Therefore, pursuant to 7 U.S.C. § 2(a)(1)(B) and 17 C.F.R. § 1.2, Binance is liable as a principal for each act, omission, or failure of the other officers, employees, or agents acting for Binance, constituting violations of 17 C.F.R. § 42.2.

230. From July 2019 through at least January 2022 and while acting as Binance’s Chief Compliance Officer, Lim willfully aided, abetted, counseled, commanded, induced, or procured the acts constituting Binance’s violations described in this Count, or acted in combination or concert with any other person in any such violation, or willfully caused an act to be done or omitted which if directly performed or omitted by Lim or another would constitute a violation described in this Count. Pursuant to 7 U.S.C. § 13c(a), Lim is therefore liable for Binance’s violations described in this Count to the same extent as Binance.

Continue Reading Here.


About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings.

This court case 1:23-cv-01887 retrieved on September 4, 2023, from docdroid.net is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction.


Written by legalpdf | Legal PDFs of important tech court cases are far too inaccessible for the average reader... until now.
Published by HackerNoon on 2023/09/08