Hybrid Quantum Key Distribution Protocol (SHQKD)
Quantum Entropy Sourced (QES-256)
Entropy as a Service (EaaS)
OpenID Connect (OIDC)
STEADYWATCH™ is an Entropy as a Service (EaaS) platform built on IBM Quantum hardware. Every product layer — SHQKD, the QRNG API, and OIDC — produces QES-256 keys: 32-byte IBM Quantum hardware-derived keys with a verifiable job ID. One entropy standard. Every surface.
Quantum random number generation via IBM Quantum hardware. Every byte linked to a verifiable Job ID.
Try Live API →Biometric identity provider — RFC 8628 device flow, Face ID approval, quantum-seeded JWT tokens. Direct Cisco DUO replacement.
View Demo →STEADYWATCH™ HANDHELD — FaceID-powered authentication. Approve OIDC logins, manage entropy keys, no passwords.
App Store →Our SHQKD protocol and research are validated on multiple quantum platforms, enabling cross-platform qubit aggregation and hardware-agnostic solutions.
Explore the 12-qubit GHZ entangled state. All 12 qubits are maximally entangled, creating a quantum state where measuring one qubit instantly determines the state of all others.
State: |GHZ₁₂⟩ = (|000000000000⟩ + |111111111111⟩) / √2
Hardware: Heron r2 v1.3.37 (156 qubits)
Job ID: d5gs5mkpe0pc73alki40
Drag to explore — click any card to open.
Our protocol differs from traditional E91: Instead of separate measurements, both parties use the same GHZ measurement (shared state architecture). This eliminates the need for basis comparison and achieves 0% error rate.
Eavesdropper Detection: We use parity comparison over classical channels. Random bits are sampled from raw keys, and parity is compared without revealing the actual key bits. Any eavesdropper measurement disturbs the GHZ state, introducing detectable errors.
Detection Probability: For our parameters (100 samples, 69% fidelity), detection probability is near-certain: P_detect ≥ 1 - exp(-620) ≈ 1.0
Key Distribution: All communication is over classical channels only. The quantum path is only for GHZ state generation (single execution), then both parties extract keys from the same measurement data.
QES-256 — Quantum Entropy Source: Every IBM Quantum job produces a QES-256 key — a 32-byte hardware-derived value with 2256 possible values, the same key size as AES-256. SHQKD, the QRNG API, and OIDC all emit QES-256 keys — one standard across the entire platform. Organizations already running AES-256 can source keys from real quantum hardware without changing their encryption stack. Classical PRNGs are deterministic and software-based; QES-256 keys trace back to a verifiable IBM Quantum job ID — auditable entropy provenance no classical system can provide.
Practical: Generation time is <0.01s (simulator) or 30–90s (hardware). Every key ships with a verifiable IBM Quantum job ID.
Yes. The protocol is backed by two independently validated security properties:
Information-theoretic security (GHZ layer): Any eavesdropper's knowledge of the key is bounded by hardware fidelity. At F = 0.69 on real IBM Quantum hardware, Eve learns at most 3.72 bits before privacy amplification — negligible after key distillation.
Eavesdropper detection: Interference with the GHZ state is detectable with near-certainty under our hardware parameters.
Computational security (Echo Resonance layer): Each session produces a QES-256 key — a 32-byte IBM Quantum hardware-derived key with 2256 possible values, equivalent to AES-256 key space.
git clone
https://github.com/Infin-8/STEADYWATCH-QUANTUM-DEMO.git
cd STEADYWATCH-QUANTUM-DEMO
pip install -r requirements.txt