DEV Community

H33.ai
H33.ai

Posted on • Originally published at h33.ai

Every Biometric Vendor Decrypts to Compare. Here Is Why That Is a Breach Waiting to Happen.

The Problem

Every biometric authentication system decrypts the template to compare. The biometric exists in plaintext in server memory during matching.

Biometrics are permanent. You cannot reset your fingerprint.

FHE Biometric Matching

H33 computes biometric matches on encrypted data using BFV FHE:

  1. Client encrypts biometric template
  2. Server computes FHE inner product on ciphertext
  3. Server returns encrypted yes/no
  4. Client decrypts locally

The server never sees the raw biometric. Not at rest, not in transit, not during computation.

The Numbers

  • 2,209,429 auth/sec
  • 42 microseconds per authentication
  • Three independent modalities
  • 17 spoofing types detected without decrypting
  • All post-quantum attested via H33-74

If someone breaches the database they get BFV ciphertexts. Useless.

Full deep dive ยท Biometrics page ยท H33 Platform

Patent pending. NIST FIPS 203/204/205. 20,000+ tests.

Top comments (0)