Verify us. Don’t trust us.
Everything a security reviewer looks for, on one page: what we never do, the keys that sign every answer and how they rotate, live uptime, our policies, and the record of our own mistakes. Every number here is read live by your browser.
What we never do.
- Hold the money.MIZAN answers whether a payment should move. The payment itself moves on the rail the parties already use.
- Let a fee depend on the verdict.An ALLOW and a REFUSE cost the same, so a verdict can never be bought.
- Delete or edit a wrong answer.Corrections are appended to the public ledger beside the original. Disputes and revocations are entries too.
- Hide a refusal.Refusals are published under the same name as passes: — of the — results on the registry were refused by our own gate.
Keys and signing.
Every answer from MIZAN’s API is signed by one Ed25519 key, and every verdict ends in a token signed by the same key. Pin it once; after that, checking an answer never needs MIZAN.
Published key set · live
| key id | alg | use |
|---|---|---|
| — | ||
The signing key for every answer and verdict. The full key set, including keys for other receipt formats: /.well-known/mizan-keys.json
Rotation · as published
—
How to pin it
- Fetch the key set once and store the Ed25519 key with id
—. - Store the successor hash
—. - Accept a new key only if its raw public key hashes to that successor.
The pre-commitment is itself on the public ledger: entry #148, 22 October 2026.
Status, measured.
—
State
Uptime · last 24 hours
Check latency
Incident history · last 24 hours, as our probe recorded it
- —
Source: /api/status · full history on the status page · incident and revocation policy
Security.
Verify offline
Any answer, on your machine.Paste a token or drop a credential; your browser or the published verifier does the math.
How to check us
What the check covers, and its limits.Published verifier binaries with checksums, and how to report a break.
Try it
Make a check and tamper with it.Watch a forged token get rejected in your own browser.
Privacy
What we keep, and what we never see.In plain words, checkable against the record.
Our own record, in public.
- Retractions →Before MIZAN counted anyone else, it counted its own research and retracted the results its counter refused, each with a documented root cause.
- Errata →Findings against the standard or the engine are published, never silently applied.
- Disputes →The subject or the requirer can contest any check. The outcome is written to the same ledger and never deleted.
- Changelog →Every release, dated, each one linked to its entry on the public ledger.
Policies.
- Signing key policy →What is signed, custody, rotation, compromise handling and the key history to pin.
- Incident and revocation policy →A revocation is never silent. An incident is never quiet.
- Continuity →A record that cannot be forked, a key that cannot vanish.
- Terms of reliance →What ALLOW means, and what it never means.
- Governance →How the standard changes, and what never does.
Prove the claim. Never reveal the method.