SHIPYARD / IDENTITY

Quiet Proof

Prove you are over 18, a resident, or a degree holder without showing a single document.

Lina wants to join a regional builder DAO that requires residency. She scans her ID locally, Quiet Proof generates a zk proof of country only, and the DAO verifies it onchain while never seeing her name or birthday.

Built for

The jobs it does

Own my identity and reputationProtect myself onchainProve what is real
Blueprint

How the vessel is built

Mission

Let people be verified without being exposed, so asking for a document scan becomes as outdated as asking for a fax.

The need

Communities, DAOs and apps often need one fact about a person (over 18, lives in a region, one human per seat) and collect whole document scans to get it. Those scans sit in shared drives and leak. People should be able to prove the fact without handing over the document.

What it will never do

  • Never upload your name, birthday, photo or document number.
  • Never accept a photo of a document as proof.
  • Never share more claims than you approved.
  • Never sell or link your proofs across gates.
Owner playbook

Pick your voyage

Quiet Proof lets someone prove they are over 18, a resident of a country, or a degree holder without showing a single document, using a zk passport SDK and an onchain verifier. If communities rely on a third party verifier, that vendor sees the traffic, sets the price and becomes the gatekeeper. Own it, and the verifier contract, the gated pages and the relationships with every DAO and app that needs private checks are yours.

Straight answers

Before you own it

Am I handling people's ID data?

The design keeps documents on the user's device; only a proof leaves it. Do not add any step that uploads documents to your servers. Still, privacy and identity rules vary by country, so get advice before selling to regulated businesses.

I can't code.

The SDK integration, claim picker, verifier contract and gated page come built. You choose which claims to offer and brand it. New claim types depend on what the underlying SDK supports.

Does it work with every ID?

No. Coverage depends on the zk passport SDK and the user's document and phone. Test with the countries your users actually come from and be upfront about gaps.

Who would pay for this?

DAOs with residency or age rules, regional builder programs, age gated communities and events. They need a check that does not create a pile of personal data they must protect.

Is it really mine?

Yes. The verifier deploys from your wallet on Base, Ethereum or Polygon, and the gated pages run on your domain.

Same berth

Nearby vessels

The whole yard →