Pre-KYC.STELLAR TESTNET

PRE-KYC + ZKPASSPORT

Prove eligibility.
Keep details private.

Prove you meet the exchange requirements, such as an age threshold, with ZKPassport on your phone. Share proof of the conditions, without revealing document details the checks do not need. Stellar verifies the proof before the vault can complete your exchange.

Reuse your eligibility for the same wallet and policy while it remains valid. You approve each wallet payment separately.

Try a simulated TRY-to-token exchange on Stellar Testnet. Mock USDC and synthetic documents only. No real money or identity documents.

Loading the Testnet anchor...

What stays private, and how does the demo work?

ZKPassport generates the proof on your phone. Our adapted Soroban verifier checks the supported proof, and the anchor contract checks the document requirements and validity. The vault enforces eligibility alongside the order's payment conditions before releasing tokens.

Eligibility can serve multiple orders for the same wallet and policy, for up to one hour from the original proof, limited by policy expiry. Each order keeps its own exact amounts. A proof does not authorize a wallet payment.

Document details that the checks do not need stay private. Wallet addresses, token amounts and proof transactions are public. A rule accepting only one country can also reveal that country attribute.

Ask the team to admit your public wallet before starting. Use a supported synthetic document in ZKPassport developer mode. The withdrawal flow is a preview: public end-to-end validation is still pending.

Standard withdrawal payments go to the anchor's custodial intake account, then into gated escrow. The operator and payment observer are trusted during intake. Simulated bank receipts are not evidence of real fiat payment.

The experimental contracts are not independently audited. This is not production identity verification or current sanctions clearance. Ordinary transfers of this asset outside the vault are not universally proof-gated.