Patent Pending · FIPS 204 + FIPS 206

One Signature.
Three Mathematical Families.
Zero Single Points of Failure.

H33-3-Key chains Ed25519, Dilithium-5, and FALCON-512 into a temporal binding that no single algorithm break can unravel. Three independent hardness assumptions. One unbreakable signature.

Get API Key Run Live Demo Read the Docs
~0µs
Triple Sign
~0µs
Triple Verify
~0B
Signature Size
0
Independent Families
The Problem

Every Post-Quantum Deployment Today
Bets on a Single Family

If that family breaks — through mathematical advance, side-channel, or supply-chain backdoor — everything signed with it is retroactively compromised. No migration path exists.

🔎
Mathematical Break
A new algorithm significantly reduces the cost of solving MLWE or NTRU SVP. All signatures using that family become forgeable overnight. Single-algorithm deployments: total compromise.
⚡
Implementation Vulnerability
Timing side-channels or fault injection exposing secret key material. Highly algorithm-specific — a Dilithium side-channel doesn't affect FALCON. Single algorithm: no fallback.
🔒
Algorithmic Backdoor
A deliberately weakened parameter set or hidden trapdoor introduced during standardization. Historical precedent exists (Dual EC DRBG). Single algorithm: undetectable compromise.
How It Works

The Temporal Binding Chain

Each outer layer signs everything beneath it. The result is a cryptographic dependency chain — breaking any single layer is never enough to forge the composite.

Layer 1 · Inner ---
Ed25519 signs the payload
Classical anchor. Signs the raw identity payload to produce σ₁ (64 bytes). This survives any lattice break — ECDLP is entirely independent mathematics.
RFC 8032 Curve25519 ECDLP hardness 64 B
composite₁ = payload ‖ σ₁
Layer 2 · Middle ---
Dilithium-5 signs payload ‖ σ₁
Module-LWE post-quantum signature. By committing to σ₁, Dilithium proves the classical signature existed at this exact moment. Breaking Dilithium alone still requires forging Ed25519.
FIPS 204 ML-DSA-87 MLWE + MSIS 4,627 B
composite₂ = payload ‖ σ₁ ‖ σ₂
Layer 3 · Outer ---
FALCON-512 signs payload ‖ σ₁ ‖ σ₂
NTRU lattice post-quantum signature. Commits to the entire prior chain. To forge this document, an adversary must break ECDLP, MLWE, and NTRU SVP simultaneously.
FIPS 206 FN-DSA-512 NTRU SVP ~666 B
Click "Sign Payload" to watch the temporal binding chain build in real time
Interactive Simulator

What If an Algorithm Breaks?

Click each algorithm to simulate a cryptographic break. Watch how the nested structure degrades gracefully — the signature remains unforgeable until all three independent families fall.

Ed25519 Secure
Elliptic Curve · ECDLP (Curve25519)
Dilithium-5 Secure
Module Lattice · MLWE + MSIS
FALCON-512 Secure
NTRU Lattice · NTRU SVP (SIS)
🛡️
Signature Unforgeable
All three algorithm families are intact. The nested hybrid signature provides maximum security across three independent mathematical hardness assumptions.
Ed25519
Dilithium-5
FALCON-512
Single-Algorithm vs H33-3-Key
Dilithium-only deployment Secure
FALCON-only deployment Secure
Ed25519-only deployment Secure
H33-3-Key nested Unforgeable
Live Demo

Run a Real Triple-Key Operation

This calls our production Graviton4 infrastructure. Real KeyGen, real Sign, real Verify. Not a simulation.

H33-3-Key Pipeline
POST /api/v1/demo/run-3key
1
Triple Key Generation
Ed25519 + Dilithium-5 (ML-DSA-87) + FALCON-512
---
2
Nested Triple Sign
Ed25519 → Dilithium-5 → FALCON-512 (temporal chain)
---
3
Nested Triple Verify
FALCON → Dilithium → Ed25519 (outer-in, fail-fast)
---
Total: ---
Performance

Benchmarked on Graviton4

All measurements on c8g.metal-48xl (96 cores, AWS Graviton4, ARM Neoverse V2). Criterion.rs v0.5, 100+ samples. February 2026.

~0
microseconds
Full triple sign
~0
microseconds
Full triple verify
~0
microseconds
Full cycle (sign + verify)
Sign Breakdown
Ed25519~50µs
Dilithium-5 (ML-DSA-87)~330µs
FALCON-512~70µs
Total~450µs
Verify Breakdown (Outer-In)
FALCON-512 (outermost first)~55µs
Dilithium-5~150µs
Ed25519~35µs
Total~240µs
Wire Format

Signature Anatomy: Version 0x03

Hover over the byte blocks to explore every field of the ~5,390-byte nested hybrid signature blob.

TripleHybridSignature · v0x03 ~5,390 bytes total
Hover to explore
Move your cursor over the byte blocks to see what each section of the signature contains.
Use Cases

Who Needs This

Triple nesting is for documents, tokens, and attestations that must remain valid for decades — where a single algorithm break would be catastrophic.

⛓️
Soulbound NFTs
Non-transferable identity tokens are permanent. If Dilithium breaks in 2035, a token minted today with only Dilithium is retroactively forgeable. Triple nesting survives any single-algorithm break throughout the token's entire lifetime.
Lifetime-critical
⚖️
Legal Documents
Contracts, wills, court filings, and title deeds are signed once and must remain valid for decades. Triple nesting provides the temporal binding that courts can audit even if one algorithm is later deprecated.
Decades-valid
📦
Software Supply Chain
Binary attestation and release signing. Software artifacts signed with a single PQ algorithm create a single point of failure for the entire distribution chain. Nested hybrid signing closes this gap.
Critical infrastructure
🌐
Cross-Border Compliance
Different jurisdictions standardize on different PQ families. A nested signature satisfying both MLWE (EU/NIST) and NTRU simultaneously eliminates re-signing for cross-border recognition.
Multi-jurisdiction

Ship Algorithmic Independence Today

One API call. Three mathematical families. Zero single points of failure. Free tier included.

Get Free API Key → API Documentation Technical Deep Dive
Free tier · 1,000 hybrid signs/month · No credit card · 108 Patent Claims Pending
Verify It Yourself