Updated 2026-10-23: the revocation bounds as deployed values (185 and 245 seconds); 2026-10-19: the operator’s name.
Reusable KYC means a qualified organisation verifies a person once. The person then proves facts from that verification anywhere and as many times as needed. They do not repeat the process or re-share documents. Good reusable KYC removes the most expensive and leaky step in digital onboarding. Bad reusable KYC just moves copies of your passport around faster. The difference is what gets reused.
One-shot KYC re-runs the same check at every relying party
Today, each relying party repeats KYC. Every exchange, bank, marketplace and fintech runs its own onboarding. The same person uploads the same documents, passes the same liveness check and waits through the same review again. Several costs compound:
- Verification cost. Each relying party pays for a full check that someone else already performed, and users abandon funnels while they wait.
- PII sprawl. Every repetition creates another database holding identity documents. Each database is another breach target, another retention obligation and another copy the user cannot recall.
- Stale assurance. A check done at signup says little a year later. One-shot KYC has no live revocation, so the relying party rarely learns when the verification stops being true.
Reusable KYC reuses the verification and leaves the data where it is
The naive version of “reusable KYC” forwards the file. One provider verifies you and transmits your identity record to each new relying party. That approach reuses the data and multiplies every problem above, because now your file travels.
The strong version reuses the verification and leaves the data with the issuer. The issuer examines the KYC evidence once, and the evidence stays put. The user carries away a cryptographic credential, which is a signed attestation they control with their own keys. When a relying party needs assurance, the user sends a proof of a claim, such as over 18, verified at a given assurance level, or credential still active. The user does not send attributes. Reusing the verification without disclosing the data makes reusable KYC compatible with data minimisation.
How the credential lifecycle works
one verification
no proof reveals the credential, the grade, or any other proof
verify once, prove many times · nothing to breach downstream
The lifecycle follows these steps:
- Issue. An accepted issuer verifies the person and issues an anonymous credential. The signature is blinded, and the holder binds it with a secret only they hold.
- Commit. The issuer publishes a compact status commitment, called a status root, on-chain on a heartbeat of roughly 30 seconds. The chain holds one root per issuer. It holds no per-user record and no credential list.
- Present. The holder answers a verifier’s challenge with a zero-knowledge presentation. The presentation proves exactly the requested predicates and proves that the credential is unrevoked against the current root. It expires in ten seconds and binds to that verifier’s exact origin, so nobody can replay or relay it.
- Verify. The verifier checks the proof against on-chain trust roots to confirm that the issuer is accepted, the root is fresh and the chain height is finalised. It stores a yes/no outcome and stores no identity data.
- Revoke. The issuer can revoke a credential by updating its root. At the reference values, verifiers refuse a revoked credential in under a minute (185 seconds on the single-node production chain). The holder can also self-revoke without the issuer’s cooperation. Verifiers everywhere then refuse the credential within about four minutes of the chain recording it (245 seconds on the single-node production chain). They do not refuse it before the next root carries the revocation. Revocation follows the schedule of the status roots. It does not wait on a support ticket.
What each party gains
Holders stop re-uploading their documents. They keep the keys, choose what to prove to each verifier, and can walk away because self-revocation needs nobody’s permission. Presentations are unlinkable, so using the same credential everywhere does not build a cross-site profile of the holder.
Verifiers get cheaper and fresher assurance. They run no document pipeline and defend no PII vault. Their revocation check is minutes old at most, whereas one-shot checks can be months old. The proof arrives pre-bound to their origin and policy, which prevents whole classes of replay and phishing fraud.
Issuers turn a cost centre into a product. One verification can serve every relying party, metered by issuance instead of repeated labour. In MintID’s model, issuers remain accountable for quality. Governance admits them on chain by proposal (and the compliance council will do so once it is seated). They post an on-chain bond and remain auditable through committed evidence without exposing raw data.
Liability, credential freshness, and regulatory reliance
“If the verifier never sees documents, who is liable?” The issuer vouches for the check. In MintID’s design, governance admits issuer organisations on chain by proposal (and the compliance council will do so once it is seated). Each issuer has a slashable on-chain bond, allowed assurance tiers and a public authorization state. The relying party relies on a named, bonded and supervised issuer, much as it relies today on a passport authority it never audits itself.
“Is a proof from last year still worth anything?” Status roots handle ongoing validity, while assurance grades and freshness bands separate the strength of a check from its age. MintID’s credentials carry a private assurance grade from A1 to A4. The issuer separately publishes how recently it checked the underlying evidence as a freshness band. It does not publish an exact date, and the zero-knowledge presentation does not prove this band. Each grade has a default validity: twelve months for A1 and A2, six months for A3, and three months for A4. After expiry, renewal issues a new credential that is publicly unlinkable to the old one.
“Will regulators accept it?” Reliance frameworks for cryptographic KYC are still forming. A protocol can make the compliant path structurally easy with auditable issuer approval, committed evidence trails and fail-closed freshness. It can also avoid uncontrolled copies of personal data, which regulators consistently punish. MintID runs on the single-node production chain, which has been in production since 20 September 2026 and is operated by Conectia. Its audits are scheduled milestones, and the findings are published.
What the MintID chain stores and what stays off-chain
MintID is an identity protocol in production on a single-node chain, and it is designed to scale to a public proof-of-stake network. The chain carries issuer and verifier records, status roots, governance and audit commitments. It never stores KYC documents, biometrics, names, addresses, dates of birth, credential serial numbers, raw credential payloads or presentation logs. Live chain state scales with the number of issuers, verifiers and validators. It does not scale with the number of people or proofs, so a billion holders add no more chain state than a thousand.
Relying parties can start at the verifier programme, and KYC organisations can start at the issuer programme. The technology page walks through the full loop, including the ten-second presentation, the status-root heartbeat and the language boundary that keeps consensus deterministic.
Reusable KYC also supports AI agents. Once an accepted issuer verifies a human, that verification can back every AI agent the human deploys. The market calls this extension to the agent economy Know Your Agent (KYA).