Files
warp/PATENTS.md
zeekay 74fccc88ac submission: Tier A documentation pack
Adds the canonical submission-doc shape adapted from luxfi/pulsar to
warp's nature (transport-agnostic envelope + posture gate, not a
threshold-sig primitive).

New files:

- SUBMISSION.md           cover sheet, scope, headline claim
- PROOF-CLAIMS.md         honest scope — what warp proves AND what it
                          does NOT (bridge-quorum trust inheritance,
                          PQ hardness of primitives, ML-DSA
                          aggregation primitive, transport-layer
                          integrity, validator-key custody)
- TRUSTED-COMPUTING-BASE.md TCB inventory (cryptographic primitives,
                          implementation, build, operational, OOS)
- PATENTS.md              royalty-free patent grant + defensive
                          termination mirroring Apache-2.0 §3
- CRYPTOGRAPHER-SIGN-OFF.md APPROVED WITH GATES verdict; reviews
                          envelope.go, security_profile.go, the new
                          registry, and the e2e/fuzz harnesses; pins
                          4 open gates (cross-language port schedule
                          disclosure, transport-layer integration
                          shape confirmation, LP-073 §11 disclaimer
                          addition, warpcli completeness)
- DEPLOYMENT-RUNBOOK.md   operator-facing — posture decision flow,
                          chain config, validator key rollout, prod
                          checklist, common failure modes, monitoring
- CHANGELOG.md            Tier A push entry; semantic-versioning at
                          the wire-format level
- LEGACY-CLASSICAL.md     operator-facing classical-opt-in policy +
                          three-phase deprecation timeline
                          (target 2027-Q4 for full removal)
- TRANSPORT.md            transport-layer notes — warp produces
                          transport-agnostic signed envelopes
                          consumed by ZAP-transport-capable
                          subsystems (luxfi/zap inter-node); warp
                          itself does NOT import luxfi/zap (keeps
                          dependency direction clean)

Updates to existing:
- README.md      Tier A status banner, submission-doc cross-links,
                 related-modules grid
- PQ_PROFILES.md two-layer-gate documentation (registry +
                 chain-mode), pointer to LEGACY-CLASSICAL.md
- SPECIFICATION.md PQ-native default banner, MLDSACertSet context-
                 binding section (FIPS 204 §5.2 / FIPS 205 §10.2
                 context-string requirement under the canonical tag
                 "lux-warp-cross-chain-v1")

The four open gates in CRYPTOGRAPHER-SIGN-OFF.md are documentation /
operational items, not algorithmic defects. The construction itself
is APPROVED.

No code changes in this commit; subsequent commit adds the e2e and
fuzz test files referenced by the sign-off.
2026-05-19 08:36:15 -07:00

6.8 KiB

PATENTS — Lux Warp 2.0 Cross-Chain Messaging

Statement of Intellectual Property and Royalty-Free Patent Grant for the Lux Warp cross-chain messaging protocol.

TL;DR

Lux Industries, Inc. ("Lux") grants a worldwide, royalty-free, non-exclusive, irrevocable patent license for any implementation of Lux Warp that conforms to the EnvelopeV2 wire format pinned in SPECIFICATION.md AND is either (a) licensed under BSD-3-Clause-Eco, BSD-3-Clause, Apache-2.0, or a compatible OSI-approved license, OR (b) is a port, validation, or interoperability test of the protocol.

The grant terminates automatically and prospectively against any party that asserts a patent claim against Lux Warp, FIPS 204 ML-DSA, FIPS 205 SLH-DSA, BLS12-381, or any conforming implementation thereof. Defensive termination mirrors Apache-2.0 §3.

The full text of the grant is in §3 Patent Grant below.

§1 Scope of the IP statement

This document covers patent rights and patent posture for:

  • The EnvelopeV2 wire format specified in SPECIFICATION.md.
  • The posture-gate composition (pq.ValidateMode over EnvelopeV2.HasPQEvidence) pinned in security_profile.go and PQ_PROFILES.md.
  • The reference implementation in this repository.
  • The KAT vectors in scripts/kat/envelope_kat.json and the oracle that generates them.
  • The cross-language reference ports (Rust lux_warp, TypeScript @luxfi/warp) when they conform byte-for-byte to the KAT manifest.

It does NOT cover, and explicitly DISCLAIMS, the following prior art:

Component Status
FIPS 204 ML-DSA-65 Public domain — NIST standard.
FIPS 205 SLH-DSA Public domain — NIST standard.
BLS12-381 pairing-friendly curve Academic / public domain (Bowe / Boneh-Lynn-Shacham).
Module-Lattice (MLWE / MSIS) Academic / public domain.
Ring-LWE Academic / public domain.
Avalanche / Subnet Warp Messaging upstream Apache-2.0 open-source upstream (ava-labs); Lux Warp is a PQ-native fork — no Lux patents asserted against the upstream.
RLP encoding Public domain (Ethereum specification).
BLS aggregate signature scheme Academic / public domain (Boneh-Drijvers-Neven).
SHA-256 / SHA3-256 / Keccak Public domain — NIST standards FIPS 180-4 / FIPS 202.
The general concept of "cross-chain messaging with PQ migration" Documented in academic literature and prior systems; Lux Warp's specific wire-format and posture-gate composition is the novel contribution.

§2 What Lux considers patentable (high level)

Subject to attorney review, Lux considers the following Warp 2.0 contributions to be candidates for patent protection:

§2.1 PQ-native envelope with classical-opt-in posture gate

The specific composition of:

  • A wire format (EnvelopeV2) that carries a classical Beam, an optional Pulse (R-LWE threshold), and an optional MLDSACertSet (FIPS 204 per-validator attestations) over the same transcript;
  • A posture gate (pq.ValidateMode) that dispatches three named modes (classical / hybrid / strict-pq) to the appropriate verifier path through a SINGLE function call;
  • A signature-scheme registry (signature.Config.LegacyClassicalEnabled) whose default posture refuses classical primitives at install time, decomplected from the chain-level posture gate;
  • The single-sentinel error model (pq.ErrClassicalAuthForbidden) used uniformly across every refusal site in the system.

§2.2 Transcript-binding domain separation

The specific binding "WARP-PULSAR-ENVELOPE-v1" || SourceChainID || SourceNebulaRoot || SourceKeyEraID || SourceGeneration || HashSuiteID || UnsignedMessage.Bytes() that prevents replay across:

  • Pulsar consensus-layer pulses ("QUASAR-PULSAR-BUNDLE-v1");
  • Warp envelopes (this tag);
  • ML-DSA cert-set attestations ("lux-warp-cross-chain-v1").

Distinct context strings per domain are required by FIPS 204 §5.2 context-string binding; the SPECIFIC concatenation here is what Lux considers novel.

§2.3 Cross-version envelope dispatcher

The 0x02-prefixed wire framing that allows a single ParseEnvelope function to dispatch both Warp 1.x (legacy bare RLP message) and Warp 2.0 (versioned envelope) inputs, lifting v1 bytes into a v2 envelope shape with empty PQ lanes. The dispatcher's correctness depends on the fact that RLP lists NEVER start with 0x02 (RLP single-byte values < 0x80 ARE the value itself; lists start at 0xc0).

§3 Patent Grant

Lux Industries, Inc. ("Lux") hereby grants to every person and entity a worldwide, royalty-free, non-exclusive, irrevocable patent license under any Patent Claims of Lux that read on the Lux Warp Protocol (as defined in SPECIFICATION.md of this repository) to make, use, sell, offer for sale, import, and otherwise transfer the Lux Warp Protocol, IF AND ONLY IF the implementation EITHER:

  1. Conforms to the EnvelopeV2 wire format pinned in SPECIFICATION.md AND is licensed under BSD-3-Clause-Eco, BSD-3-Clause, Apache-2.0, MIT, or another OSI-approved license that grants the same rights to its recipients; OR

  2. Is part of a port, validation, or interoperability test of the Lux Warp Protocol that is published under an OSI-approved license; OR

  3. Is a fork or derivative of this repository that retains the wire format byte-equality with the KAT manifest in scripts/kat/envelope_kat.json.

"Patent Claims of Lux" means any patent claims owned or controlled by Lux that would necessarily be infringed by implementing the Lux Warp Protocol as specified.

Defensive termination. This grant terminates automatically and prospectively against any party that initiates patent litigation (including a cross-claim or counterclaim) against Lux, Lux Warp, FIPS 204 ML-DSA, FIPS 205 SLH-DSA, BLS12-381, or any conforming implementation thereof, alleging infringement by the recipient's use of the Lux Warp Protocol. Defensive termination mirrors Apache-2.0 §3 and extends to all NIST-standardized post-quantum cryptographic primitives.

No grant for non-conforming implementations. A modified wire format that breaks byte-equality with the KAT manifest is NOT a conforming implementation and receives no patent grant under this document. Forks are encouraged; wire-format breaks are NOT licensed under this grant.

§4 Attribution and trademarks

"Lux Warp" and "Lux Network" are trademarks of Lux Industries, Inc. This patent grant does not include a trademark license. Forks and derivatives are encouraged to use distinct names for their wire- incompatible variants.

§5 Contact

Patent questions, royalty-free-grant applicability questions, and attorney-prep claim drafts should be directed to the Lux Industries patent counsel via the repository's MAINTAINERS.md.


Document metadata

  • Name: PATENTS.md
  • Version: v1.0 (Tier A)
  • Date: 2026-05-18