Typed secret operations
ML-DSA-65 key generation and signing use liboqs. Secret keys are move-only and zeroized on destruction.
Core · Cryptography
A deliberate security boundary.
Acceleration where it belongs.
Secret-key and single-message operations stay on CPU. Vulkan accelerates deferred batch work over public or non-secret data where parity can be verified precisely.
Security boundary
Secrets stay private. Public workloads go wide.
The backend is selected by data sensitivity and operation shape—not by a blanket promise that every cryptographic primitive belongs on GPU.
Deferred Vulkan hashing
SHAKE-128, SHAKE-256, Keccak-f[1600], and power-of-two Merkle roots have Vulkan routes with exact CPU parity tests.
Fail-closed inputs
Hashes, public keys, signatures, and Merkle proofs reject malformed lengths and encodings at the boundary.
Claims stay bounded
Implementation tests prove the stated contracts. They are not FIPS 140 validation or independent security certification.
Production surface
One API. Explicit backends.
CPU routes protect secret-bearing work. Vulkan routes are deferred, event-driven operations for public batch data with a CPU oracle beside them.
SHAKE-128 / SHAKE-256
CPU reference operations with official known-answer vectors and strict output contracts.
KMAC-256
Keyed hashing stays on the CPU boundary and is checked against official known-answer vectors.
Hash and Merkle proofs
CPU verification rejects malformed lengths, invalid encodings, and broken proof paths before use.
Batch SHAKE and Keccak-f[1600]
Deferred Vulkan work over public batches, verified against the CPU reference and direct KAT tests.
Power-of-two Merkle root
A deferred Vulkan route for public data with exact CPU parity across the supported tree contract.
ML-DSA-65
Typed CPU key generation, signing, and verification through liboqs with negative-path coverage.