COSRYX.com · Status as of 21 October 2026

Mission evidence for space.

COSRYX builds verifiable mission intelligence for space: every command, decision and health record a spacecraft or rover produces becomes evidence a third party can check later.

Twelve products are built and internally tested on one trust layer: signed, hash-chained receipts that anyone can verify offline. Code gates G0 and G1 are complete. Radiation testing is next.

Code gatesG0 + G1 complete
Product tests692 / 692
RC3 security freeze677 / 677 checks · internal
External auditAudit not completed
SCROLL
01 What COSRYX is

A black box that a third party can read.

Space missions already protect their links. What they rarely keep is evidence: a record of what was commanded, what the spacecraft decided on its own, and how its hardware was doing, in a form an outsider can check years later without trusting the operator's word.

COSRYX is the space research line of DCS Labs. Every COSRYX product writes its actions as DCS R-Series receipts: small signed statements, each naming the one before it, signed twice (Ed25519 and ML-DSA-65) and checkable offline.

The software is built and internally test-green. It is not flight-qualified, it has not been through an external audit, and no launch contract is signed. This site says exactly which of those is which.

We do not replace mission security; we add mission evidence.

02 How one record becomes evidence

Five steps from an action to a proof.

Trust layer01 / 05
STEP 01

The action is written down

A command arrives, the rover plans a drive, a battery reading is taken. Each becomes a receipt: what happened, who or what did it, under which mission intent, and when.

STEP 02

It is hashed canonically

The receipt is reduced to canonical bytes and hashed with SHA-256, so the same record always produces the same fingerprint on any machine.

STEP 03

It is signed twice

Ed25519 and ML-DSA-65 sign the same bytes, and both legs are required. PQ leg: ML-DSA-65 (FIPS 204) via the R-Series engine; software key custody; not flight-qualified.

STEP 04

It joins the chain

Each receipt names the hash of the one before it. Removing, reordering or editing a record breaks every link after it, visibly.

STEP 05

Anyone can check it, offline

A verifier needs the receipts and the public keys, nothing else: no network, no account, no trust in COSRYX. That is what makes it evidence rather than a log.

05 COSRYX V2 mission recorder

Two gates closed. Six to go.

COSRYX V2 is a verifiable mission recorder: a distributed black box that keeps the last verified state, decision history and command lineage of a spacecraft, even when the link is down.

410/410integrated tests, C0–C9 all GOG1 complete
5,447of 5,447 manifest entries reproducedG0 complete
Inside the recorder
06 Roadmap

Radiation testing next. Then our own CubeSat.

Done · internal

G0 + G1 · RC3 freeze · 12 products built

Code gates complete, internal security freeze complete. Internal results, not an external audit.

Then

COSRYX's own 6U CubeSat

Target about 18 months after radiation testing. Planning stage, subject to funding and licensing. No launch contract is signed.

The full public roadmap
07 Trust layer

Every number names its population.

692product tests across 12 products and the Hybrid MoatInternal
410integrated tests for COSRYX V2 (gate G1)Complete
677RC3 internal security-gate checksFreeze complete
0external audits completed. This is the next outside gate (G2)Audit not completed
Internal security freeze (RC3) complete · External audit not completed · No flight qualification claimed.
The post-quantum (PQ) leg uses ML-DSA-65 (FIPS 204) via the R-Series engine. Key custody in this stage is software; hardware custody certification is pending. Not flight-qualified. Not independently audited.
No launch contract is signed.
08 Our own satellite

A test bench we own.

With a COSRYX-owned CubeSat we can run our own payload tests: power-cycle the payload, check that it re-acquires the signal, and run controlled fault drills, with every step receipted.

This is a plan, not a mission. It depends on radiation testing first, then funding and licensing. Planning

The CubeSat plan
09 A correction we keep visible
Earlier internal soak records were withdrawn on 30 August 2026 because the verdict logic could not report a failure; corrected records will be re-issued as a set. No figure from those records appears on this site. Read the evidence page →
11 Talk to us

Bring a mission question. Leave with evidence.

Research collaborations, technology evaluations and investor conversations start with a defined problem and a written scope.