DCS Labs · Technology · How proof works

An action. A receipt. An independent check.

Every action an autonomous system takes leaves a receipt: the exact bytes of what happened, hashed, signed twice and chained to the receipt before it. Anyone holding the public keys can check it, offline, without asking us.

SignaturesEd25519 + ML-DSA-65
Canonical formRFC 8785
CheckOffline, by anyone
01 The film

Thirty seconds, start to finish.

Starts muted. The visualisation is illustrative; the steps are the real ones.

02 Four steps

What happens to every action.

01 · RECORD

The action is written down

Who acted, what they did, on which resource, when, and which receipt came before. Inputs and outputs are kept as hashes, not raw content. Names, resource identifiers, times and the model used stay readable, and can themselves be sensitive.

02 · CANONICALISE

One exact byte form

The record is rewritten in RFC 8785 canonical JSON, so two independent implementations produce the same bytes and the same SHA-256 digest.

03 · SIGN TWICE

Classical and post-quantum

The digest is signed with Ed25519 and with ML-DSA-65. Both must hold; a receipt with one signature missing is refused.

04 · CHAIN

Each receipt names its parent

Receipts link into a chain and roll up into a Merkle root. Change one byte anywhere and verification fails at that point.

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

Request a technical briefing