The Protocol
A deterministic cryptographic process.
The bDNA protocol defines the technical requirements for capturing, processing, and attesting biological and physical data inside protected hardware environments. It specifies how raw data is transformed into a compact cryptographic proof object containing a machine-origin commitment, integrity proofs, hardware attestation, and a binding to an on-chain credential. Published under the Apache License 2.0.
Conversion Process
Four stages — binding across all implementations.
Every certified implementation executes this pipeline in sequence without exception.
The Proof Object
Self-contained. Chain-agnostic. No derivable data.
The proof object is the sole output of one protocol execution. Its composition varies by implementation — each reflecting the distinct cryptographic pipeline appropriate to its biological or physical input.
Each proof object carries a machine-origin commitment sealed to the device, the session, and the moment of capture. It may be anchored to any public or permissioned ledger and verified by any party holding the public key, independently of any centralised service and without access to the underlying data.
Security Model
Universal Composability — machine-origin commitment.
Three properties are formally required of every conformant implementation.
The proof object is sealed to its source data. It cannot be forged, transferred, or reproduced independently of the session and device that generated it.
It is generated only inside a certified implementation device at the point of data intake. Not in software. Not retroactively.
It carries a hardware-attested timestamp and is valid only for the session in which it was generated.