QUBEX SENTINEL
Post-Quantum Verification API · Live & Early

Build the
Future

We're building in public — real cryptography, clearly labelled. A verification checkpoint institutional crypto can add to its own authorization flows.

How It Works

API Architecture Today

01. Caller Sends Signature

POST /verify with an ML-DSA-87 public key, message, and signature. Stateless REST endpoint. Holds no keys, stores nothing.

02. Backend Verifies

Qubex verifies the ML-DSA-87 signature and signs the result with its own attestation key — returning a portable receipt in milliseconds.

03. Anyone Verifies the Receipt

The attestation is checkable independently against the public key at /attestation-key. You don't have to trust us — you can verify.

Direction

Built: ML-DSA-87 core + verification API + signed, persistent attestations
In progress: security hardening
Next: independent security review
Then: institutional pilots Toward the standard

Direction, not a promise of dates. We move fast and iterate on real feedback. Timelines depend on audits and partners, so we don't pin them.

What's Real. What's In Development.

What Exists

• ML-DSA-87 signature verification (live, benchmarked)

• Stateless /verify API returning signed attestations

• Independent receipt verification (/verify-attestation, /attestation-key)

• Public, reproducible benchmark + open repo

• Persistent attestation identity (stable across restarts)

• 200/200 official NIST KAT vectors verified — 100/100 deterministic, 100/100 hedged mode

• Load tested: 2,100 requests, 0 failures across four concurrency levels

What's In Development

• ZK proof of correct verification (research)

• Independent security review

• Institutional integration path & pilots

Fast. Honest. Executable.

Join The Mission

We're building post-quantum verification infrastructure for institutional crypto. No hype. No fake metrics. Just execution toward becoming the standard.

Verify It Yourself View GitHub