> ZadQ, the first product built on MintID: an x402 seller-verification pilot in which sellers prove that an accountable, verified party stands behind their payment address, without revealing who. How it works, how it runs today and how it is measured. [](https://zadq.app)Pilot on MintID # x402 seller verification ZadQ is the first product built on MintID. An x402 seller — an API, data or content endpoint paid per request in stablecoins — proves through ZadQ that an accountable, KYC-verified person or organisation stands behind its payment address, without revealing who. PILOTPRIVATE INSTALLATIONFIRST IMPLEMENTER How it works ## One seller, one attestation, a free signal 01 ### The seller is verified once An accepted issuer verifies the party behind the seller and issues a conventional, issuer-signed attestation for its payment address and resource. This first version makes no zero-knowledge claim: the seller’s endpoint is public, so unlinkability would add nothing there. 02 ### Buyers read the signal for free Explorers and buying agents check the attestation through MintID’s free verification path before they pay. 03 ### A verifier keeps it current A registered verifier re-checks each seller on a published cadence and publishes its own signed verdict: active, suspended, revoked or unknown. 04 ### Built from standard MintID parts The pilot is an ordinary issuer-and-verifier pairing. It needs no change to the protocol. Who it is for ## Sellers with something at stake Sellers and agents with meaningful economic volume, and regulated business counterparties. ZadQ offers them privacy and compliance by design today, and funded recourse once the network reaches its financial-recourse stage — not cost savings. How it runs ## Three steps, one change at a time The distributed MintID network is still being built, so the pilot starts on a private installation and changes one thing at each step. 01 We are here ### Private installation A private, self-hosted installation of the MintID software, operated by the first implementer. MintID is operated here, never forked; the installation is not the MintID network and is never described as a launch. 02 Upcoming ### Zero-knowledge proofs on the same installation Once the audited proof core and a holder client exist, seller attestations move to the standard ten-second zero-knowledge presentation. Buyer-side agent credentials wait for the same audited core; there is no interim mode without zero knowledge. 03 Upcoming ### On the MintID network Then the topology changes: the pilot moves onto the distributed MintID network. Until then, nothing measured on the private installation counts toward the network’s traction criterion. Evidence ## What the pilot measures Success criteria are set in advance and measured. Four signals decide whether the pilot scales: 01 Sellers sign up for the paid service. 02 Attested sellers stay beyond 90 days. 03 Explorers show the verdict to buyers. 04 Verifiers ask for the signal. Pilot activity is reported as a related-party pilot and excluded from the network’s traction criterion. Who runs it ## Operated by the first implementer The pilot is operated by [Conectia PRO](https://conectia.pro), MintID’s first implementer and a related party, as the group’s own product line. Payment addresses held by a third party on a seller’s behalf are outside this first version. ZadQ’s own site is [zadq.app](https://zadq.app). ## Take part in the pilot ZadQ is described in full on zadq.app, and its place in the launch plan in Protocol Whitepaper v1.0. Sellers, explorers and verifiers who want to take part can get in touch. [Get in touch](/en/contact)[Visit zadq.app](https://zadq.app)[Read the whitepaper (PDF)](/docs/MintID-Whitepaper.v1.0.pdf) --- Source: https://mintid.net/en/x402-pilot · ZadQ — the x402 seller-verification pilot on MintID