Most zero-knowledge-proof patents claim a proving protocol — the math by which a prover convinces a verifier of a statement without revealing the underlying secret. US12367490B2, “Computer-implemented system and method for enabling zero-knowledge proof,” granted to nChain Licensing AG on July 22, 2025, frames itself differently, and the difference is worth reading carefully: it claims enabling a proof, not merely performing one.
The distinction is not pedantic. A zero-knowledge proof in the abstract is a protocol; a zero-knowledge proof in a real system needs scaffolding — a way to set up the parameters, encode the statement to be proven, connect the proof to the data it is about, and integrate verification into the surrounding application. The breadth of the CPC tags here — spanning data-structures (G06F 16/2379), payment codes (G06Q 20/389), and a long list of cryptographic mechanisms — reflects that this is a systems claim, not a single algorithm.
nChain is a prolific blockchain-patent filer with a large and deliberately broad portfolio, which colors how to read this grant. The “enabling” framing and the wide CPC spread are consistent with a strategy of claiming the practical machinery around a technique, not just the technique — the kind of patent whose value lies in its scope and its place in a portfolio as much as in a single inventive step.
This is exactly where this desk's editor-in-chief insists on caution. A broad systems claim invites the misreading that the patentee “owns zero-knowledge proofs,” which it does not — it owns a specific claimed method of enabling them, whose true scope is whatever the independent claims actually recite and survived examination. The headline temptation (“company patents ZKP”) is almost always wrong; the claim language is narrower than the title.
Per the desk's rules: issued grant (B2), not an application; a system/method claim, not a product. nChain's blockchain-IP business is the context, and its filing strategy is well known to favor breadth.
For the IP-strategy reader, the lesson is to treat “enabling” and “system and method” framings as signals to read the independent claim, not the title. The interesting question is never whether someone patented zero-knowledge proofs in general — they did not — but exactly which slice of the deployment machinery a given grant fences off.