Getting started

Before any code: become a verifier (R13)

Installing an SDK does not make you a verifier. The SDK refuses to accept presentations for an unregistered identity — origin resolution runs against proven on-chain state on every single decision. Complete these first:

1. Register on-chain and pass verifier KYC — MsgRegisterVerifier; your verifier record must be ACTIVE.
2. Register every exact origin you present from — MsgRegisterVerifierOrigin, with periodic revalidation (MsgRenewVerifierOrigin). Origins are exact: no wildcards, one verifier per origin, so a lookalike domain can never impersonate you.
3. Register request-signing keys — MsgRotateVerifierKey; the key that signs your challenges must be registered for your origin.
4. Plan your infrastructure: chain access (any RPC node — answers are cryptographically verified, the node is never trusted — plus a trust-anchor header source), a crash-durable nonce store (the bundled SQLite store qualifies), a disciplined clock, and a place for the decision log.

Installation channels

Current channel (design partners): the SDK is consumed from the repository at a tag — packaging as platform wheels is decided and implemented (the Rust proof engine compiles into the wheel at a pinned version; pip install needs no Rust toolchain), and the first tagged release follows the release checklist. Talk to us to integrate as a design partner today.

Target channel: pip install mintid-verifier-sdk from a package index (private first). One wheel per platform (Linux/macOS, x86_64/arm64), CPython ≥ 3.12. The TypeScript client ships as @mintid/verifier-client (Node ≥ 20, ESM + types).

Every artifact records its pins — engine version, chain store-layout vector identity, SPEC revision, conformance-suite version — readable at runtime.

Current status — read before integrating