Frequently asked questions

MintID is an identity protocol for privacy-preserving, KYC-backed credentials, for people and for the AI agents they deploy. An accepted issuer verifies a person once; the person then proves what a counterparty needs, in zero knowledge, without revealing who they are. MintID is in production on the single-node production chain, operated by the CONECTIA group since 20 September 2026, and designed to scale to a public, permissionless proof-of-stake network.

No. No KYC data, personal data, credential, credential serial, presentation or per-person record is ever written to the chain. It holds only issuer and verifier records, status roots, self-revocation nullifiers, staking, governance and evidence commitments — and it grows with institutions, never with people.

Under the protocol, only accepted issuers can issue: KYC organisations admitted on chain by governance proposal, today voted by the chain’s single validator and, once the compliance council is seated, by the council. Each one locks a slashable bond before it can operate, posted in the native token on a public network, and can be suspended or slashed through an evidence-backed decision. Today the single-node production chain carries the first accepted issuer, operated by the CONECTIA group as a disclosed related party on the same terms as any other.

The holder proves a claim — for example “grade ≥ A3”, “over 18” or “credential active” — against public chain state without revealing the underlying attributes or which credential was used. The verifier learns the policy result and which accepted issuer stands behind it.

A private four-level measure of how strong the identification was, anchored on eIDAS and squared with ISO/IEC 29115: A1 corresponds to eIDAS low (LoA2), A2 to substantial with biometric liveness (LoA3), A3 adds enhanced due diligence — sanctions, PEP and adverse-media screening — and A4 corresponds to eIDAS high (LoA4), such as qualified identity proofing or the EU Digital Identity Wallet. A verifier receives only a threshold proof such as “grade ≥ A3” — never the grade itself.

There is exactly one recovery path: fresh KYC re-verification, which issues a brand-new credential with new secrets, publicly unlinkable to the old one. There is no social recovery and no custodial back door.

Yes. Holder self-revocation works without the issuer and reveals neither your identity nor the credential; every service refuses the revoked credential in under two minutes. It has run on the single-node production chain since 24 September 2026. Because it is the one proof the chain checks itself, it gets its own dedicated audit, a scheduled milestone whose findings are published.

Ten seconds, and only once. It is bound to one verifier, that verifier’s exact origin and request key, a single-use challenge, the requested policy and the chain state the verifier checked — so it cannot be replayed or reused anywhere else.

Agent KYC is how MintID provides verifiable human-backed agent identity, what the market calls know your agent: a person does KYC once, and the issuer mints privacy-preserving credentials for the agents they deploy, up to a per-person cap. Each agent proves it is backed by a KYC-verified, liable human at a required grade and within a delegated scope, without revealing which human, and without two agents of the same person being linkable.

No token exists today. Today MintID runs on the single-node production chain, operated by the CONECTIA group: a permissioned chain where security is key custody, not stake, and nothing can be bought; whatever unit of account that chain uses has no value and is never carried over to a public network. If MintID later scales to a public, permissionless network — a route it does not need today — that network’s design includes a native token with a hard cap of exactly 108,000,000 and a declining emission. The genesis allocation is ratified as bands — development 15%, public sale 20–25%, reward pool at least 60% — with priors of 15, 25 and 60%, which the independent economic simulation validates or argues against before any genesis. Whether a public network is launched, and how it is financed, is decided at the Gate-1 go/no-go: a public token offer is one route among several, and if chosen it would follow the full EU MiCA Title II process at a single fixed price. Nothing is for sale, and nothing here is an offer or investment advice.

No. They are free, unlimited and worthless by construction. They exist so the software can be exercised by the parties admitted to the environment; they never convert into any future token, and they may be deleted at any time through resets.

No. Grades measure strength, never age. Recency is a second axis, published by the issuer as a band — F4 under 30 days, F3 under 90, F2 under 180, F1 under a year — rather than a date, so records cannot be correlated by timestamp. The band is read on the classical seller rail; a presentation proves the grade threshold, not the band. Each grade has a default validity (12 months for A1 and A2, 6 for A3, 3 for A4); the credential expires exactly when the verification behind it does, with no grace period and no extension, and the way back is a new verification. Expiry is not revocation.

ZadQ is an x402 seller-verification service and the first product built on MintID. A seller paid per request proves that an accountable, KYC-verified party stands behind its payment address, without revealing who. It runs as a pilot on the single-node production chain, not yet the distributed network, and its first version runs on the classical seller rail, with conventional issuer-signed attestations; the zero-knowledge seller rail follows. ZadQ is the CONECTIA group’s own product, a disclosed related party, so nothing it records counts as independent adoption.

MintID is conceived and built by the CONECTIA group, a related party that also runs the first issuer, the first verifier and ZadQ — on the same terms as anyone else, and disclosed as such. Today MintID runs on the single-node production chain, in production since 20 September 2026 and operated by the CONECTIA group, with the code under an Apache-2.0 licence. The MintID Foundation, a Netherlands Stichting, is being incorporated by the founder and stays dormant until the public-offer route is chosen; on that route, its seat would make the AFM the competent authority under MiCA.

The chain with its registries, bonds and status roots; the verifier service; the issuer status plane and a first issuer service; the proof core, with credential issuance and selective-disclosure presentations; holder self-revocation, in production since 24 September 2026; a Python SDK, a transport-only TypeScript client, an MCP server and a holder library with Python, Go and TypeScript bindings; the public testnet with its KYC sandbox; and the single-node production chain, in production since 20 September 2026, which runs the ZadQ pilot. Bounded agents are minted today from a bundle catalogue the operator supplies. The consented commercial disclosure rail, contact-attribute identification included, is built and ships switched off and fail-closed; its activation waits for counsel.

In stages, each behind a published gate. The target for an identity-only mainnet is the second half of 2027, ahead of the EU Digital Identity Wallet acceptance date of 24 December 2027, but genesis waits for conditions rather than dates: a published traction criterion, the simulation and counsel work delivered, and, if the public-offer route is chosen, a raise above the $4.0 M net floor. If a minimum is not met, the plan re-stages.