Private & secure · Post-quantum trust

Two signatures. Both required.

Every COSRYX receipt is signed twice: Ed25519, which everyone can verify today, and ML-DSA-65, a post-quantum signature. A verifier requires both. SLH-DSA-signed checkpoints are implemented, not yet deployed, and SLH-DSA archives are planned; key exchange will use X-Wing (implemented, not yet deployed). Your mission workspace stays under your control.

PQ-AgilityTested · 109 tests
X-WingNot yet deployed
RC3 freeze677/677 checks
External auditAudit not completed
00 Why two signatures

Mission records have to outlive today's cryptography.

A spacecraft can fly for decades. Its evidence should stay checkable for at least as long.

Classical signatures such as Ed25519 are fast, small and verifiable everywhere today. A large enough quantum computer would break them. ML-DSA-65 (FIPS 204) is designed to resist that. Each alone has a weakness: one is exposed to future quantum attack, the other is newer and less battle-tested.

COSRYX signs every receipt with both, over the same canonical bytes, and a verifier requires both. A missing leg is a failure, not a warning. Downgrade paths are rejected (COSRYX-HYBRID-02, 37/37).

For records kept for decades, an SLH-DSA (FIPS 205) archive leg is planned: a hash-based signature designed for post-quantum security under hash-function assumptions. Key exchange will use X-Wing, a hybrid key encapsulation (IETF draft), implemented and tested with the draft vectors, not yet deployed.

Post-quantum 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.
Internal security freeze (RC3) complete · External audit not completed · No flight qualification claimed.
01 Checking one receipt

Six checks, all offline.

Verify01 / 06
01 · CANONICAL BYTES

One exact byte form.

The receipt's fields are serialised into one canonical form, so every verifier hashes and checks exactly the same bytes.

02 · DIGEST

SHA-256 over those bytes.

Any change to any field, even one character, changes the digest and every check after it fails.

03 · ED25519

The classical leg.

Fast, small and supported everywhere. It verifies against the issuer's public key.

04 · ML-DSA-65

The post-quantum leg.

Verified over the same canonical bytes. PQ leg: ML-DSA-65 (FIPS 204) via the R-Series engine; software key custody; not flight-qualified.

05 · CHAIN

Parent and sequence.

Each receipt names its parent and carries a sequence number, so an inserted, removed or reordered record shows.

06 · ARCHIVE

A leg for the long run.

Long-lived records will add an SLH-DSA signature (planned), so the archive stays checkable as algorithms age.

02 The cryptography, labelled

What is used, and how far it has got.

ComponentRoleEvidenceStatus
Ed25519Classical signature leg on every R-Series receiptRequired by every verifierTested
ML-DSA-65Post-quantum signature leg (FIPS 204)Via the R-Series engine; software key custody; not flight-qualifiedTested
SLH-DSAHash-based archive leg (FIPS 205)For long-horizon records; checkpoints implemented, not yet deployedArchives planned
X-WingHybrid key encapsulationImplemented, tested with the draft vectorsNot yet deployed
CBOMCryptographic bill of materials11/11Tested
PQ-AgilitySwap algorithms without breaking old records109 testsTested
AI Sovereignty OracleFoundation controls for AI use249 foundation tests, 0 CVEsTested
03 Your workspace, your control

Private by design, honest about what is not built yet.

01 · WORKSPACE

Private mission workspace

Mission context, models, evidence and permissions inside one controlled boundary, with a human approval on high-impact actions.

Research preview
02 · KEYS

Bring your own key

Use approved provider keys and routing policies, so mission workflows stay under organisational control.

Design target
03 · BOUNDARIES

Data boundaries

Customer context, simulation data and source evidence kept separate, with retention and access agreed in writing per pilot.

Design target
04 · APPROVALS

Approval guardrails

Operator confirmation before uplinks, irreversible steps or wider autonomy; each approval is a receipt.

Research preview
05 · TOOLS

Air-gapped tool receipts

Tool calls create local, chained receipts without network modules or raw payload retention (COSRYX-HYBRID-03, 28/28).

Built · definition-of-done sign-off pending
06 · DEPLOYMENT

Sovereign and on-premises

Private-cloud, sovereign and on-premises options need product engineering, security review and customer-specific work before we offer them.

Future direction
04 Security evidence, by population

Counts that name what they count.

677/677RC3 security-gate checks (internal security freeze)Tested
109PQ-Agility testsTested
249AI Sovereignty Oracle foundation tests, 0 CVEsTested
0external audits completed; the external audit (G2) is pendingAudit not completed
Soak records. 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. See the evidence page on cosryx.com.
05 What we add

Evidence on top of your security, not instead of it.

COSRYX does not replace link encryption, command authentication or ground-segment security. Those stay with the mission. We do not replace mission security; we add mission evidence.

What we add is a record that survives: who commanded what, what the spacecraft decided, how its health changed, signed twice and chained, so a third party can check it later without trusting the operator, the vendor or us.

Trust the receipts, not the vendor. Including us.

06 Questions

About security and privacy.

Is the post-quantum leg finished?

Not yet. The signing design is hybrid. 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.

Has anyone outside COSRYX audited it?

No. The internal security freeze (RC3) is complete with 677/677 internal security-gate checks; the external audit is not completed.

Can we keep everything on our own servers?

Not yet. Sovereign, private-cloud and on-premises deployment are a future direction. Pilot data boundaries are agreed in writing.

Do receipts contain our raw mission data?

Receipts carry digests and commitments, not the raw content, so evidence can be shared without exposing the data itself.

07 Pilot

Check our receipts yourself.

A security-focused pilot starts with a receipt bundle and the public keys. Your team verifies it offline.

Request pilot accessEvidence on cosryx.com