CHAINVERDICT — HELP TURN A REAL FAILURE INTO A REPRODUCIBLE CASE

The current catalogue is entirely synthetic. It is not a customer incident corpus,
benchmark, certification, credential verifier or evidence of market adoption.
Useful future cases explain a specific mistake and demonstrate its correction.

Start locally: inspect your capture with Inspector and run the free purchase kit.
You can adapt a synthetic case without sending a real capture. Prefer that option.

If you want to suggest a case, email contact@chainverdict.xyz with a short plain-text
description first. No account, payment, bounty or response-time commitment. This is
a voluntary contribution channel, not a new support contract or upload endpoint.

DO NOT SEND credentials, proof payloads/nonces, cookies, Authorization headers,
PAYMENT-SIGNATURE headers, signed payment payloads, wallet keys, request/response
bodies, private URLs, customer data, payer addresses or transaction hashes. Hashing
these values does not make them anonymous. Do not attach a raw HAR or server log.
Inspector reports are designed to omit values; inspect even those before sending.
Replace hosts with example.test and values with fictional ones locally. Keep only
what reproduces the rule failure. Do not send another party's information.

Suggested initial description (plain text, no raw capture):
  Case name:
  Protocol/version and tool version:
  Expected decision and reason:
  Actual decision and reason:
  Minimal synthetic reproduction steps:
  Proposed correction and regression expectation:
  Rights/publication permission: pending discussion, or explicitly described
  Attribution preference: anonymous, or an optional public name

Sending a report is not blanket permission to publish or change its licence.
We must confirm rights, sanitisation and explicit publication permission before a
real case can become a public fixture. Optional attribution is separate. A report
remains unconfirmed until reproduced and reviewed; a reporter assertion is not a
verified exploit or a seller-quality score. Confirmed fixes need before/after
reproductions and an identified method/version, with limitations preserved.

No external telemetry is collected by the offline tools. Do not send secrets to
this mailbox. There is no guarantee we can safely assess unsolicited private data.
