H33

What is post-quantum cryptography?

Post-quantum cryptography (PQC) uses mathematical problems that quantum computers cannot solve efficiently — unlike RSA and ECC, which Shor's algorithm breaks. H33 implements NIST's finalized standards: ML-KEM (FIPS 203) for key encapsulation and ML-DSA (FIPS 204) for digital signatures. Every H33 API call is post-quantum end-to-end.

Is fully homomorphic encryption fast enough for production?

H33's BFV engine runs encrypted biometric matching at 35.25 microseconds per authentication — 2.21 million per second sustained on Graviton4. The optimization stack includes Montgomery NTT, Harvey lazy reduction, and NTT-domain fused inner products.

What are NIST FIPS 203 and 204 and do I need to comply?

FIPS 203 (ML-KEM/Kyber) and FIPS 204 (ML-DSA/Dilithium) are NIST's post-quantum cryptography standards, finalized August 2024. Federal agencies and their contractors must migrate. H33 is FIPS 203/204 compliant today.

Is reCAPTCHA GDPR compliant?

As of April 2, 2026, Google shifts reCAPTCHA from data controller to data processor — meaning you bear legal responsibility for all data it collects. H33-BotShield uses SHA-256 proof-of-work instead: no cookies, no fingerprinting, no personal data. GDPR compliant by architecture.

What is a CAPTCHA alternative that doesn't track users?

BotShield by H33 replaces CAPTCHA with invisible proof-of-work. The visitor's browser solves a SHA-256 challenge in 1-3 seconds — no images, no checkboxes, no behavioral tracking. Free for 2,500 challenges per month.

What is harvest now, decrypt later?

Adversaries are capturing encrypted data today to decrypt once quantum computers mature (estimated 2030-2035). If your authentication tokens or session keys use RSA or ECC, they're already at risk. H33's entire pipeline uses lattice-based cryptography that remains secure against quantum attacks.

How do I add post-quantum encryption to my app?

One API call. H33 handles FHE encryption, ZK-STARK proof generation, Dilithium signing, and biometric matching — all in 35.25 microseconds. Integrate via REST API, Python/Node/Rust/Go SDKs, or a single script tag for BotShield.

How does encrypted biometric matching work?

H33 performs the entire biometric match in encrypted space using BFV fully homomorphic encryption. Biometric data is encrypted on-device, transmitted encrypted, compared encrypted, and never exists in plaintext on any server. The result is a ZK-STARK proof revealing only match or no match.