Verdict transparency log

MIZAN cannot rewrite its past.

Every verdict MIZAN issues, mint or preview, pass or refusal, revocation, reliance and bounty disposition, is one leaf of an append-only Merkle log. Heads are signed and stamped to Bitcoin. Anyone can fetch an inclusion proof, a consistency proof, or recompute the whole thing from the raw file.

A certificate authority is trusted because every certificate it issues lands in a public log. This is ours.

—Leaves

—Mints logged

—Refusals logged

—Bitcoin-confirmed through

§ 01The head

Signed head, read live.

—Merkle root (sha256 / RFC 6962)

—Head time (UTC)

—Ed25519 signature, prefix

—Latest anchor

Key: studio.mizan.market/.well-known/mizan-keys.json · head: /api/log/head · anchors: /api/log/anchors

§ 02Latest leaves

The last fifty verdicts, as issued.

#	When (UTC)	Kind	Subject	Verdict	Proof

Identities are hashed. Previews and refusals are logged like passes. The full log: /api/log/entries.

§ 03Audit it

Three checks, no trust in MIZAN at any step.

curl -s https://studio.mizan.market/api/log/head # signed head curl -s https://studio.mizan.market/api/log/proof/21 # inclusion path for leaf 21 curl -s "https://studio.mizan.market/api/log/consistency?old=100&new=133" # old head ⊂ new head curl -s https://studio.mizan.market/api/log/audit # server recomputes every leaf from the raw file # leaf_hash = sha256(0x00 || canonical(leaf)); node = sha256(0x01 || left || right); fold the path; compare to head.root; # verify head.signature with the published Ed25519 key; verify the .ots against Bitcoin with any OpenTimestamps client.

An agent gets the same with the MCP tools log_head and log_proof. A missing or rewritten leaf fails the consistency proof; that failure is itself a verdict about MIZAN.