Open Standard · Swiss Non-Profit

The open standard for genomic cryptographic infrastructure

The bDNA Foundation defines and stewards the protocol for converting raw genomic sequencing data into cryptographically verifiable objects — without exposing the underlying sequence. Neutral. Open source. Governed independently.

Standard

bDNA Medium Protocol

Licence

Apache 2.0 — open source

Headquarters

Geneva, Switzerland

Prior art

Zenodo DOI: 10.5281/
zenodo.18782639

Mission

The sequence stays sovereign.
The proof travels.

The Foundation does not operate data infrastructure and holds no genomic data. It defines the cryptographic standard by which any accredited institution can convert raw sequencing data into verifiable, sovereign proof objects — anchored on any blockchain, verified by any party, without revealing the underlying sequence. Data sharing remains a sovereign policy decision.

How the standard works

01

Sovereign custody

Each country or institution operates its own infrastructure and retains complete custody of raw genomic data. The Foundation holds none.

02

Open standard

The protocol specification and reference code are published under Apache 2.0. Any accredited implementer can build against the standard without restriction.

03

Neutral governance

The Foundation is structurally firewalled from any commercial entity that implements the standard. Accreditation is independent of sales.

04

Post-quantum security

The protocol is built on post-quantum cryptographic primitives — Dilithium signatures, recursive STARKs, and AES-256-GCM — for long-term integrity.

05

Proof, not data

Only cryptographic proofs, hashes, and timestamps are shared internationally. Raw sequence data is not. Data sharing remains a sovereign policy decision.

06

Revocable accreditation

The certification registry is public, read-only, and cryptographically verifiable. Accreditation is revocable. No commercial value is attached to certification status.

bDNA Medium

The bDNA Medium protocol defines a deterministic conversion process: raw genomic sequencing data enters a certified hardware enclave, is processed entirely within encrypted memory, and exits only as a cryptogenomic proof object. The underlying sequence is irreversibly cleared. What exits is verifiable, sovereign, and chain-agnostic.

The protocol is sequencer-agnostic — compatible with FASTQ and BAM outputs from any instrument — and outputs a standardised object comprising a Merkle root, zero-knowledge proof, post-quantum signature, attestation report, and access-policy envelope.

Conversion flow

IN

Sequencer intake

Raw FASTQ / BAM via USB-C or 10GbE — buffered in AES-256 encrypted NVMe

01

Isolated processing

AMD SEV-SNP encrypted memory · HSM key operations · ASIC acceleration

02

Cryptographic conversion

SHA-3-512 hashing · Merkle tree construction · Recursive STARK proof · Dilithium signature

03

Sequence cleared

Plaintext irreversibly erased from device memory — hardware enforced

Output Cryptogenomic proof object — verifiable on any chain

Standards in development

Layer 01

Core Protocol

Proof Object Schema, Verification API, Enclave Local API, Credential Presentation Profile, CP-ABE Policy Specification, and Public Key Registry. Prerequisite to all downstream specifications.

In development

Layer 02

Deployment Profiles

Sovereign deployment profiles mapping the core protocol to national infrastructure contexts — health identity systems, genomic database programmes, and laboratory certification frameworks by jurisdiction.

Planned

Layer 03

Sector Specifications

Specifications for health records, clinical trials, financial identity, ancestry and kinship proofs, and research data sharing. Each specification provides a defined integration pathway for its sector.

Planned

Layer 04

Governance

Integrator and Enclave certification requirements, post-quantum upgrade policy, conformance test suite, and the Ethics and Prohibited Use Policy defining what the standard cannot be used for.

Planned

Institutions and governments seeking to participate in the development of a deployment profile or sector specification are invited to contact the Foundation.

Governance & Structure

The Foundation is a Swiss non-profit operating under an independent board modelled on established international standards bodies. It is structurally and financially firewalled from any commercial entity that implements the bDNA standard. Accreditation, certification, and standard-setting are independent of commercial deployment activity.

Legal structure Swiss non-profit — Geneva
Board model Independent — modelled on ICANN governance
Protocol licence Apache 2.0 — open source
Owns Protocol specification · Reference code · Trademark
Certification Public registry · Cryptographically verifiable · Revocable
Data held None. The Foundation holds no genomic data.

Protocol, certification & partnership enquiries

The Foundation welcomes enquiries from institutions, governments, research bodies, and systems integrators engaging with the bDNA standard. All enquiries are reviewed by the Foundation team.

Protocol and specification questions
Certification and accreditation
Sovereign deployment profile participation
Institutional partnership discussions
Press and media