Quorum-QaaS

Byzantine consensus as a service. You send a SHA-256 digest. A live cluster of 4 validators in 4 US regions orders and commits it, and hands back a receipt of signed votes from at least 3 of them. Anyone can check that receipt offline, with no CAIN code and no trust in us.

#2 of the CAIN-42 Top 25 live cluster: … 19/19 live checks 17/17 forgeries rejected

validators: Atlanta, Los Angeles, Miami, San Jose

3 of 4

signatures needed (N=4, f=1): survives one faulty or lying node

2.6 s

to notarize one digest, measured 2026-11-02 (evidence, not a hot path)

CAIN imports in the offline verifier

Why it matters

CAIN-42 is a Byzantine trust fabric: no agent, node or wrapper vouches for itself. Quorum-QaaS is that idea as a product. A single server's signature proves only that one server signed. A quorum certificate proves that a majority of independent validators, each with its own key and in its own region, agreed on the same digest at the same position in one ordered log, and that one lying validator could not have produced it alone.

Very few small teams run real PBFT across regions with certificates a stranger can verify. That is what makes this one of the most distinctive things in CAIN-42.

What a receipt proves, and what it does not

Proves	Does not prove
A quorum of 3 of the 4 published validators committed exactly this digest at this sequence	What the digest is a hash of: you keep your data, we never see it
Each vote was signed by the member's own Ed25519 key from the published membership	The wall-clock time of the commit (`issued_at` is the gateway's statement, not a consensus fact)
The leader's proposal carried exactly this operation	Who you are beyond a pseudonymous client id
Changing any of it breaks verification	Anything at all if you skip the pin: see limits

On this site

How it works

From digest to quorum certificate.

Live demo

Verify a real receipt, then tamper with it, in your browser.

Evidence

19 live checks, 17 forgeries, hashes.

Verify it yourself

Offline, with a pin you fetch yourself.

Anatomy of a receipt

Every field of a real receipt.

The cluster

Members, keys, placement, health.

API

Routes, limits, errors.

Limits

Plainly stated.

Use cases

What people notarize, and why.

2026-11-02 upgrade

A real flaw found and fixed today.

History

Commits that shaped it.

FAQ

Questions engineers ask.

Found and fixed on 2026-11-02: the public verify route accepted a receipt from a cluster the forger invented when the caller sent no pin. Details. The offline verifier fix is live; the route fix is written and tested and goes live with the next gateway deploy.

FIRME AI CORPORATION · CAIN-42 is a Byzantine trust fabric. Numbers marked "our own check" were run by us, not by an independent party. Nothing on these pages is a certification.