Ecosystem Patents¶
Soqucoin Labs Inc. has filed a portfolio of United States provisional patent applications covering the post-quantum techniques used across the ecosystem. Each is filed under 35 U.S.C. 111(b) and converts to a non-provisional within twelve months to maintain priority. Assignee: Soqucoin Labs Inc.
This page summarizes what each patent covers and why the technique is needed, grouped by product line: the blockchain (Soqucoin L1), the custody and settlement software (SOQ-TEC), and the compliance product (PQCAT).
Soqucoin L1 (blockchain)¶
| Patent | Application | What it covers | Why it is needed |
|---|---|---|---|
| PAT (Practical Attestation Technique) | SOQ-P001, 64/022,954 | Commits a batch of ML-DSA signatures to a fixed 100-byte Merkle root that attests to them; the signatures themselves stay in witness data. | ML-DSA-44 signatures are 2,420 bytes each. PAT gives a constant-size on-chain commitment so per-block verification and footprint stay tractable. Active from genesis. |
| SoquObscura Confidential Transactions | SOQ-P010, 64/131,585 | Amount-hiding transactions using ABDLOP lattice commitments with LNP22 range/balance proofs and LaBRADOR block-level aggregation. See SoquObscura. | Quantum-safe on-chain privacy without elliptic-curve cryptography. In development. |
| Lattice-BP++ Confidential Transactions | SOQ-P002, 64/023,515 | Ring-LWE commitments, lattice ring signatures, and Dilithium-compatible stealth addresses for opt-in privacy. | The foundational lattice-privacy techniques. Superseded in implementation by SoquObscura; the patent covers the underlying methods. |
| LatticeFold UTXO-Bound Batch Verification | SOQ-P004, 64/026,715 | Recursive lattice folding for batch ML-DSA signature verification. Not amount-hiding. Deprecated: OP_CHECKFOLDPROOF remains in the tree behind a deployment that does not activate on any network; reviewed in the April 2026 external extension audit. |
Was a verification-scaling research track. Superseded by SoquObscura (SOQ-P010) for confidential assets and succinct proofs. Research record only. |
| USDSOQ Consensus-Enforced Stablecoin | SOQ-P007, 64/047,929 | Native UTXO asset typing with threshold lattice authority and consensus-enforced mint, burn, and freeze operations. See USDSOQ. | A stablecoin whose supply invariant and controls are enforced by consensus on a quantum-safe chain. Active on stagenet. |
SOQ-TEC (custody and settlement software)¶
| Patent | Application | What it covers | Why it is needed |
|---|---|---|---|
| SoquShield Post-Quantum Mobile Wallet | SOQ-P003, 64/023,076 | ML-DSA-44 key generation and signing in a managed cross-platform runtime (Dart/Flutter) across iOS, Android, and web. | Makes post-quantum key management usable on consumer mobile devices from a single codebase. |
| XMSS-Lite Revolving Vault | SOQ-P005, 64/035,857 | Hash-based one-time-per-leaf custody that advances the signing leaf after each use. | A captured signing key is usable at most once, so a compromise does not drain the vault. See SOQ-TEC. |
| Quantum Express Cross-Chain Transfer | SOQ-P006, 64/035,873 | Optimistic cross-chain asset transfer with deferred post-quantum attestation and fraud-proof windows. | Reduces cross-chain confirmation latency without giving up post-quantum security. Design stage. |
PQCAT (compliance)¶
PQCAT is Soqucoin Labs' post-quantum cryptography compliance scanner, a separate product line. Twelve applications are filed. They are grouped below by technique family rather than by filing order, because the families are what the techniques actually have in common: a group builds on one shared mechanism, and later applications in a group extend the earlier ones rather than standing apart from them.
Confidential commitment and selective disclosure¶
How an inventory is committed, and how little of it has to be revealed to prove something about it.
| Patent | Application | What it covers | Why it is needed |
|---|---|---|---|
| Confidential Compliance Engine (CCE) | PQCAT-P001, 63/999,796 | Privacy-preserving compliance verification that proves an organization's post-quantum posture without disclosing its inventory. | An agency or enterprise will not hand a vendor a map of its infrastructure. A compliance claim that requires one does not get made. |
| Graduated Selective Disclosure | PQCAT-P011, 64/122,032 | Opens one class of a committed inventory to a counterparty using domain-separated derived subsalts, while every other class stays sealed under the same root. | An auditor needs one slice, not the estate. What stays sealed includes the number of assets in it, not only their contents. |
| Retained-Root Cross-Boundary Disclosure | PQCAT-P019, 64/126,720 | Verifies a returned opening against the commitment root the requester retained when it issued the request, never against the root the returned artifact carries. | A responder can mint its own commitment over an inventory of its choosing and open it honestly. Checking an opening against its own root proves only that the responder is consistent with itself. |
Provenance-bound reporting¶
Turning a technical inventory into something reportable, and recording how every value in it was established.
| Patent | Application | What it covers | Why it is needed |
|---|---|---|---|
| Provenance-Bound Compliance Reporting | PQCAT-P015, 64/125,634 | Binds discovered cryptographic assets to authoritative system-of-record identifiers and commits, per reported value, whether a scanner observed it, an identified export supplied it, or a named person asserted it. | Several of the data items a federal report requires do not exist in the assessed infrastructure at any scan quality. Typing them into a spreadsheet produces an opinion formatted as a table. |
| Cryptographic Agility Index | PQCAT-P016, 64/126,113 | Scores each asset by what must change to move its algorithm, weighted by control tier, and publishes the definition so a third party can reproduce any figure without the software. | The federal mandate requires systems to be cryptographically agile and defines no metric for it, so organizations are asked to attest to a property nobody has specified. |
| Migration Plan Derivation | PQCAT-P018, 64/126,407 | Derives the required migration-plan contents from the inventory, marks each section by the sufficiency of its inputs, and withholds figures that have no authoritative basis. | A cost basis invented inside a federal funding request is an audit finding. The technique declines to supply one rather than defaulting it. |
Evidence across time¶
Claims that compare two points in time: what changed, what was already exposed, and what was previously missed.
| Patent | Application | What it covers | Why it is needed |
|---|---|---|---|
| Cryptographic Remediation Transaction | PQCAT-P012, 64/122,047 | Proves an asset moved from vulnerable to compliant between two scans, with ordering established cryptographically rather than by a timestamp. | A tracker should close a finding on evidence that the fix happened, not on an assertion that it did. |
| Backward-Looking Harvest Exposure Clock | PQCAT-P014, 64/122,164 | Measures ciphertext already collectable, in asset-years, and which of it becomes readable at a forecast decryption event. | Harvest-now-decrypt-later exposure accrued before today. A forward-looking risk score misses all of it. |
| Retro Reconciliation and Fidelity Attribution | PQCAT-P017, 64/126,154 | Reconciles an inventory against a prior submission and attributes each added asset to improved inventory fidelity or to genuine growth, per asset, from evidence the asset itself carries. | A better scanner raises the reported count, which reads as a program going backwards. Without per-asset attribution, the safe move is to scan narrowly. |
| CCE with HNDL Risk Quantification | PQCAT-P001B, 64/023,449 | A harvest-now-decrypt-later exposure scoring model layered on the compliance engine. | Ranks what to migrate first by what is actually being collected today, rather than by algorithm age. |
Hardware and infrastructure discovery¶
Reaching cryptography that host-based scanning does not see.
| Patent | Application | What it covers | Why it is needed |
|---|---|---|---|
| Firmware Region-Bound Compliance Verdict | PQCAT-P013, 64/122,137 | Binds a verdict to a digest of the exact firmware bytes, so verification requires the verifier's own re-dump of the device. | The least patchable cryptography sits below the operating system. A verdict about it should not rest on trusting whoever ran the scan. |
| Cloud-Native PQ Compliance Assessment | PQCAT-P010, 64/023,535 | Automated discovery and CNSA 2.0 scoring of cryptographic assets across cloud infrastructure. | Cryptography terminated inside managed cloud services is not enumerable by scanning hosts. |
A single non-provisional application may claim the benefit of more than one provisional under 35 U.S.C. 119(e), so related applications within a family may be converted together rather than one for one.
Full detail lives at pqcat.io.
Twenty United States provisional applications are filed and assigned to Soqucoin Labs Inc. "Patent pending" reflects a filed provisional application; it does not indicate a granted patent, and a provisional is not examined.