Nueces Blockchain LLC v. JPMorgan Chase Bank NA

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Nueces Blockchain LLC (Texas)
  • Defendant: JPMorgan Chase Bank, N.A. (United States)
  • Plaintiff's Counsel: KRAMER LLP; THE DACUS FIRM, P.C.
• Case Identification: 2:26-cv-00601, E.D. Tex., 07/22/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant JPMorgan Chase Bank, N.A. (JPMC) maintains regular and established places of business in the District, including a major office in Plano, Texas, and has committed alleged acts of infringement there, such as operating nodes for its blockchain and initiating infringing transactions.
• Core Dispute: Plaintiff alleges that Defendant's Kinexys blockchain platform infringes three patents related to foundational methods for creating and securing tamper-evident, cryptographically-chained digital logs.
• Technical Context: The lawsuit concerns distributed-ledger technology, which forms the basis for modern blockchain systems used for securing and processing high-value digital asset transactions.
• Key Procedural History: The complaint does not specify any prior litigation, inter partes review proceedings, or licensing history for the asserted patents. It does, however, advance a secondary infringement theory alleging that JPMC induces infringement by Coinbase, Inc. when JPMC initiates transactions using its JPM Coin Deposit Token on Coinbase's EVM-based "Base" network.

Case Timeline

Date	Event
2006-08-09	'987 & '949 Patents Priority Date
2008-10-02	'733 Patent Priority Date
2012-05-22	'733 Patent Issue Date
2020	Kinexys Platform Launch Date
2025-08-26	'987 Patent Issue Date
2025-09-09	'949 Patent Issue Date
2026-07-22	Complaint Filing Date

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 8,185,733 - "Method and Apparatus for Automatically Publishing Content Based Identifiers"

• Patent Identification: U.S. Patent No. 8,185,733, "Method and Apparatus for Automatically Publishing Content Based Identifiers," issued May 22, 2012. Compl. ¶13

The Invention Explained

• Problem Addressed: The patent's background describes the difficulty in verifying the integrity of electronic communications and data logs, which can be easily edited or manipulated, undermining their reliability for purposes like auditing or legal proceedings. '733 Patent, col. 1:11-25 '733 Patent, col. 1:43-47
• The Patented Solution: The invention proposes creating a verifiable "hash-chained log" by embedding a "content based identifier" (CBI), such as a cryptographic hash of a previous log entry, into a new electronic communication. This CBI, often referred to as a rolling checksum, links each new entry to the entire history of the log, making any subsequent alteration to a past entry detectable by re-calculating the chain of hashes. '733 Patent, abstract '733 Patent, col. 6:1-24
• Technical Importance: This method provides a decentralized way to establish a tamper-evident, auditable history for digital records and communications, a foundational concept for later distributed ledger and blockchain technologies. Compl. ¶20

Key Claims at a Glance

• The complaint asserts at least independent Claim 9. Compl. ¶21
• The essential elements of Claim 9, a method claim, are:
  • Adding a content based identifier (CBI), which is a hash value that enables verification of a hash-chained log, to an electronic communication via an outgoing electronic communication server.
  • Embedding the CBI in a field of the electronic communication that does not get modified when processed by a second communication server.
  • The field is a message identification header of the electronic communication.
  • Transmitting the electronic communication to a receiving system.
• The complaint reserves the right to assert additional claims. Compl. ¶21

U.S. Patent No. 12,399,987 - "Performing Authentication"

• Patent Identification: U.S. Patent No. 12,399,987, "Performing Authentication," issued August 26, 2025. Compl. ¶14

The Invention Explained

• Problem Addressed: The patent addresses the vulnerabilities of traditional authentication systems, where users may forget passwords and where secondary authentication methods, like security questions, can be insecure or also forgotten. '987 Patent, col. 1:50-59
• The Patented Solution: The patent describes a method for securely managing actions in a computing system by using a tamper-evident log. Crucially, it requires that information about a proposed action be appended to the log, and a cryptographic digital signature (an "attestation value") be obtained for that action, before the action itself is allowed to be performed. This "log-then-execute" sequence ensures that any tampering with the recorded action can be detected by verifying the signature against the logged information. '987 Patent, claim 1 '987 Patent, col. 13:17-32
• Technical Importance: This technique provides a robust framework for ensuring the integrity and auditable sequencing of operations in a distributed environment, a core requirement for systems that execute smart contracts or manage digital assets. Compl. ¶31

Key Claims at a Glance

• The complaint asserts at least independent Claim 1. Compl. ¶32
• The essential elements of Claim 1, a method claim for utilizing a tamper-evident log, are:
  • Before an action is allowed to be performed, appending information about the action to the log.
  • Before the action is allowed to be performed, obtaining an attestation value for the action computed using a cryptographic digital signature function.
  • Upon appending the information to the log, performing the action.
  • Wherein tampering of the log is detectable by verifying the information and the attestation value.
• The complaint reserves the right to assert additional claims. Compl. ¶32

U.S. Patent No. 12,411,949 - "Performing Authentication"

• Patent Identification (Multi-Patent Capsule): U.S. Patent No. 12,411,949, "Performing Authentication," issued September 9, 2025. Compl. ¶15

Technology Synopsis

This patent discloses a specific technical method for managing actions through a tamper-evident log, similar to the '987 Patent. It enhances the security of the process by requiring that the cryptographic attestation value be based not only on the action's information but also explicitly on a nonce, a time, and a date. It further requires that the performance of the logged action be associated with a resulting state change in the system. Compl. ¶42 '949 Patent, claim 8

Asserted Claims

The complaint asserts at least independent Claim 8. Compl. ¶43

Accused Features

The complaint alleges that the Kinexys blockchain infringes by logging transactions before execution, where the block-level attestation (signature) is based on transaction nonces and block timestamps, and where the execution of these transactions produces changes to account balances and smart contract data, which constitute a state change. Compl. ¶¶43-44

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are JPMC's Kinexys platform, which includes the Kinexys blockchain, Kinexys Digital Assets, Kinexys Digital Payments, and Blockchain Deposit Accounts. Compl. ¶16 Compl. ¶22

Functionality and Market Context

• The Kinexys platform is a private, permissioned blockchain based on Ethereum Virtual Machine (EVM) technology and utilizes Quorum, a permissioned version of Ethereum. Compl. ¶2 Compl. ¶17
• Functionally, it operates as a tamper-evident log where each block is cryptographically linked to the previous one via a parent hash, a structure intended to ensure immutability. Compl. ¶18
• The platform is alleged to process billions of dollars in tokenized asset transactions daily for institutional clients. Compl. ¶2 Compl. ¶17
• The complaint also accuses transactions involving JPMC's "JPM Coin Deposit Token" on Coinbase's "Base network," alleging it operates in a materially similar, infringing manner. Compl. ¶9 Compl. ¶25
• No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

8,185,733 Infringement Allegations

Claim Element (from Independent Claim 9)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
adding a content based identifier (CBI) to an electronic communication by an outgoing electronic communication server that processes the electronic communication for transmission...	A node on the Kinexys blockchain acting as a "block proposer" functions as an "outgoing electronic communication server" when it assembles a new block for propagation across the network. Compl. ¶21	¶21	col. 13:51-57
...the CBI a hash value and enables verification of integrity of a hash chained log...	The block proposer embeds a "parent-hash value," which is a cryptographic hash of the preceding block's contents. This hash value enables verification of the integrity of the entire blockchain (the hash-chained log). Compl. ¶21	¶21	col. 6:1-24
...wherein the CBI is embedded in a field of the electronic communication that does not get modified when the electronic communication is processed by a second communication server...	The parent-hash value resides in a field within the block's header that is not modified as the block is transmitted to, validated by, and replicated across other nodes in the network. Compl. ¶21	¶21	col. 17:10-21
...wherein the field is a message identification header of the electronic communication...	The parent-hash value is alleged to reside in a "message identification header" within the block, identifying the new block by reference to its predecessor. Compl. ¶21	¶21	col. 17:40-48
...and transmitting the electronic communication by the electronic communication server to a receiving system.	The block proposer propagates the newly assembled block across the network to other nodes, which function as receiving systems. Compl. ¶21	¶21	col. 18:4-6

12,399,987 Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
before the action is allowed to be performed, appending information about the action to the tamper-evident log;	On the Kinexys platform, a node records a newly assembled block (containing transaction information) to its local copy of the chain before the transactions within it are executed and their resulting state is committed. Compl. ¶32	¶32	col. 13:17-19
before the action is allowed to be performed, obtaining an attestation value associated with the action, the attestation value having been computed using a cryptographic digital signature function...	Each transaction is signed by its originator, and the block proposer signs the assembled block, yielding cryptographic attestations. A change to the underlying information would invalidate the signatures. Compl. ¶32	¶32	col. 13:19-25
upon appending the information about the action to the tamper-evident log, performing the action;	Only after the block has been appended to the chain and approved do the nodes execute the transactions contained within it, thereby performing the logged actions. Compl. ¶32	¶32	col. 13:26-27
wherein, tampering of the tamper-evident log is detectable by performing a verification using the information about the action and the attestation value for the action.	Tampering with the logged transaction information is detectable because it would invalidate the cryptographic signatures, which can be verified against the logged data. Compl. ¶32	¶32	col. 13:28-32

Identified Points of Contention

• Scope Questions ('733 Patent): A central dispute may arise over whether a blockchain "block" constitutes an "electronic communication" and its "header" constitutes a "message identification header" as those terms are understood in the patent. The defense may argue these terms are limited to the patent's email-centric examples, while the plaintiff may argue for a broader, functional interpretation that covers any sequentially linked digital record.
• Technical Questions ('987 Patent): The infringement analysis will likely focus on the precise sequence of events in the accused Kinexys platform. A key technical question is when an "action" is considered "performed" in the context of a multi-stage blockchain consensus protocol, and whether the Kinexys platform's logging operation provably occurs before that point, as strictly required by the claim.

V. Key Claim Terms for Construction

• The Term: "message identification header" ('733 Patent, Claim 9)

• Context and Importance: The infringement allegation for the '733 Patent hinges on construing a blockchain block header as a "message identification header." Practitioners may focus on this term because its construction will determine whether the patent, which uses email as a primary example, can read on modern blockchain technology.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The claim language itself is general and does not explicitly limit the term to email. The term could be argued to cover any field that serves to uniquely identify a communication and link it in a sequence.
  • Evidence for a Narrower Interpretation: The specification provides an example where the "Message-ID" header of an email is used to store the CBI, which could suggest the term is intended to refer to headers in email-like communication protocols. '733 Patent, col. 17:40-48 '733 Patent, col. 18:40-50

• The Term: "performing the action" ('987 Patent, Claim 1)

• Context and Importance: The claim requires several steps to occur before "performing the action." The definition of this term is therefore critical. In a distributed system like a blockchain, a transaction "action" involves multiple stages (e.g., initial execution, consensus, final state commitment). The specific point in this process that constitutes "performing the action" will be a central point of dispute.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The term could be construed to mean the final, irreversible commitment of a transaction's outcome to the global state of the ledger, which happens late in the process.
  • Evidence for a Narrower Interpretation: The specification discusses "performing an operation" and "executing a script" as examples of actions. '987 Patent, col. 1:56 '987 Patent, claim 2 This could support a view that the "action" is the initial execution of code by a node, which the complaint alleges occurs after the block is written to the log. Compl. ¶32

VI. Other Allegations

• Indirect Infringement: The complaint alleges JPMC actively induces infringement of all asserted patents. The factual basis includes JPMC allegedly instructing its institutional clients to use the infringing Kinexys platform. Compl. ¶24 Compl. ¶35 Compl. ¶46 The complaint also alleges inducement by JPMC initiating transactions on Coinbase's Base network, which allegedly causes Coinbase to directly infringe the patents. Compl. ¶25 Compl. ¶36 Compl. ¶47
• Willful Infringement: Willfulness is alleged for all asserted patents on the basis that JPMC has had "actual knowledge" of the patents "at least as of the filing of this Complaint" and has continued its allegedly infringing conduct without taking steps to design around the claims. Compl. ¶29 Compl. ¶40 Compl. ¶51

VII. Analyst's Conclusion: Key Questions for the Case

1. A core issue will be one of definitional scope: can the term "message identification header", rooted in the '733 Patent's description of email systems, be construed to cover the "parent hash" field within a modern blockchain "block header"? The case may turn on whether the function of the field, rather than its specific technological context, governs the claim's reach.

2. A key evidentiary question will be one of operational sequence: does the accused Kinexys platform, as a factual and technical matter, complete the "appending... to the tamper-evident log" and "obtaining an attestation value" steps before "performing the action," as strictly required by the '987 and '949 Patents? This will likely involve a detailed technical dispute over the precise definitions of these steps within the Quorum consensus and transaction execution lifecycle.

3. A significant strategic element of the case will be the plaintiff's secondary liability theory involving Coinbase. The success of this claim will require not only proving that Coinbase's Base network directly infringes, but also establishing that JPMC, by initiating JPM Coin transactions, acted with the specific intent to cause that infringement.