FinCon

Verify a proof

Stateless, public, and it trusts nothing. Hand it a proof from an audit export and records you ingested yourself from the source files, and it re-derives the arithmetic under a policy you name.

How it works

  1. Fetch the source files named in the export and confirm each sha256.
  2. Ingest them with the published adapter spec in data/adapters/.
  3. POST /v1/verify with the proof, your records, and a loop name.
  4. Confirm the decision log's chain with GET /v1/runs/{id}/chain.

None of this needs our database, our network or our goodwill. A step that disagrees is a finding about us.

Published loops

The verdict names the policy that judged it and whether you supplied it. A lenient policy you bring along yields a verdict about your constraints, stamped caller-supplied so it cannot be quoted back as ours.

Open the API reference Sign in