1:26-cv-00722
Securitize Inc v. Tzero Group Inc
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Securitize, Inc. (Delaware)
- Defendant: tZERO Group, Inc. and tZERO IP, LLC (Delaware)
- Plaintiff's Counsel: Morris, Nichols, Arsht & Tunnell LLP
- Case Identification: 1:26-cv-00722, D. Del., 06/22/2026
- Venue Allegations: Venue is alleged to be proper in Delaware because Defendants are organized under Delaware law, maintain registered agents in the state, and directed patent enforcement activities to Plaintiff's registered agent in Delaware.
- Core Dispute: Plaintiff seeks a declaratory judgment that its "DS Protocol" and "Vault Registrar" products do not infringe two of Defendant's patents related to blockchain-based trading of tokenized securities.
- Technical Context: The technology at issue involves using smart contracts and distributed ledgers (blockchains) to automate regulatory compliance and facilitate the trading of tokenized assets, bridging traditional financial systems with decentralized crypto platforms.
- Key Procedural History: The action was prompted by a cease-and-desist letter sent by Defendant's counsel on June 15, 2026, which alleged infringement and included claim charts. This letter, along with a subsequent press release by the Defendant, created the "actual controversy" that provides the jurisdictional basis for this declaratory judgment action.
Case Timeline
| Date | Event |
|---|---|
| 2015-02-09 | U.S. Patent No. 11,394,560 Earliest Priority Date |
| 2017-01-01 | Securitize, Inc. founded |
| 2018-08-10 | U.S. Patent No. 11,216,802 Earliest Priority Date |
| 2022-01-04 | U.S. Patent No. 11,216,802 Issued |
| 2022-07-19 | U.S. Patent No. 11,394,560 Issued |
| 2025-12-01 | tZERO publicly acknowledges business difficulties |
| 2026-06-12 | tZERO counsel emails courtesy copy of enforcement letter to Securitize |
| 2026-06-15 | tZERO enforcement letter received by Securitize's registered agent |
| 2026-06-15 | tZERO issues press release regarding patent enforcement against Securitize |
| 2026-06-18 | Deadline for Securitize's response to tZERO's letter |
| 2026-06-22 | Complaint for Declaratory Judgment filed |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 11,216,802 - "Self-enforcing security token implementing smart-contract-based compliance rules consulting smart-contract-based global registry of investors"
The Invention Explained
- Problem Addressed: The patent's background describes the difficulty of ensuring that transactions involving cryptographic tokens comply with securities regulations, such as those from the U.S. Securities and Exchange Commission (SEC). This regulatory uncertainty limits the pool of eligible investors and restricts the market for tokenized assets. '802 Patent, col. 3:1-7 '802 Patent, col. 3:19-24
- The Patented Solution: The invention proposes a "self-enforcing" security token that automatically checks for regulatory compliance before executing a transfer. It achieves this by having the token's smart contract call upon one or more external compliance rules, which in turn consult a "global registry of investors." This registry stores investor attributes (e.g., accreditation status, KYC checks), allowing the system to verify transaction eligibility on-the-fly. '802 Patent, abstract '802 Patent, col. 3:25-34 Figure 1 illustrates this architecture, showing the security token (102) referencing compliance rules (106) that interact with an external global registry (108).
- Technical Importance: This system was designed to automate complex regulatory checks within blockchain transactions, aiming to make tokenized securities more accessible to a broader, regulated market while managing compliance risk for issuers. '802 Patent, col. 2:46-54
Key Claims at a Glance
- The complaint indicates that independent claim 1 and dependent claims 3, 4, and 5 of the '802 Patent were asserted in the pre-suit correspondence Compl. ¶15
- Independent Claim 1 recites a network node configured to:
- Receive a request to transfer a security token.
- Execute compliance rules via a smart contract that is separate from the token's originating smart contract.
- Wherein the smart contract references a "global registry" on a distributed ledger.
- Transfer the token based on the execution of the rules.
- Wherein the "global registry" comprises specific data, including: at least one PII hash for each investor; an indication of whether the offering qualifies under SEC Regulation A or S; an indication of whether an investor qualifies under SEC Regulation D; and an indication that AML/KYC checks have been performed. '802 Patent, claim 1
U.S. Patent No. 11,394,560 - "Crypto integration platform"
The Invention Explained
- Problem Addressed: The patent identifies the technical incompatibility between legacy financial trading systems, which often use protocols like Financial Information eXchange (FIX), and modern cryptographic exchanges. These systems use different protocols, and their methods for storing market and ownership data are not interoperable. '560 Patent, col. 1:31-41
- The Patented Solution: The invention is a "Crypto Integration Platform" that functions as a bridge. It receives trade orders in a legacy format (like FIX), translates them into cryptographic transactions, and interfaces with crypto exchanges. '560 Patent, abstract '560 Patent, col. 2:55-61 A core feature is its method for ensuring authorization: it cryptographically signs both the asset transfer transaction and a second transaction containing the order details, then verifies that both were signed by the same key before authorizing the trade, mathematically linking the legacy order to the on-chain transaction. '560 Patent, abstract '560 Patent, col. 8:40-51
- Technical Importance: The platform enables traditional broker-dealers to access liquidity on crypto exchanges without replacing their existing infrastructure, thereby connecting the worlds of traditional and decentralized finance. '560 Patent, col. 2:61-66
Key Claims at a Glance
- The complaint indicates that independent claim 1 of the '560 Patent was asserted in the pre-suit correspondence Compl. ¶15
- Independent Claim 1 recites a system configured to:
- Receive an order to execute a trade of an item associated with a first account.
- Cryptographically sign a first transaction to transfer the item from the first account to a second account.
- Cryptographically sign a second transaction that includes the order.
- Verify that both the first and second transactions were signed using the same cryptographic key.
- Authorize placement of the order on an exchange based on this verification. '560 Patent, claim 1
III. The Accused Instrumentality
Product Identification
The complaint identifies "Securitize's DS Protocol" and "Securitize's Vault Registrar" as the accused instrumentalities Compl. ¶15
Functionality and Market Context
- The complaint positions Securitize as a "leader in real-world asset tokenization," overseeing over $4 billion in tokenized assets, suggesting significant commercial adoption of its technology Compl. ¶1
- The DS Protocol is accused of infringing the '802 Patent. The complaint alleges that the protocol's on-chain register "contains only certain information about investors" and specifically lacks the offering qualification data (e.g., Reg A) and investor PII hashes required by the patent's claims Compl. ¶28
- The Vault Registrar is accused of infringing the '560 Patent. The complaint characterizes its functionality as limited to "registering vaults to an investor's identity." It explicitly denies that the Vault Registrar handles trade orders, cryptographically signs transactions to transfer items between accounts, or authorizes orders on an exchange Compl. ¶35
IV. Analysis of Infringement Allegations
The complaint does not provide the claim charts from the pre-suit demand letter. The following tables summarize the non-infringement arguments articulated in the complaint's narrative.
No probative visual evidence provided in complaint.
'802 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Non-Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| ...wherein the global registry further comprises at least one indication of: whether an offering of the security token qualifies under Securities and Exchange Commission (SEC) Regulation A,... whether the offering of the security token qualifies under SEC Regulation S,... and... at least one personally identifiable information (PII) hash for each of at least one investor... | The on-chain register used by the DS Protocol allegedly "does not contain information about an offering of any security token" or a "personally identifiable information (PII) hash for an investor." | ¶28 | col. 31:56-65 |
'560 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Non-Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| ...receive an order to execute a trade,... cryptographically sign, using a cryptographic key, a first transaction to transfer the at least one transactional item from the first account to the second account,... cryptographically sign, using the cryptographic key, a second transaction that includes the order,... and authorize placement of the order on an exchange... | The accused Vault Registrar allegedly "performs the limited function of registering vaults to an investor's identity." It is alleged that it "does not handle orders to execute trades" and "does not cryptographically sign transactions that transfer transactional items between accounts" or authorize placement on an exchange. | ¶35 | col. 23:2-17 |
Identified Points of Contention
- '802 Patent Scope Question: The dispute raises a question of claim scope regarding the term "global registry." The court may need to determine if this term requires the explicit inclusion of all data elements listed in claim 1 (PII hash, Reg A/S status, etc.) for infringement to be found, as Securitize alleges its system omits them Compl. ¶28
- '560 Patent Technical Question: A central technical question is whether the Vault Registrar's function of "registering vaults to an investor's identity" performs the same steps as the claimed method. The court may need to analyze if this registration process involves receiving a trade order and creating two distinct, cryptographically signed transactions as required by claim 1, or if it is a fundamentally different, single-step operation Compl. ¶35
V. Key Claim Terms for Construction
The Term: "global registry" (['802 Patent, claim 1](https://ex:cit:7))
- Context and Importance: The definition of this term is central to the non-infringement argument for the '802 Patent. Securitize alleges its DS Protocol does not infringe because its on-chain register lacks the specific data elements that, in its view, define a "global registry" under the patent Compl. ¶28 Practitioners may focus on this term because its construction could be dispositive of infringement for the '802 Patent.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent summary states the smart contract "references a global registry," and the detailed description notes it "may include attributes of the investors," which could be argued to support a more flexible definition not strictly limited to the enumerated examples '802 Patent, summary '802 Patent, col. 3:30-32
- Evidence for a Narrower Interpretation: Claim 1 explicitly states the "global registry comprises at least one" of several specific data types, including PII hashes and indications of qualification under SEC Regulations A, D, and S. This explicit recitation in the claim body provides strong evidence for a narrower construction that requires the presence of these elements '802 Patent, claim 1:56-65
The Term: "cryptographically sign... a first transaction to transfer the at least one transactional item... [and] a second transaction that includes the order" (['560 Patent, claim 1](https://ex:cit:13))
- Context and Importance: Securitize's defense against infringement of the '560 Patent rests on its assertion that its Vault Registrar does not perform these two distinct signing actions Compl. ¶35 The case may turn on whether the Vault Registrar's operations can be characterized as performing these claimed steps.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: A party could argue that any complex cryptographic process that achieves both an asset transfer and an order record, even if implemented as a single logical function, meets the claim limitation.
- Evidence for a Narrower Interpretation: The claim language recites two separate "cryptographically sign" steps for two distinct items: a "first transaction to transfer" and a "second transaction that includes the order." This structure, reinforced by the abstract which also distinguishes the two transactions, suggests they are required to be separate and discrete events for literal infringement. '560 Patent, claim 1 '560 Patent, abstract
VI. Other Allegations
- Indirect Infringement: The complaint makes a blanket denial of any "direct[] or indirectly" infringement but does not provide details of any specific indirect infringement allegations made by tZERO Compl. ¶27; Compl. ¶34 The complaint does not provide sufficient detail for analysis of indirect infringement.
- Willful Infringement: The complaint notes that tZERO's pre-suit letter accused Securitize of willful infringement, establishing knowledge as of the date of the letter Compl. ¶15
VII. Analyst's Conclusion: Key Questions for the Case
This declaratory judgment action appears to center on two primary questions of claim interpretation and technical functionality.
A core issue will be one of definitional scope: can the term "global registry" in the '802 Patent be construed to cover an on-chain register that allegedly lacks the specific data elements-such as PII hashes and SEC regulation qualification status-that are explicitly enumerated in the language of claim 1?
A key evidentiary question will be one of functional equivalence: does the accused "Vault Registrar" product, which Securitize claims only "register[s] vaults to an investor's identity," perform the distinct, two-part process of cryptographically signing a first transaction for asset transfer and a second transaction for the order itself, as required by claim 1 of the '560 Patent?