Modulus Global Incorporated v. Patrick Gruhn, et al.

CourtDistrict Court, D. Arizona
DecidedFebruary 13, 2026
Docket2:24-cv-03195
StatusUnknown

This text of Modulus Global Incorporated v. Patrick Gruhn, et al. (Modulus Global Incorporated v. Patrick Gruhn, et al.) is published on Counsel Stack Legal Research, covering District Court, D. Arizona primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Modulus Global Incorporated v. Patrick Gruhn, et al., (D. Ariz. 2026).

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA

9 Modulus Global Incorporated, No. CV-24-03195-PHX-ROS

10 Plaintiff, ORDER

11 v.

12 Patrick Gruhn, et al.,

13 Defendants. 14 15 Before the Court are several Motions to Dismiss for lack of personal jurisdiction 16 (Docs. 48, 51, 52, 53, 54, 55). The Plaintiff responded to each (Docs. 66, 67) and the 17 Defendants replied. (Docs. 70, 72, 73, 74, 75). For the reasons stated, the Court will grant 18 the Motions to Dismiss as to Defendants Brandon Williams (“Williams”), Kephas 19 Corporation, WIB Technologies Inc., and DAAG USA, LLC, and deny the Motion to 20 Dismiss as to Defendants Patrick Gruhn (“Gruhn”), and Stephen Stephens. 21 I. Background 22 Although Plaintiff alleges tort claims, this case arises from two contracts entered 23 between Plaintiff Modulus Global, Inc. (“Modulus”) and Digital Assets AG (“DAAG”).1 24 Modulus is a corporation incorporated in Delaware that “provides advanced, proprietary 25 financial technology products and services.” (Doc. 39 ¶¶ 3, 7). In August 2021, Modulus 26 entered into two Licensing Agreements with DAAG for use of Modulus’ matching engine 27

28 1It is noted “DAAG” is not alleged to be a defendant in this case, rather “DAAG USA” is an alleged defendant and “DAAG” is a party to the two contracts. 1 and source code. (Doc. 39 ¶ 4). Modulus alleges DAAG and the Defendants, through the 2 Licensing Agreements, secretly worked to provide financial company FTX Trading Ltd. 3 (“FTX”) and others with prohibited access to Modulus’ engine and source code.2 What 4 follows are the alleged facts. 5 Defendants Gruhn, Williams, and Stephens3 were aware of Modulus’ software from 6 at least July 18, 2018 (Doc 39 ¶¶ 57–58). Having a pre-existing relationship with then- 7 CEO of FTX Samuel Bankman-Fried, in May 2020, Defendant Williams proposed a deal 8 with FTX to help FTX expand into the European Union. (Doc. 39 ¶ 65). Both Williams 9 and Gruhn incorporated DAAG in July 2020 and entered into two confidential Share 10 Purchase Agreements (the “First SPA” and “Second SPA”) in October 2020 and July 2021, 11 whereby FTX’s associated entity Alameda acquired 20% of DAAG shares in advance of 12 DAAG having begun operating. (Doc. 39 ¶¶ 66–74). The acquisition price in the Second 13 SPA reflected a $370 million valuation of DAAG, which was unusual because at the time 14 DAAG had no active business. (Doc. 39 ¶¶ 74–77). 15 Just a month after receiving payment under the Second SPA, Gruhn contacted 16 Modulus via an online contact form expressing interest in Modulus’ Source Code. (Doc. 17 39 ¶ 78-80). Modulus then began a “careful vetting process” and negotiations with Gruhn 18 and Stephens for the software licenses. (Doc. 39 ¶ 84). Throughout the process, Gruhn and 19 Stephens failed to disclose the close relationship between DAAG and FTX despite the 20 “careful vetting process” and the confidentiality conditions contained in the “License 21 Agreements” (Source Code). (Doc. 39 ¶¶ 82–86). Had Modulus known of this relationship, 22 it would not have agreed to license its Source Code to DAAG. (Doc. 39 ¶ 102). 23 2 Hereafter the “source code” will be referred to as: Source Code. 24 3 Gruhn is identified as a founder, shareholder, and Global IT Director of DAAG (Doc. 39 ¶ 56), as well as President and owner of Kephas Corp. (Doc. 39 ¶ 26), and “owner/member” 25 of DAAG USA (Doc. 51 at 14) and primary owner and CTO of WIB Technologies. (Doc. 26 39 ¶ 28). Although Gruhn’s title at DAAG is undefined, he had authority to sign contracts on DAAG’s behalf. See Doc. 66-2. Williams is identified as a co-founder, shareholder, 27 and Corporate Development Lead of DAAG. (Docs. 39 ¶ 25; 34-4 at 2). These titles are 28 undefined. Stephens is identified as the CEO of WIB Technologies and COO of Kephas Corp. (Doc. 39 ¶ 24, 28). His official role with DAAG is not specified. 1 One day prior to execution of the License Agreements, Stephens introduced 2 Shailesh Nair to Modulus as the project lead for DAAG’s implementation of the licensed 3 Source Code. (Doc. 39 ¶ 93). Nair also had connections with FTX: days before his 4 introduction as the project lead, he opened a personal forked repository in the Go FTX 5 Library on GitHub—a platform for storing and sharing code and files such as the licensed 6 Source Code. (Doc. 39 ¶¶ 87–90, Doc. 39-5 at 3). The Go FTX Library is used by 7 programmers and users to interact with FTX’s exchange. (Doc. 39 ¶ 93). 8 On August 20, 2021, Modulus, still completely unaware of DAAG’s involvement 9 with FTX insiders, executed the License Agreements with DAAG. (Id.) The License 10 Agreements included certain essential and key provisions and restrictions, including non- 11 transferability, confidentiality, usage restrictions, technical support and updates, and 12 Arizona choice-of-law and arbitration provisions. (Docs. 44, 44-1). 13 The Licensed Source Code was deployed to DAAG in mid-October, and by the end 14 of the month, FTX was in the process of finalizing the purchase of the remaining 80% of 15 DAAG’s shares. (Doc. 39 ¶ 14-15). Counsel for FTX notably found a due diligence process 16 unnecessary because “they do not have any active business,” “they are not yet operating,” 17 and FTX was “not too concerned” because DAAG was “not up and running yet.” (Doc. 39 18 ¶ 115, Doc. 39-1 ¶ 73-76). Examining DAAG’s financial statements was also “not 19 important for the business going forward.” (Id.). 20 The Third Share Purchase Agreement (“Third SPA”) was finalized on November 21 14th, 2021, and the 20% previously acquired by Alameda was transferred to FTX in a 22 separate share purchase agreement just days later. (Doc. 39-1 ¶¶ 63, 70). After the Third 23 SPA, Defendant Williams parted ways with DAAG and DAAG began to operate as FTX 24 Europe, with Gruhn serving as its head. (Doc. 39 ¶ 138, 192). 25 After this acquisition, Modulus alleges Defendants provided FTX with the Licensed 26 Source Code in violation of the License Agreements and trade secrets law. Historically, 27 FTX’s matching engine and software were notoriously flawed. (Doc. 39 ¶ 4). But 28 approximately one year after DAAG received the Source Code, in October 2022, Samuel 1 Bankman-Fried posted a series of tweets (the “Matching Engine tweets”) touting upcoming 2 improvements to its matching engine. (Doc. 39 ¶¶ 16–17). The tweets indicated these 3 improvements had “been in the works for most of the year.” (Id.). Seven days before FTX’s 4 planned release of these improvements, Stephens sent an email to Modulus’ CEO Richard 5 Gardner asking for an updated version of the Licensed Source Code, requesting: ““We 6 would like to get together soon to go through a technical call about Modulus. Does our 7 license give us access to the latest version of the Modulus system? Can we do that this 8 week?” (Doc. 39 ¶ 176). The acquisition was finally disclosed when Stephens included 9 FTX employees in an emailed meeting invitation regarding the updated Source Code. (Doc. 10 39 ¶¶ 180–86). Other related entities including Defendants Kephas Corp. and WIB 11 Technologies4 also now provide products containing Source Code identical to Modulus’ 12 Source Code. (Doc. 39 ¶¶ 199–207, 218–19). 13 Furthermore, in February 2022 an accounting and professional services firm called 14 BDO USA, LLP was retained by Jen Chan, Chief of Staff for the FTX Group, to “determine 15 the fair value of the [assets and liabilities] of DAAG, acquired by FTX Trading Ltd. on 16 November 14, 2021.” (Doc. 39-7 at A.0147). This report found “the primary rationale 17 behind the acquisition of DAAG was to acquire its operating licenses.” (Id. at A.0149). 18 The list of relevant operating licenses included, notably, “Modulus, Matching engine, 19 Crypto Derivative Exchange.” (Id. at A.0150).

Free access — add to your briefcase to read the full text and ask questions with AI

Related

International Shoe Co. v. Washington
326 U.S. 310 (Supreme Court, 1945)
Shaffer v. Heitner
433 U.S. 186 (Supreme Court, 1977)
Calder v. Jones
465 U.S. 783 (Supreme Court, 1984)
Burger King Corp. v. Rudzewicz
471 U.S. 462 (Supreme Court, 1985)
CollegeSource, Inc. v. AcademyOne, Inc.
653 F.3d 1066 (Ninth Circuit, 2011)
Janusz Omeluk v. Langsten Slip & Batbyggeri A/s
52 F.3d 267 (Ninth Circuit, 1995)
Dietel v. Day
492 P.2d 455 (Court of Appeals of Arizona, 1972)
Batton v. Tennessee Farmers Mutual Insurance
736 P.2d 2 (Arizona Supreme Court, 1987)
Burt v. Titlow
134 S. Ct. 10 (Supreme Court, 2013)
Walden v. Fiore
134 S. Ct. 1115 (Supreme Court, 2014)
Loredana Ranza v. Nike, Inc.
793 F.3d 1059 (Ninth Circuit, 2015)
Kelly Park v. Karen Thompson
851 F.3d 910 (Ninth Circuit, 2017)
Boon Global Limited v. Usdc-Caoak
923 F.3d 643 (Ninth Circuit, 2019)
Lns Enterprises LLC v. Continental Motors, Inc.
22 F.4th 852 (Ninth Circuit, 2022)
Schultz v. Principi
25 F. App'x 831 (Federal Circuit, 2001)

Cite This Page — Counsel Stack

Bluebook (online)
Modulus Global Incorporated v. Patrick Gruhn, et al., Counsel Stack Legal Research, https://law.counselstack.com/opinion/modulus-global-incorporated-v-patrick-gruhn-et-al-azd-2026.