Issuers
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, tiers and bonding.
Roadmap
Where we are, and what comes next
MintID is at the very beginning — deliberately. The specifications are written and frozen; the first lines of chain code are what comes now. This page shows the whole build sequence honestly, including the gate that matters most: no mainnet before independent security audits.
Build sequence
Seven phases, one launch gate
Each phase builds on the previous one and ends with something testable. Dates are deliberately absent: a security-first project ships when the audits pass, not when a calendar says so.
00
Done
Specifications frozen
The three normative specifications and the full requirement set are written and locked, so every line of code that follows has a fixed target. This is where the project stands today — design done, foundation next.
01
Done
Chain foundation
Stand up the sovereign Layer-1 itself: consensus, the native token, the base modules and chain state. The first thing that runs is a real blockchain, not a demo. Done: the chain builds, runs and finalizes deterministically.
02
We are here
Issuers, council, bonds & status
Add the machinery of trust: the accepted-issuer registry, the compliance council, slashable issuer bonds and the on-chain status-root heartbeat. Implemented and under hardening: consensus-enforced bond-gated activation, 30-second heartbeats with fail-closed freshness, and the hard-capped declining emission are merged and tested; external audit gates remain before any public network.
03
Upcoming
Verifiers & online verification
Register accepted verifiers and ship the verification core — the part that checks a 10-second proof against the chain’s latest finalized state.
04
Upcoming
Anonymous credentials
Deliver the cryptographic heart: the anonymous-credential scheme and issuance core, so issuers can mint credentials that holders prove in zero knowledge.
05
Upcoming
Holder self-revocation
Implement the proof that lets anyone kill their own credential — after a lost phone, for instance — without revealing who they are or which credential it was.
06
Upcoming
Public adversarial testnet & audits
Invite the world to attack a public testnet, run independent application, cryptography, infrastructure and economic audits, and only then open mainnet. The launch gate is a precondition, not a milestone to skip.
In parallel
The agent layer rides the same sequence
Agent KYC is a single committed launch scope, not a separate ladder of promises: issuer-mediated agent credentials, self-custodied stablecoin escrow (collateral roadmap: USDC/EURC at launch → BTC → XMR, counsel-gated) and the consented disclosure rail. Its one piece of new cryptography — the proof-of-harm circuit for disputes — is launch-blocking and ships only after independent audit. Deferred ideas (a shared liability pool, an insurance backstop) stay explicitly out of scope until they earn their way in.
Adopted product tracks: zero-cost verifier packages (web widget, guest mobile flow, printed-QR mode), an MCP verification server for agent runtimes, a wallet-local identity statement reconcilable against on-chain disclosure receipts, and an x402 agent-payments integration — an identity MVP first (an agent proves it is human-backed, with its assurance grade and delegated scope, to payment facilitators and sellers), with escrow-backed coverage following once the audit gates close.
Early is the best time to join
The network needs three kinds of collaborators, and each can start a conversation today — well before mainnet.
Verifiers
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.
Validators
Operators who run nodes and secure consensus for staking rewards. No identity work, no KYC files — just infrastructure. Early validators join the testnet first and help battle-test the network.
Follow the build from day one
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.