Technology · Status as of 21 October 2026

Receipts that survive the distance.

Every COSRYX product issues DCS R-Series receipts: canonical records signed twice, chained by hash, and checkable offline by anyone with the public keys. This page explains how, and where the limits are today.

SignaturesEd25519 + ML-DSA-65
VerificationOffline · no account
PQ legML-DSA-65 (FIPS 204) via the R-Series engine; software key custody; not flight-qualified
External auditAudit not completed
01 Why receipts

Logs say what happened. Receipts let you check.

A spacecraft log is written by the spacecraft, in its operator's format, stored where its operator decides. When something goes wrong, everyone outside that operator has to take the log on trust.

A receipt is different: a small, self-contained, signed statement about one action. It names what was done, by which unit, under which mission intent, at what time, and the hash of the receipt before it. Anyone can verify it later without trusting the system that wrote it.

COSRYX builds on the DCS R-Series trust layer, the receipt standard DCS Labs develops for AI agents and machines, and applies it to commands, autonomous decisions and health records in space.

02 One receipt, five steps

From an action to something a stranger can verify.

Trust layer01 / 05
STEP 01 · THE RECEIPT

Write the action down, completely

Each receipt carries the action, the acting unit, the mission intent it was taken under, a canonical timestamp, a hash of the result, and prev: the hash of the receipt before it.

STEP 02 · CANONICAL HASH

Same record, same bytes, everywhere

The receipt is reduced to one canonical byte form and hashed with SHA-256. A ground station and a rover computing the same receipt get the same fingerprint, bit for bit.

STEP 03 · HYBRID SIGNATURE

Two algorithms, both required

Ed25519 (classical) and ML-DSA-65 (post-quantum) sign the same bytes. A receipt with only one valid leg is refused. Partial signatures never enter the chain.

STEP 04 · THE CHAIN

Each receipt names the one before

Deleting, reordering or editing any receipt breaks every link after it. A gap is not hidden; it is visible to the first person who checks.

STEP 05 · OFFLINE VERIFY

No network, no account, no trust in us

A verifier needs only the receipts and the public keys. It recomputes each hash, checks both signatures and walks the chain, on an air-gapped laptop if need be.

03 Hybrid signatures

Classical and post-quantum, together.

Spacecraft records may need to be checked decades after they are written, possibly after large quantum computers exist. So every R-Series receipt is signed with a lattice-based post-quantum algorithm, ML-DSA-65 (FIPS 204), alongside Ed25519.

The hybrid rule is strict: both legs must verify over the same canonical bytes, and downgrade paths (one leg, or the weaker leg alone) are rejected before any signature work begins.

PQ-Agility, the foundation product behind this, also generates a CycloneDX cryptographic bill of materials and an executable deprecation calendar, so a mission knows which algorithms it runs and when each must change.

The honest caveat. 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.
109PQ-Agility product tests, with X-Wing key encapsulation (IETF draft; implemented and tested with the draft vectors, not yet deployed) and CBOM 11/11 against reference vectors

Tested

04 Founder feature · Mars without round trips

Send the plan once. Verify the decisions later.

A message to Mars takes between about 3 and 22 minutes one way, depending on where the planets are, and the same again back. Ground control cannot steer a rover in real time. COSRYX does not try to.

Signed intent01 / 05
01 · THE DISTANCE

3 to 22 minutes, each way

Light takes minutes to cross between Earth and Mars. A question and its answer cost up to about 44 minutes, before anyone has even thought about the answer.

02 · THE OLD LOOP

Ask, wait, answer, wait

If every significant action needs permission, a rover spends most of its life waiting. Each round trip is lost time, and lost opportunity when conditions change.

03 · ONE SIGNED INTENT

The plan travels once

COSRYX pre-authorises signed intents: the mission plan and the actions the rover is allowed to take are signed on Earth and sent once.

04 · AUTONOMY IN BOUNDS

The rover acts inside those bounds

The rover executes autonomously, but only within the signed limits. An action outside the bounds is not taken. No repeated ask-and-wait loops.

05 · VERIFIED AFTERWARDS

Every decision is receipted

Each autonomous decision becomes a receipt tied to the intent that allowed it. When the receipts reach Earth, anyone can verify what was done and why.

COSRYX-EDGE · BuiltCOSRYX-MCC · BuiltSimulation-validatedDSRP · Simulation-validated
05 The numbers behind the delay

Why real-time control does not work at Mars.

~3 minone-way light time at Mars's closest approach
~22 minone-way light time near the far side of the Sun
1 tripfor a signed intent, instead of a round trip per decision

Light-time figures are approximate and depend on planetary positions. They describe physics, not COSRYX test results.

06 Architecture

Five layers, from objectives to evidence.

LAYER 01

Mission objectives and constraints

Scientific goals, priorities, operating rules, energy limits, communication windows and approval requirements: the raw material of a signed intent.

LAYER 02

Planetary and operational context

Telemetry, terrain, orbital conditions, environment data, subsystem health and mission history.

LAYER 03

Reasoning and simulation

Planners, worker agents, models and deterministic tools compare options and simulate outcomes before acting.

LAYER 04

Relay and autonomous systems

Communication priorities, bounded autonomous actions and recovery strategies under disruption, carried by DSRP.

LAYER 05

Evidence, review and governance

Sources, confidence, assumptions, retries, approvals and decisions, written as receipts and kept in the mission recorder.

WHERE IT LANDS

COSRYX V2 mission recorder

The distributed black box that holds the chain. G0 and G1 complete.

Inside the recorder →
07 A receipt, in full

Small enough to send over a thin link.

An illustrative receipt for one autonomous drive decision. The field names are simplified; the structure is the point: who, what, under which intent, chained to the previous record, signed twice.

// illustrative receipt (simulated values)
{
  "action":  "drive.segment",
  "actor":   "rover-02/edge",
  "intent":  "plan#771",        // the signed intent that allowed it
  "bounds":  "within",
  "time":    "2026-10-11T09:14:05Z",
  "result":  "sha256:9c41…e07a",
  "prev":    "sha256:51d0…7b2c",   // the chain
  "sig": {
    "ed25519":   "…",
    "mldsa65":   "…"          // ML-DSA-65 (FIPS 204) via the R-Series engine
  }
}
08 Future direction

One evidence network from Earth to Mars.

The long-term direction is to link Earth, the Moon and Mars into one verifiable communication and evidence network: an interplanetary relay where every hand-off is a receipt.

COSRYX-NEXUS already simulates an Earth–Moon–Mars custody chain that survives link outages. Building the real network is a future direction, not a plan with dates. Future direction

09 What the trust layer is not

Evidence, not a replacement for security.

It does

  • Make each action independently checkable after the fact
  • Expose deletions, edits and reordering
  • Bind autonomous decisions to the intent that allowed them
  • Survive long link outages through store-and-forward

It does not

  • Replace link encryption or command authentication
  • Make a spacecraft safe on its own
  • Carry flight qualification, certification or an external audit today
  • Hold its post-quantum keys in hardware custody yet (key custody in this stage is software; hardware custody certification is pending)

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

10 Required statements

The three lines we print in full.

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.
11 Questions

Asked about the technology.

Why sign twice?

Ed25519 is fast, small and well understood today. ML-DSA-65 is designed to resist quantum attacks. Requiring both means a record stays trustworthy if either algorithm is later weakened.

What produces the post-quantum signatures?

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.

Can a rover really act without asking?

Within signed bounds, yes, in simulation today. COSRYX-EDGE and COSRYX-MCC are built and simulation-validated; nothing has flown.

Do you need to trust COSRYX to verify a receipt?

No. The verifier needs the receipts and the public keys. It runs offline.

Has this been audited?

Not externally. The internal security freeze (RC3) is complete, with 677 internal security-gate checks. The external audit is gate G2 and is not completed.

12 Next

See where the receipts are kept.

The COSRYX V2 mission recorder holds the chain, through link loss and back.

Mission recorderMission health