The path is published before it is walked. The design has been reviewed for economic viability by Conectia PRO, a related-party service provider, and both that review and the whitepaper are published in full. Every change since traces back to a recorded decision; the specifications are available on request.
Today MintID runs on the single-node production chain, in production since 20 September 2026 and operated by the CONECTIA group. The MintID Foundation, a Netherlands Stichting, is being incorporated by the founder and stays dormant until the public-offer route is chosen. The independent simulation and the audit programme come next, as scheduled milestones with published findings; an offer under the full MiCA process follows only if the public route is chosen, and the network starts after that.
If a minimum is not reached, the plan re-stages rather than launching early. Stages and target windows follow Protocol Whitepaper v1.0 (4 October 2026).
The seven build phases below sit inside this stage. The single-node production chain, in production since 20 September 2026 and operated by the CONECTIA group, carries the first issuer, the first verifier and the ZadQ pilot while the distributed network is built; the public testnet with its KYC sandbox runs beside it, and the proof core is in production. The code is open source under Apache-2.0. The MintID Foundation is being incorporated by the founder and stays dormant until the public-offer route is chosen, and the financing route is decided at the Gate-1 go/no-go. The CONECTIA group funds the work as its own R&D and is never reimbursed.
Gate: the Gate-1 go/no-go on the financing route; on the public route, the simulation delivered, legal workstreams complete, trademark filed, and the Foundation’s board and statutory safeguards in place.
If the Gate-1 go/no-go chooses the public route, the full EU MiCA Title II path follows, in order: the crypto-asset white paper, notification to the AFM, the public offer, then admission to trading.
Gate: white paper cleared by counsel and notified, board and safeguards in effect before signature, bank and custodian onboarded, and the $4.0 M net raise floor met — otherwise the plan re-stages.
Genesis, with a set of 60 validators. Credentials for people and their agents, zero-knowledge presentations, status roots, free verification, the verifier registry and the compliance council go live, and ZadQ, today on the classical seller rail, moves onto the network. No escrow and no disputes yet.
Gate: the economic-security thresholds met in measurable units, genesis values frozen and the Genesis Allocation Statement published, with the audit programme reported as scheduled quality milestones whose findings are published — with genesis itself triggered by a published traction criterion sustained for two quarters.
Self-custodied stablecoin escrow, the dispute rail and its arbiter market. The consented commercial disclosure rail is already built and ships switched off and fail-closed; its activation waits for counsel.
Gate: a published demand criterion and unmasking governance reviewed by counsel, with the audits of the escrow contracts and the dispute cryptography as scheduled milestones whose findings are published.
Multiple issuers, a growing agent population, the active set grown toward 100 by governance, and the post-emission transition planned on a committed ladder.
Gate: continuous — transparency reporting, annual audits published with their findings, and monitored gate metrics.
Underneath the stages sit seven build phases. Each one ends in something that can be tested.
The core, agent-identity and disclosure specifications and the full requirement set were written and frozen before code was built against them — then revised and frozen again after the economic-viability review.
Stand up the sovereign Layer-1 itself: consensus and the base chain. The first thing that runs is a real blockchain, and it runs without any token.
The machinery of trust: the accepted-issuer registry, the compliance council’s on-chain machinery (the council itself is not yet seated), slashable issuer bonds and the 30-second status heartbeat — done on the chain, with the status plane and the issuer service running off-chain and issuing credentials in production.
The exact-origin verifier registry and the verification core: chain reads proven rather than trusted, single-use challenges and the full acceptance pipeline, behind a versioned service contract. Done.
The cryptographic heart: the anonymous-credential scheme and issuance, so that holders can prove claims in zero knowledge. Done: credential issuance, selective-disclosure presentations and the non-revocation path run in production, with the construction and the proof system frozen.
The proof that lets anyone withdraw their own credential — after a lost phone, for instance — without revealing who they are or which credential it was. In production on the single-node production chain since 24 September 2026; its audit a scheduled milestone whose findings are published.
Invite independent operators, issuers and verifiers to attack the public adversarial testnet, run the independent audits and publish their findings, and open mainnet when the launch gate is met. The gate is measurable and price-independent — priors of at least 20% of supply bonded by external parties, at least 25 independent operators and a Nakamoto coefficient of at least 7 — and insider accounts count toward none of it.
Two deployments exist today: the single-node production chain on which the ZadQ pilot runs, and the public testnet with its KYC sandbox. Neither is yet the distributed MintID network. 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.
If the Gate-1 go/no-go chooses the public route, the launch would be financed through the project’s own public tranche, under the EU MiCA Title II regime and in its prescribed order: the independent economic simulation sets the numbers, counsel drafts the crypto-asset white paper, the AFM — the Dutch regulator, competent through the Foundation’s seat — is notified, the public offer opens, and admission to trading follows.
Any such offer would have a single fixed price and a raise floor of $4.0 M net: below it, the project re-stages instead of launching under-funded. Proceeds would finance the launch under a published budget — audits, validator bootstrap, counsel, the Foundation, custody and runway — and every other offer term would appear only in the MiCA white paper.
How a native token would secure a public network, if MintID ever scales that way: token design
An external study that fixes the emission and allocation points inside the ratified bands, the launch-gate thresholds, bond sizing, the post-emission security budget and the traction criterion — with adverse, base and growth scenarios, and a model a third party can re-run.
The legal path for a possible offer and for the disclosure rails — including drafting the single crypto-asset white paper that MiCA Title II requires.
On the public route, notification to the AFM, the Dutch regulator, comes first, then the public offer, and admission to trading only after both. The European regime runs in full and in that order.
ZadQ, the first product built on MintID, is an x402 seller-verification service operated by the CONECTIA group, a disclosed related party. It runs today as a pilot on the single-node production chain, on the classical seller rail, and nothing it records counts as independent adoption.
MintID needs three kinds of collaborators, and each can start a conversation today, well before mainnet.
KYC organisations that verify people and vouch for them. You keep the customer relationship and the only private link to a person; the chain never sees your files. Early issuers help shape admission, the KYC policy behind the A1–A4 grades, and bonding.
Businesses that need to check a fact about a person or an AI agent — age, accreditation, a real human behind a bot — without holding their data. Early verifiers define the policies the rail must serve.
Operators who would run nodes and secure consensus on a public network, if that route is chosen. The role involves no identity work and no KYC files. Early validators join the public adversarial testnet first, when it opens, and help battle-test the network.
The whitepaper explains the destination; the specifications, available on request, define every step. If you want to issue, verify, validate — or just understand — we would like to hear from you.