The Five-Link Proof Chain
How Enigma Genetics Works
Most health data systems verify accounts, devices, or credentials. Enigma Genetics is designed to verify that the authorized biological person is present and approving a specific data request.
In the examples below, “Nova” represents an Enigma user.
The Problem We Are Working On
Most health systems can store, encrypt, and audit access to your data. What they typically verify is that an account, device, or credential was used.
Enigma Genetics is designing a chain of cryptographic checks intended to bind data access approval to the authorized biological person, not just the device or credential.
The Five-Link Proof Chain
Every interaction with your data is designed to pass through all five links.
Enrollment
In DevelopmentNova is a real person
When you create your Enigma Biological ID (EBID), biometric authentication helps bind access approval to the authorized user rather than relying only on passwords or devices. Unifactor is designed to associate identity with biology in a way that is hard to share or steal.
Identity
ImplementedThis EBID is Nova
Each access request is designed to verify that the EBID corresponds to the authorized user. The system uses HMAC-SHA3-256 fingerprinting linked to a device key to support continuous identity verification.
Consent
In DevelopmentNova personally authorized this
At the moment of each data request, biometric re-authentication is required. The goal is to bind authorization to the present moment and the specific action, rather than a long-lived session.
Request
RoadmapQuery answered on Nova's confirmed data
Queries are designed to run inside secure hardware enclaves with SignaChain attestation. The intent is for only the answer to the approved question to leave the enclave, not the underlying record.
Record
In DevelopmentThis happened and is hard to alter
Each action is cryptographically signed (ML-DSA-65 planned) and timestamped per RFC 3161. The audit trail is designed to be tamper-evident and difficult to alter without detection.
Why This Matters
Most data infrastructure can prove that a credential was used. Binding approval to the authorized biological person, at the moment of access, is a different problem.
Enigma Genetics is building toward that capability.
Technical Building Blocks
Post-Quantum-Ready Encryption
In DevelopmentML-KEM-1024 and ML-DSA-87 are planned to protect long-horizon biological data. NIST FIPS 203/204/205 alignment.
Zero-Knowledge Architecture
In DevelopmentThe architecture is designed so Enigma Genetics does not possess the keys needed to decrypt user-controlled biological data.
Biometric Binding via Unifactor
In DevelopmentBiometric authentication is designed to bind access approval to the authorized user rather than relying only on devices or passwords.
Revocation
RoadmapPermissions are designed to be revocable, with the goal of timely propagation across the access layer.
Questions? Contact us