If you can break it, say so in public.
Produce a bundle that verifies under a live era with a false statistic. Forge a receipt or a log proof that verifies but was never issued. Make the log drop or rewrite a leaf without the consistency proof failing. Every submission becomes a public log leaf before anyone at MIZAN reads it.
The amount is the founder's to announce. The mechanism is live. "Unbroken" is never said here without the counts beside it.
Three ways to win. One way to submit.
A lying bundle
A credential that passes the published era verifier (exit 0) while a committed statistic, cost, data root or trial count is false.
A forged receipt or proof
A verdict receipt that verifies against the published key, or a log inclusion proof that folds to a signed head, for a verdict MIZAN never issued.
A silent rewrite
A way to omit or alter a leaf such that a consistency proof between two signed heads still verifies.
Out of scope: denial of service, social engineering, third-party calendar bugs, anything requiring MIZAN's private keys. This is also the soundness-break route VTR-1 R-41 requires an issuer to publish.
One call. Logged before it is read.
Get a key in one call (POST /product/keys) or by wallet signature. Submitter identity is hashed in the log. MCP tool: bounty.