UIE SYSTEMSQUANTAUIEXCHANGEUIE ACADEMY
QUANTA Sign in Verify a pass

Quanta

Quanta

Quanta is UIE’s verification and authority product. It has two parts: a Q-Pass, a signed, short-lived, revocable statement of permission; and a Q-Gate, the free reader embedded at the relying party. The Gate is free forever, Apache-2.0, and never a precondition of access. It is distribution, not product.

If you rely on other people’s claims

Today you rely on paper: certificates, screenshots, phone calls to issuing bodies that may or may not answer. A certificate is a claim. A Q-Pass is a record: it states what a named principal authorised, the conditions attached, and — because it is short-lived and revocable — whether it still stands today, not whether it stood the day it was printed.

You check it with a Q-Gate. The check runs offline; the presenter carries the proof, and the verifier calls nobody. The Gate returns one of exactly five outcomes: verified · insufficient · invalid · absent · error. That is where Quanta stops. The placement is observing-class: the answer informs your decision, and your own policy decides what follows.

UIE attests the binding, never the underlying fact. A verified outcome means a named principal issued this record and it still stands. It never means the holder is good, safe or competent; that judgement was never ours to sell, and the fact that we refuse to sell it is what makes the record safe to rely on.

Q-Gate, for the people who will embed it

  • Licence: Apache-2.0. Verify it in the LICENCE file, not in this paragraph.
  • The reader is free forever. It is never a precondition of access, never a tier, never a trial.
  • Verification is offline and deterministic: same pass, same conditions, same answer. The verifier makes no network call. Nothing phones home.
  • A check returns one of exactly five outcomes: verified · insufficient · invalid · absent · error. The enumeration is exhaustive.
  • A Q-Pass is short-lived and revocable. Expiry and revocation are properties of the pass the presenter carries, readable offline.
  • Interoperability: W3C VC 2.0 compatibility; an AP2 mandate is consumable as one condition inside a Q-Pass. Schemas are versioned; changes are logged.
  • What the outcome asserts: that a named principal issued the pass and that it still stands, within its stated conditions. What it does not assert: any judgement about the holder.

The payment protocols verify identity and payment. A Q-Pass states authority: who may act, within what bounds, on whose mandate, and whether the mandate still stands.