INDEPENDENT PROOF. AUTONOMOUS SYSTEMS.

The proof layer formachines that acton their own.

Signed evidence for connected AI workflows and cryptographic change.
R-Series is designed to record captured intents, approvals and outcomes so that the resulting receipts can be checked independently.

Explore the research

HYBRID SIGNATURES Ed25519 + ML-DSA-65

R-SERIES / AGENT NETWORK

Signed receipts for AI actions.

R-SERIES/ACTION → RECEIPT

Illustrative research scenes · 00 / 72 s

HOW PROOF WORKS · 30 s

An action becomes a receipt: one exact byte form, one hash, signed twice (Ed25519 + ML-DSA-65), chained to the one before. Change one byte and verification fails.

DCS LABS / RESEARCH
10,463passed · 0 failed · 78 skippedInternal test result — 20 October 2026 · R-Series release candidate · full suite · internal test environment
215 / 215Mutation testing: 215 of 215 evaluated mutants detected, in the same internal run.Internal test result — 20 October 2026
Internal AI-assisted review, a human cryptography review and a re-run by an engineer who did not write the code are separate steps.

Receipt stream above is illustrative. Counts are measured, with what they count named.

01 Defence & security
Hybrid · Ed25519 + ML-DSA-65 · ML-DSA-87 profile in development

Built for forces that operate where the network does not.

  • Signed orders. Checked by every platform before it acts.
  • Bounded autonomy under jamming. Every decision sealed on board, forwarded when the link returns.
  • Firmware checked before flash. A tampered image is refused, and the refusal is a receipt.
Illustrative research scene
02 Don’t trust us. Verify. Interactive demo

A receipt, signed and checked in your browser.

This page makes a fresh key pair, signs a sample receipt with both Ed25519 and ML-DSA-65, and verifies it here. The checks make no network request; site analytics run at page load. Then change one byte, or strip the post-quantum signature, and watch it fail.

Preparing keys…
  1. 1Parse the receipt
  2. 2Canonical bytes of the body
  3. 3SHA-256 digest matches
  4. 4Ed25519 signature
  5. 5ML-DSA-65 signature
  6. 6Both signatures present and valid (hybrid)

A full walk-through of every check is on the R-Series verify page; it issues its own sample receipt, which you can edit field by field. This interactive demo verifies signatures using keys generated in the current browser session. For issuer-aware verification and trust-policy checks, explore the detailed demo. Neither page is a verifier for production receipts.

03 One proof layer, five worlds

The same receipt, wherever machines act.

Five worlds01 / 06
01 · AI AGENTS · R-SERIES

An agent approves an invoice. The approval is a signed receipt.

Each action captured through a supported integration becomes a receipt: the intent, the policy that applied, a hash of the result, two signatures. Anyone can check it offline, without asking us.

Enter R-Series →

02 · DEFENCE

An order crosses a jammed link. The drone still proves what it did.

Signed orders, bounded autonomy when the link is denied, firmware checked before it is flashed, and an after-action record a coalition partner can verify.

Defence & security →

03 · DEEP SPACE · COSRYX

A rover acts twenty light-minutes from Earth, inside signed bounds.

The plan travels once, as signed intents. Every autonomous decision is receipted and sealed through months of blackout, then forwarded home intact.

COSRYX →

04 · SPACECRAFT · COSRYX · ORBIT

Commands checked on board. Logs verified on the ground.

Post-quantum trust for spacecraft that fly for twenty years. Flight software for a hosted run on an operating satellite is built and founder-approved after five dated review rounds across two model families (records held internally); the orbital test is planned.

COSRYX · ORBIT →

05 · PLANTS · IOT / OT

A controller older than the cloud moves to post-quantum keys.

A gateway can protect supported communication paths and record evidence for legacy devices. It does not upgrade the cryptography inside every device. Assessment determines whether a device can be adapted, isolated, replaced or decommissioned.

IoT / OT →

06 · ONE VERIFIER

Five worlds. One receipt format. Two verifiers, one verdict.

JavaScript and Go verifiers for the current receipt profile, with a shared conformance corpus; publication pending. One difference is a defect.

How we prove it →

04 Programmes

One trust engine under every programme.

R-Series is the engine. The other programmes put the same signed, chained receipts to work in space, in critical infrastructure and, next, in autonomous systems.

04b Post-quantum cryptographic capabilities
DIGITAL SIGNATURES

ML-DSA · SLH-DSA

ML-DSA (FIPS 204) signs every R-Series receipt alongside Ed25519. SLH-DSA (FIPS 205, based on SPHINCS+) is hash-based, for the longest-lived records.

KEY ESTABLISHMENT

ML-KEM

ML-KEM (FIPS 203) is a key-establishment mechanism; it never signs anything. X-Wing (ML-KEM-768 + X25519) is in evaluation and development for encrypted envelopes. Key establishment is separate from signature evidence.

The Ed25519 + ML-DSA-65 receipt profile is running on staging. Customer production availability is assessed separately. SLH-DSA checkpoints are in development. Every family and parameter set, on R-Series →

05 How we prove it

Nothing ships on our word alone.

Every release candidate goes through the same path. Internal AI-assisted review looks for defects. Every finding gets a failing test before it is fixed. An engineer who did not write the code re-runs the evidence. A human cryptography review rules on the cryptographic boundary. No external audit has taken place yet, and no certification is held.

Test first, then fix

Each finding is reproduced by a failing test before any code changes, then proven fixed by that test turning green.

Test the tests

We inject deliberate defects into our own code. A suite that does not catch them is not trusted, however green it looks.

Same verdict everywhere

JavaScript and Go verifiers for the current receipt profile, with a shared conformance corpus; publication pending. One difference is a defect.

06 Research areas

What the lab works on.

The research in depth →

PQ

Post-quantum cryptography

Hybrid signatures and key exchange, and the migration from classical keys without losing old evidence.

AI

Verifiable AI agents

Each action captured through a supported integration becomes a signed receipt that can be checked offline, by anyone.

SP

Space trust

Provable commands and mission evidence for spacecraft that fly for twenty years and lose contact every orbit.

OT

Critical infrastructure

Post-quantum migration for plants, grids and device fleets, with evidence at every step.

LH

Long-horizon evidence

We are developing preservation workflows that retain original signed bytes and add linked renewal evidence. Their assurance depends on the available history, timing evidence and cryptographic assumptions.

07 Status

Where each programme stands.

Built means built and tested. Simulated means it runs and is checked, but not yet in its real environment. We do not round up.

R-Series

Release candidate 4 is tagged and signed. The Ed25519 + ML-DSA-65 receipt profile is running on staging. Customer production availability is assessed separately. Internal AI-assisted review, a human cryptography review and a re-run by an engineer who did not write the code are separate steps. No external audit has taken place yet, and no certification is held.

Staging
COSRYX

Mission recorder, relay protocol and PQ-agility built and validated in simulation. Foundation gates complete; external audit, radiation and hardware gates pending. No flight qualification claimed.

In development
COSRYX · ORBIT

Ground trust layer, autonomy and quorum built and simulated. Flight software for a hosted run on an operating satellite built and founder-approved after five dated review rounds across two model families; records held internally. Orbital test planned.

In development
IoT / OT migration

We are developing an R-Series reference architecture for industrial systems and device fleets. Capabilities are qualified by device class, bench tests and deployment environment. Gateway hardware, firmware signing, update distribution and on-device rollback protection are planned.

In development · Planned
Post-quantum cryptography

Receipts Ed25519 + ML-DSA-65: Staging. ML-DSA-87 defence profile: In development. Checkpoints with SLH-DSA: In development. Archive signing: Planned. Firmware signing (LMS): Planned. ML-KEM-1024 defence integration: Planned. X-Wing envelopes: In development.

Staging · In development · Planned
Drone track

A trust layer for autonomous systems: secure command links, signed decisions and a verifiable black box. Future direction.

Planned
Built forGovernmentDefenceSpaceCritical infrastructureEnterprise AI

Want the full technical picture? This site shows what we build. Architecture, live demonstrations and detailed status are shared in a private technical briefing, under NDA. Write to hello@dcslabs.ai.

Request a technical briefing