milestone
MintID stood up its first live network — a single-validator chain and the verifier service, deployed behind TLS from a reproducible bring-up package — and drove the first end-to-end test through it: proof-backed reads, live ten-second challenges, a fixed-slot decision record and a complete MCP session. Protocol-code defects found: zero. Alongside it, what the v2.0 re-freeze leaves fixed in the tokenomics — the hard cap, the ratified bands, the price-independent launch gate, the protocol cuts and the post-emission plan — now reads as closed policy, not promise.
transparency
Crypto projects publish code audits after the token is sold. MintID put itself through a full economic-viability audit — solvency of every actor, survivability of the project — before genesis, against its own frozen corpus, with the authorship on the cover: Conectia PRO, a related-party service provider to the protocol. The answer came within days: a full re-freeze of the corpus as v2.0. The verdict, stated whole: a qualified opinion, a demand thesis corroborated against independent sources, and five critical findings with five written answers. The report is downloadable, unedited.
announcement
The MintID client family grew a third member — not another language, a protocol. An MCP server exposes the three frozen verifier-service operations as tools any agent framework can call, with the same closed reason-code vocabulary: a rejection stays a decision, now readable by an agent.
standards
Between an anonymous payment and a doxxed buyer sits the slot only a zero-knowledge proof can fill: human-backed, in scope, unrevoked — and unrevealed. MintID has drafted the standards-track transport profile that fits it, with machine-readable schemas and a validation suite.
issuance
AI screeners are collapsing the cost of KYC — which is good for a credential rail. But a screener produces evidence, not verdicts. The MintID issuer plane now enforces that division by construction: enumerated checks with provenance, or a named rejection — and no field anywhere that could carry a provider-asserted grade.
agentic identity
Cloudflare’s Monetization Gateway makes agents pay per call over x402. Payment and fleet signatures are solved — the accountable human behind the long tail of agents is not. Why zero-knowledge KYA is the missing half of the agentic web.
architecture
The multi-language strategy behind the MintID SDKs is decided and locked into the spec: one audited verification core, embedded in Python — and TypeScript and PHP clients that carry no cryptography and no policy, built against a verification service you host yourself. Why thin clients are the strongest guarantee we could ship.
announcement
Development of the MintID verifier SDKs has started — TypeScript, PHP and Python — and we expect the first builds tested and working in a couple of weeks. Inside every binding, the same non-negotiables: nine acceptance checks, a ten-second proof lifetime and zero policy knobs.
comparison
ERC-8004 makes agents discoverable and their work verifiable — but its identity is a transferable NFT, its reputation is Sybil-prone, and recourse is out of scope. Where the standard stops, and how human-backed credentials fill the gap.
agent credentials
Agent authorisation today is a plaintext scope inside a token: all or nothing. A scope structured along five provable axes applies selective disclosure to authorisation itself — the merchant learns the limit, not the mandate.
economics
Per-check verification re-pays KYC at every counterparty. Amortisation — one human verification backing N agent credentials — changes the cost structure of trust. The five flows a sovereign identity rail earns from.
privacy
Identifying an agent once, paid and consented, is categorically different from holding a handle that tracks its human forever. How pay-per-disclosure, pseudonym churn and on-chain receipts make surveillance structurally impossible.
disputes
Most disputes want money back, not a name. How a dispute rail built on self-custodied escrow, anonymous arbitration and due process settles claims without unmasking anyone — and why that protects both sides.
agentic identity
Every identity system of the last twenty years assumed a human at the keyboard. AI agents break that assumption — and six concrete failures follow. Why the accountability-versus-privacy binary is the one to solve first.
reusable kyc
Reusable KYC explained: verify once with an approved issuer, then prove age, assurance grade or status anywhere in zero knowledge — with no PII on-chain.
comparison
How MintID and Concordium differ: identity architecture, anonymity revocation vs zero-knowledge presentations, compliance models and token design.
kya
What Know Your Agent (KYA) means, why AI agents need verified human backing, how KYA differs from KYC, and how zero-knowledge agent credentials work.