Copies kept today
Attackers can collect encrypted data now and retain it for future decryption. This is called harvest now, decrypt later.
Updating your systems later cannot protect copies already taken.
Products / Files
Demo / early accessQuantumVault
Protect files and verify records.
QuantumVault helps your organization keep sensitive information confidential and verify that critical records remain unchanged.
Quantum risk
Long-lived files
Patient records, research, and business information can remain sensitive for decades.
A sufficiently capable quantum computer could break widely used public-key encryption and digital signatures.
Source: NIST
Records trusted later
Future attacks on vulnerable signing keys could let someone forge a signature that a system accepts.
Long-term file protection must address both confidentiality and the signatures used to verify records.
QuantumVault
File protection
QuantumVault combines post-quantum key protection with file encryption and signed verification records. Your deployment defines who controls the keys and how authorized users recover files.
Confidentiality
Encrypt files locally before upload. Post-quantum key protection addresses future attacks on vulnerable public-key encryption.
Integrity
Compare the file with its signed verification record to detect changes.
Key control
Define key ownership and access rules for your organization.
Recovery
Retrieve and decrypt files with the required keys. Agree recovery procedures before deployment.
Demonstration
Encrypt a test file, verify its proof, and recover the original.
Use a non-sensitive file of 10 MB or less. The service receives the encrypted file, filename, and proof metadata. Keep this page open until recovery completes. Reset or leaving this page clears your local recovery keys; it does not delete stored files or proofs.
Demo keys stay in this tab. Reset, reload, or leaving this page loses the recovery keys. Dytallix does not hold these demo recovery keys. Reset does not delete stored files or proofs.
Encrypt
Select a fileEncrypt the file in your browser. Send the encrypted file to QuantumVault.
Demo only. Non-sensitive files of 10 MB or less.
Documents, text, and images. You can also drop a file here.
1 / 5
Demo proof signatures use legacy Dilithium format, not ML-DSA-87. The browser testnet wallet uses ML-DSA-87. These are different implementations.
Demo scope
File encryption uses ML-KEM-1024 and AES-GCM. Hashes use BLAKE3. Proof signatures retain the deployed demo’s Dilithium format. This signature format is not ML-DSA-87.
The demo uses the current Dytallix chain and QuantumVault service. Anchoring must return a confirmed blockchain transaction. If submission or confirmation is unavailable, the step fails and can be retried. It does not provide persistent key custody or an independent security audit. The lifecycle record describes this browser session.
Deployment requirements
The client, storage service, custody rules, and operating limits must be agreed for each deployment.
- You provide
- File requirements, data location, key owners, access roles, and retention rules.
- You decide
- Recovery authority and whether the workflow needs a shared proof reference.
- You verify
- Encryption and decryption, access controls, record verification, recovery, and deletion.
- You retain
- The configuration, payload hash, signer, verification status, and recovery procedure.
Limits
Encryption protects confidentiality. A recorded hash supports verification of a value, but does not prove that the source file is true. Endpoint compromise can expose data before encryption or after decryption.
Industry use cases
Government and defense
Keep sensitive records confidential and check their integrity when teams exchange or retrieve them.
- Policy and procurement archives
- Investigation records
- Technical documents
Healthcare
Protect patient information retained for years and check that retrieved records match the protected originals.
- Patient records
- Medical images
- Genomic data
Financial services
Protect confidential client records and give review teams evidence that retained files have not changed.
- Identity documents
- Transaction reports
- Risk models
Technology and software
Keep proprietary work confidential and verify archived files before teams reuse or distribute them.
- Source code archives
- Software release packages
- Product designs
Design and media
Protect unreleased work and verify the files delivered to clients or production teams.
- Design files
- Video and audio masters
- Client assets
Pharma and research
Keep unpublished research confidential and detect changes to files used in reviews and submissions.
- Drug formulations
- Laboratory and trial data
- Submission packages