Prove a specific fact
An organization issues a credential to a Zerant ID. The holder reviews the exact claim before a verifier receives a bounded result.
Explore the workspace →Prove trust.
Preserve privacy.
Zerant connects private credentials and consent to Zcash payment workflows. Organizations issue specific claims; people decide what to prove and use their own wallets for Zcash payments.
An application asks for a specific condition. The holder reviews that request. Zerant verifies the approved result against trusted issuers and policy, while unrelated evidence stays private.
In one sentence
Trust checks without the data dragnet.
Zerant sits between an issuer, a holder and a verifier so the verifier can learn the required result without receiving the holder's entire private evidence.
Instead ofUpload everything
Zerant enablesRequest one condition
Holder controlsWhat gets shared
Verifier receivesThe minimum approved result
How Zerant uses Zcash
One product, two privacy boundaries.
Zcash testnet handles payments. Zerant handles credentials, requests and consent without publishing a person's credential history on chain.
Move funds with a wallet
Zerant prepares a reviewed payment request. A compatible Zcash wallet authorizes the transaction; the wallet never becomes the person's Zerant ID.
Explore Zcash payments →Submission is not settlement
Prepared requests and wallet-reported transaction IDs persist in Zerant. Testnet confirmation remains pending until the server can verify the exact payment.
What Zerant solves
Trust should not require surveillance.
Zerant is designed for situations where an application needs confidence in a fact, not ownership of a person's whole profile.
Stop collecting entire identities
Applications often need one fact — eligibility, membership, role, completion or authorization — but end up collecting far more personal data than the decision requires.
Make trust portable without making people trackable
A holder can carry signed evidence between services while each verifier receives only the approved result for its own context.
Keep Zcash payment evidence narrow
A Zcash payment request should not require importing a wallet history. Zerant saves the specific request and submission while trustworthy testnet settlement verification is being built.
How Zerant works
Three roles. One narrow trust decision.
01
Issuer creates trusted evidence
An authorized issuer signs a claim and can later revoke it.
02
Holder reviews the request
The holder sees who is asking, why, and what result will leave the private vault.
03
Verifier gets a bounded result
Zerant checks trust, expiry, revocation, audience and replay before acceptance.
Who Zerant is for
One trust layer, many real-world decisions.
The same privacy-first trust model can serve people, organizations, communities and applications.
Individuals
Keep trusted credentials private and decide what each application is allowed to learn.
Freelancers & service providers
Prove work, eligibility or settlement conditions without exposing unrelated clients or wallet activity.
Businesses & marketplaces
Verify vendors, customers, fulfillment or payment conditions with less data collection.
Communities & grants
Check membership, contribution or program eligibility without building a universal reputation score.
Organizations & teams
Issue trusted roles and credentials, request narrow proofs, and use shared approvals for sensitive actions.
Developers
Add private trust checks to applications without turning identity or wallet activity into a public profile.
Privacy model
Collect less by design.
Privacy is a protocol boundary, not a marketing checkbox.
Minimum disclosure
Source credentials are not verifier fallbacks. The verifier asks for the condition it actually needs.
Explicit consent
Origin, purpose and requirements are bound to one holder decision.
Contextual reputation
Trust stays tied to a purpose and policy instead of becoming one universal score.
Zcash payment boundary
Only a named payment may be tracked. A wallet-reported transaction ID does not become a verified settlement claim.
One private trust layer
Trust can move with you without becoming a public profile.
Zerant connects organizations that issue trust, people who hold it, and applications that need to verify it — while keeping unnecessary personal information out of the exchange.
Issuer
Creates trusted credentials
Organizations attest to roles, contributions, memberships, achievements or eligibility.
↓ private credential
Holder
Owns the decision
Credentials stay private until the holder approves a specific use.
↓ approved proof
Verifier
Gets only what it needs
The application receives a narrow answer instead of the holder’s complete identity history.
What Zerant enables
A practical trust layer for people, communities and applications.
Receive private credentials
Keep trusted evidence from organizations without publishing it as a public profile.
View credentials →Issue trusted credentials
Organizations can send private credentials directly to a recipient’s Zerant ID.
Issuer workspace →Prove only what matters
Respond to verifier requests with a narrow approved result instead of sharing the whole credential.
Prepare Zcash payments
Review a payment request, approve it in a compatible wallet, and keep its submitted state available in Zerant. Settlement verification is still in progress.
Open Zcash payments →Zerant workspace
Your trust, on your terms.
Receive credentials, review requests and prove what matters without handing every application your full identity.