Open a Discussion describing:
- Who the check is for (a person, an app, or an agent).
- What it proves (identity, ownership, permission, safety).
- Inputs the integrator supplies.
- Outcome the user sees (verified, processing, failed) and what it unlocks at a gate.
A reviewer confirms whether the check belongs in the public catalog or is better handled by combining existing checks. An accepted check ships once it is implemented in the Proofable service. It then appears in the verifier catalog, with its schema in verifiers/VERIFIERS.json.
Requirements
A public check must:
- Return deterministic outputs for identical inputs.
- Carry no PII in inputs or outputs.
- Document external API usage with rate limits and error handling.
- Note gas or performance considerations if it anchors on-chain.
Last modified on October 25, 2026