Learn Quorum-QaaS (4-region PBFT): from zero to expert, then sell it

No AI background needed. Five levels, each with something to actually do, at your own pace. Tick items as you go (your ticks stay in this browser).

Evidence, proof and selling tools for Quorum-QaaS (4-region PBFT)

Level 1 Beginner: understand it

Companies need to prove that a document, a log or a decision existed in a certain form at a certain time. Quorum-QaaS does that. You send a fingerprint of the file (a SHA-256 hash, so the file itself never leaves you). Four servers in four regions vote on it, and at least three must agree. You get back a receipt: their signed votes.

Anyone can check that receipt later on their own computer with a free checker that contains no CAIN code. If the file, the time or any vote is changed, the check fails.

Think of it like this: A notary public, times four. Instead of one notary who could be bribed or make an error, four independent notaries in four cities each stamp the same page, and a page counts as notarized only when three stamps match.

Read the full plain-English explanation: Quorum-QaaS (4-region PBFT), explained.

I read the explanation above.
I can say what it does in one sentence, without notes.

Level 2 User: see it work

Run it live: open the live demo. Before each result, guess what will happen. These are checks it must pass:

Published receipt verifies: Signed by a quorum of the pinned cluster.
Digest changed: The quorum signed this digest, not yours.
Cluster renamed (unsigned top-level field): cluster_id must equal the signed membership's; the 2026-11-03 lab found the verifier echoing it. Fixed and deployed 2026-11-03.
Request id swapped: The commit certificate names exactly one request.
Sequence moved: The certificate is for one slot in the log.
Operation digest differs from the receipt digest: The operation must notarize exactly the receipt's digest.

I ran the live demo.
I can explain what one of these checks shows.

Level 3 Verifier: prove it yourself

This is the skill that sets you apart: you don't have to believe us, and neither do your customers.

Install Python 3 if you don't have it (python.org/downloads).
Download the kit and unzip it.
Open a terminal in that folder. On Windows, click the folder's address bar, type cmd and press Enter. On a Mac, right-click the folder and choose New Terminal at Folder.
Run python3 verify.py (on Windows, python verify.py). It checks the seal without the internet.
Run python3 verify.py --live. It repeats every check from your own computer.
Try to cheat it: open transcript.json in a text editor, change one character, save, and run python3 verify.py again. It must now say FAIL. Unzip a fresh copy afterward.

I ran the kit's check on my own computer.
I changed a file and saw it fail.

Level 4 Expert: know the edges

An expert knows what a product does not do, and says it first. That is what makes a buyer trust you.

Read its limits page in full: what Quorum-QaaS (4-region PBFT) does not do.

You can say

Records are confirmed by four servers in four regions; at least three must agree.
Only a fingerprint is sent; the content stays with the client.
Receipts verify offline with a checker that has no CAIN code, against keys the client pins.
A changed record, vote or cluster name fails verification.

Never say

"Independent validators": all four are operated by us today, on one cloud provider.
"Certified timestamp" or "legally binding": the time is the gateway's word.
"Real-time": it takes seconds, not milliseconds. And never promise an SLA or uptime.

Read the questions real buyers send, with honest answers: answers to buyer questions.

Test yourself (click a question to see the answer)

Does the client send us their file?

No, only its SHA-256 fingerprint.

How many of the four servers must agree?

Three.

A prospect says "you run all four, so why trust it?" What is the honest answer?

They are right that the operator is one company; it protects against a faulty server, not against us. Independent operators are the planned fix.

Can you quote a price?

No published price. Sell it inside the Safety Evidence Pack or pass to the founder.

Is it right for a real-time payment check?

No: about 2.6 seconds per receipt.

In the live check "Digest changed", what answer must come back, and why?

"NOT_VERIFIED". The quorum signed this digest, not yours.

In the live check "Cluster renamed (unsigned top-level field)", what answer must come back, and why?

"NOT_VERIFIED". cluster_id must equal the signed membership's; the 2026-11-03 lab found the verifier echoing it. Fixed and deployed 2026-11-03.

In the live check "Request id swapped", what answer must come back, and why?

"NOT_VERIFIED". The commit certificate names exactly one request.

Does a passing kit prove the product is safe for every possible input?

No. It proves what the live product answered to the inputs listed in the kit, and lets anyone check that again.

Has an independent party audited or certified this product?

No. No third-party audit is complete and no certification is held. Say so if asked.

I got every quiz question right without looking.
I can name one thing it does not do.
I explained it to a friend, and they understood it.

Want a formal study path? The CAIN Academy has courses and exams. Finishing this page is your own practice; it is not a qualification or certification.

Level 5 Seller: put it in front of a customer

Copy, paste, send: the shortest route, no technical skill needed.
Who buys it and where to find them.
The sales conversation, then the offer and the close.
The rules: read these before your first message.
Selling tools with this product's evidence built in: pitch, emails, call script, objection answers, one-pager.

I read the rules.
I sent my first personal message.

About money: your share is agreed in writing with FIRME AI CORPORATION before your first message (email vincent@firmeai.com). Nothing here promises income. Most messages get no reply; that is normal.