LatticeWorks, LLC · Delaware

A company built around
one protocol.

LatticeWorks exists to develop, license, and defend the Lattice Transfer Protocol. Single product. Deliberate go-to-market. NIST-grounded math. Built for regulated infrastructure that has to be right the first time.

// Founder

Jas Strokus

Creator, Lattice Transfer Protocol · Founder, LatticeWorks

Jas designed LTP after concluding that the urgency of post-quantum migration was being met with retrofit thinking — wrapping legacy transfer protocols in new primitives — rather than rebuilding the transfer layer around what lattice cryptography actually makes possible.

LatticeWorks is the result: a focused company built around the protocol, deliberately licensed by field of use, and aligned to the cadence of regulated infrastructure rather than the cadence of software product cycles.

The transfer layer should be boring, verifiable, and built from primitives that hold up under both classical and quantum scrutiny. The interesting work is making that the default.
// Origin

The three constraints that shaped the internet don't shape this.

LTP began with a question about interplanetary communication: how do you move data between Earth and Mars when the link is slow, lossy, and minutes deep in light-lag? The honest answer was that you don't — not the way we move data today. The file can't make the trip. But a mathematical description of it can, and the file can be rebuilt on the other side, verifiably identical. Once that works at planetary distance, distance itself stops being the interesting problem.

Bandwidth. Latency. Distance. — solved in the commit, not the wire.
// How we operate

Four principles, applied consistently.

These are not aspirations. They are the operating decisions that shape what LatticeWorks ships, who we license to, and what we refuse to do.

01

Standards over novelty.

Only NIST-finalized lattice primitives: ML-KEM (FIPS 203) and ML-DSA (FIPS 204). No homebrew cryptography, no proprietary curves, no unproven assumptions. The math has to be auditable by a third party in an afternoon.
02

Field-of-use, not platform.

We license LTP into specific verticals — regulated finance, defense and space, healthcare, critical infrastructure, AI and ML pipelines — under terms that match how those industries actually procure technology. We are not building a horizontal platform.
03

Quiet over loud.

Selective engagement. We respond to inquiries, share material under NDA, and let the protocol do the talking. The cost of being wrong about a security claim is higher than the cost of being slow to publish one.
04

Composable, auditable, durable.

Every claim LTP makes is reducible to a standard hardness assumption. Every shard is verifiable. Every transfer either materializes correctly or doesn't materialize at all. We build for systems with decades of shelf life.
// Where we are

A short arc, moving deliberately.

LatticeWorks is a small company doing a specific thing. The roadmap below is intentionally loose on specifics — we'd rather under-promise and ship than the reverse.

Origin

Protocol design

Initial LTP architecture, reference implementation, and whitepaper drafted. Three-phase pipeline formalized.

2026

Patent pending

Provisional patent application filed. Technical paper available to evaluators under NDA.

Now

Engaging selectively

Active field-of-use licensing conversations in regulated finance. Evaluation requests welcomed across other verticals.

Next

v1 — Reference implementation in Rust

Production-grade LTP implementation in Rust. Memory-safe by construction, built for the environments the protocol is licensed into.

Forward

The transfer layer

As post-quantum mandates accelerate, LTP becomes the default transfer primitive for systems that have to be right the first time.

Want to know more?

The protocol is documented. The math is auditable. The licensing model is deliberate. The next step is a conversation.

Open a channel →