Name: Quiet Proof
Brand: DEPLOYR
Price: 399 USD
Availability: PreOrder

Picture this

Who it is for

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.

Two ways to own it

What you get

Base$399

$100 deposit to reserve

Integration of an existing zk passport SDK, claim picker, onchain verifier contract, gated page or role unlock.

You choose: chain
You choose: name and logo
You choose: accent color
You choose: which claims to require

Customfrom $3,000

Built around you

Reshape it entirely: new features, your flows, your brand end to end, integrations you need. We scope it with you.

Everything in Base
Custom features and design
Priority build

Why it is new

What exists today, and what this does differently

Why own your own

A branded gate app on live zk passport SDKs; packaging, not a new primitive.

Closest things out there

Self (formerly OpenPassport) already proves age over a threshold without revealing documents, and projects like Anonibara build community gates with dashboards on it; zkPassport and zkPass are similar.

Checked with web searches in October 2026. A search is not proof that nothing similar exists, and the market moves fast, so we recheck before every build.

What it unlocks

The human in it

Lets you be verified without being exposed.

The Regatta Board

Races it can enter

grant · Ethereum Foundation · rolling

Ethereum Foundation ESP

rolling

Official page ↗

Privacy public goods angle; existing projects OK.

Their rule on existing code: Existing projects OK

grant · Polygon · rolling

Polygon Community Grants

seasonal; current season unknown

Official page ↗

Existing projects OK.

Their rule on existing code: Existing projects OK

What you own

The whole app, not a starter kit.

The complete Quiet Proof member app: people prove one fact from their passport chip (over 18, resident, one seat) without handing over the document, with a sharing diary, over-ask warnings and a paywall for running gates built in.

Base price · $399

The user app, complete

Every buyer gets the same finished app. Basic branding and copy changes come through a quick form.

Three step onboardingHome

Shown once: prove one fact, the passport stays shut, it pushes back.

Next action and who is askingHome

Open gate requests, expiring proofs and a running count of documents shared: zero.

Gate requests inboxProve

Each gate shows what it asks, what it learns and what stays hidden on the passport data page.

Chip scan with location guideProve

Asks the passport country first, then shows where the chip sits. Proof is built on the phone.

Over-ask warning and counter offerProve

When a gate asks for name or passport number, the app offers the smaller claim or declines.

No photo fallback, human fallbackProve

Photos of documents are refused by design. Unreadable chips go to a human queue, nothing uploaded.

Verifier receiptsProve

Chain, proof, claims, seat code, block and gas, with what is onchain and what is never sent.

Sharing diaryDiary

Every proof with expiry bar, re-prove with the same seat code, revoke, and declined requests.

Diary export and auto renewDiary

Signed export of every proof. Gated behind Organiser.

Gate builderMy gate

Pick claims, expiry and publish a gate contract with a Telegram or Discord role. Gated behind Organiser.

Plans and USDC checkoutMe

Tiers from the owner paywall, paid through the shared USDC on Base checkout with a receipt.

Privacy settingsMe

Fresh wallet per gate, Face ID lock, permissions and the product vision.

Open the full app demo

Add-on

Owner console

Your admin side: revenue, paywall editor, users, rules and the agent log.

Revenue and paywall editorRevenue

MRR, per check fees, tier names and prices, free proof limit, gated features, USDC payments and payment methods.

RulesRules

Allowed claims, verifier chain, default validity, over-ask warning, chip guide, fallback queue, gas sponsorship, reminders.

Scan helper logAgent

What failed, how it adapted, refusal reasons and running costs.

Roadmap requestsRoadmap

Priced v2 and v3 builds you can request from DEPLOYR.

Top-up

Growth and referrals

Referral and growth mechanics, switched on when you are ready to grow.

Community switch, referrals and over-ask nudgesGrowth

Cohorts, growth loops, gate to gate referral codes and a trigger to switch a community off passport scans.

The money path, built in

How it earns for you

Members prove for free. Organisers pay monthly to run a gate, organisations pay for several gates and a fallback queue, and apps that check occasionally pay per successful proof. All paid in USDC.

MemberFreeProve claims from your passport chip, sharing diary, up to 2 live proofs

Organiser$19 a monthRun one gate, 300 checks a month, role sync, diary export, unlimited proofs

Organisation$99 a monthSeveral gates, custom claims and expiry, human fallback queue, admin view of claim results

Per check apps pay $0.25 per successful proof by default, set by the owner. Gas sponsorship on an L2 costs cents per proof.

Prices are yours to set. Illustrative, not a promise of income.

Growth loops, built in

How it spreads

No scan word of mouth: members invite the next community
Over-ask nudge: members counter, gates switch to smaller claims
Public 'holds no documents' badge on gate pages
Share card after joining a gate
Gate to gate referral codes with a free month for both

Roadmap · build the next phase with us

Where it goes next

v1 included

The full member app

Chip scan with per document guide
Claim picker, verifier receipts, seat codes
Over-ask warning with counter offers
Sharing diary with renew and revoke
Paywall with USDC checkout, member gate builder

Included

Event check-in and verify API

Door check-in by QR
Verify API with metered per check billing
Discord and Telegram bots for many servers
Gate directory with a public no documents badge

Add-on from $500

Signed credentials beyond passports

Degrees and licences from issuers that sign digitally
National ID cards where chips are supported
Optional liveness step, off by default
Open claim schema for other gate apps

Add-on from $1,200

For investors and grant reviewers

The pitch, ready

Prove you are over 18, a resident or one person without showing a single document.

Problem: Communities, DAOs and apps need one fact about a person and collect whole passport scans to get it. Those scans sit in shared drives and leak.

Solution: A branded gate app on an existing zk passport SDK: the phone reads the chip, proves only the claims the gate needs, and the gate stores a seat code, never a document.

Why now: Passport chips are everywhere, zk passport SDKs such as Self make proofs practical on phones, and L2 verification costs cents.

Market: Builder guilds, DAOs, grant programs, events and age gated apps that today collect document scans they do not want to hold.

The ask: Fund a pilot with three regional communities to replace document uploads with gates and publish the results.

Funding is never guaranteed. Check each program's rules.

For hackathons and demo days

Your 2 minute demo

Home: meet Lina at her kitchen table in Amman and see three gates asking.
Prove: answer the Levant Builders Guild with country: JO and a seat code, using the chip guide.
Prove: open Petra Grants DAO, see the over-ask warning and send the counter offer.
Diary: show who learned what, re-prove and revoke.
My gate: hit the paywall, pay with USDC on Base, publish the Amman Hack Night gate.
Owner Revenue: edit a tier price and show the Plans sheet change live.
Owner Rules and Agent: switch off the chip guide and watch the scan success rate drop.
Owner Growth and Roadmap: switch a community, then request the v2 build.

Many hackathons require code written at the event. See the Regatta Boardfor each race's rule.

Make it entirely yours

Custom work covers new claim types your SDK supports, your own chain or verifier, branded gate pages, compliance reviews with your counsel, and integrations with your community tools. Custom features start from $3,000, scoped on a call.

Custom from $3,000

BLUEPRINT

Why it matters and how it really works

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 exists and what is new

This already exists as infrastructure: Self (formerly OpenPassport) proves age over a threshold and nationality from a passport chip without revealing the document, and projects like Anonibara build community gates with dashboards on it; zkPassport and zkPass offer similar proofs. Quiet Proof is packaging, not a new primitive: a branded gate app on an existing zk passport SDK with a claim picker, an onchain verifier, an over-asking warning and a sharing diary. Research verdict: exists, low novelty.

The data it runs on

On the user's phone only: the passport chip data (name, birth date, photo, document number), read over NFC and never uploaded. Onchain: the verifier contract, the proof result for the chosen claims, and a per-gate nullifier (seat code) that stops one document joining twice. Offchain for the gate owner: member wallet and claim results only.

1.The mission

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

2.Why people can't resist it

Nothing to steal Gate owners store no documents, so there is nothing to leak and less to worry about.

It pushes back When a gate asks for more than it needs, the app says so and offers the smaller claim. Users feel protected, not processed.

A sharing diary Every proof is listed: who learned what, and when it expires. People come back to check it and to renew.

3.How it works for real

Passport reading: An existing zk passport SDK (for example Self) reads the ICAO 9303 chip over NFC on the phone, checks the issuing country's signature, and builds the proof locally.

Claims: The gate owner picks claims: nationality or issuing country, age over a threshold, and one person per gate via a nullifier. Degrees are not in passports and need a separate signed credential.

Verifier contract: The SDK's onchain verifier on Base, Polygon or Ethereum (Self's own verifiers run on Celo today, so other chains may need a bridge or relayed result). A small gate contract records the member wallet, claim result, nullifier and expiry.

Gated access: On success the app grants a role: a Discord or Telegram role through a bot, a Guild style role, or a soulbound membership token that expires.

Wallets: Privy embedded wallets for members who do not have one, with gas sponsored by a paymaster.

Scan helper: Rule based guidance per document type (where the chip sits, how to hold the phone), plus a small model for plain language help. It never sees chip data.

4.Cost per use and pricing

Per verification: proof generation runs on the user's phone at no server cost. Onchain verification gas varies by verifier design and chain; on an L2 such as Base or Polygon it is typically cents, while Ethereum mainnet can cost several dollars. Example month for a guild verifying 300 members on Base with sponsored gas: roughly $5 to $20 gas, $20 hosting and bot, so about $25 to $40 a month. Check current SDK fees before launch.

Community $19 a month

One gate, up to 300 verifications a month, Discord or Telegram role sync, sponsored gas on an L2.

Organisation $99 a month

Several gates, custom claims and expiry, an admin dashboard of claim results (never documents), and a human fallback queue.

Per check $0.25 per verification

For apps that only need age or uniqueness checks now and then, billed per successful proof.

5.Growth loop

Every member who joins without uploading a scan tells the next community it is possible. The over-asking warning nudges other gates to switch. Share cards and a public badge on the gate page show it holds no documents.

6.Risks and guardrails

Not everyone can prove: Older passports without chips, unsupported countries and phones without NFC exclude people. Always keep a human fallback route.

Legal and age rules: Some uses (alcohol, gambling, financial services) have specific legal requirements that a zk claim may not meet. Do not market it as compliance; check local law per use.

Linkability: Reusing the same wallet across gates can link a person's activity. Use per-gate nullifiers and encourage separate wallets.

Stolen documents: A proof shows a valid document was present, not that its holder is the one scanning. Optional liveness or face match steps exist in some SDKs and add their own privacy trade-offs.

Dependency on the SDK: The app relies on a third party proving system and its verifiers and certificate lists. Track their updates and audits.

7.Build order

Integrate an existing zk passport SDK on mobile
Claim picker for gate owners: country, age, one per gate
Gate contract with nullifier and expiry on one L2
Discord and Telegram role sync
Over-asking warning and sharing diary
Scan helper with per document guidance and a human fallback queue

8.Where this is going

Now
A builder guild admits members by residency without storing a single document.
Next
Many communities and events gate on one fact, and members manage all their proofs in one diary.
Later
More credentials (degrees, licences) arrive as signed digital documents and become provable the same way.
The world it builds
Asking for a document scan becomes unusual, and people get verified without being exposed.

Costs and tools are estimates at the time of writing. General information only, not legal or financial advice.

OWNER PLAYBOOK

Own it, then chart your voyage

Nine routes from one vessel. Tap a port to open its chart.

Why own Quiet Proof

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.

What’s stopping you?

“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.

The million-dollar ladder

Organisations pay per verification or a monthly plan to gate roles, pages or contracts behind private proofs. Users verify free. This is a target, not a promise.

$100

$4,000

$30,000

$85,000

First 10 users

1 community verifying 100 members

$1 per verification

Regional programs

20 communities

$200 per month

App integrations

60 organisations