zkTLS Proofs with Reclaim
I will integrate Reclaim zkTLS proofs to verify user data without exposing it
About this gig
Asking users to upload screenshots or bank statements is slow, easy to fake, and leaves you holding data you'd rather not store.
I integrate Reclaim Protocol, a zkTLS system, so users can prove a fact from any website they log in to (their bank, payroll, a social network, a marketplace or an exchange) and share only the claim. Your app receives a cryptographic proof that, for example, their income is above $2,000 or their account is older than a year. You verify it in your backend or on-chain, then unlock the action.
What you get:
- Reclaim providers set up for the data you need
- Custom claims such as thresholds and date ranges
- Proof verification in your backend
- On-chain verification on EVM chains or Starknet
- Gated actions: loans, airdrops, access passes, transactions
- Checks against reused or duplicate proofs
I write Cairo and Solidity contracts that act on verified conditions, like Bilateral Escrow and LandReg3 on Starknet.
Tell me what users need to prove and what it should unlock.
Use cases
Income without statements
A tenant or borrower proves monthly income is above a threshold straight from their bank or payroll portal.
Real people, not farms
Airdrop and reward claims require a proof of an aged social or ride-hailing account, so fresh wallets can't farm them.
Reputation that travels
A freelancer proves their rating and completed jobs on another platform without exporting their profile.
Exchange balance
A trader proves a balance or volume on a centralized exchange to unlock a tier, without an API key.
Verified purchases
A customer proves they bought from a store to claim a warranty or loyalty reward.
Credentials
Prove a degree, a certification or a professional membership from the issuer's portal.
What changes
Today
- You need to know a user earns enough, owns an account or has a following, and screenshots are easy to fake
- Collecting bank statements and IDs makes you a data breach waiting to happen
- Airdrops and rewards get farmed by bots with fresh wallets
- Manual verification takes days and turns good users away
After
- Users prove a fact (income above a threshold, account age, a completed order) straight from the source website
- Your app receives a cryptographic proof of the claim, not the underlying data
- Proofs verified in your backend, or on-chain on EVM chains or Starknet
- Actions gated on the proof: a loan offer, an airdrop claim, an access pass or a transaction
How it works
- 01User opens the verification link
- 02Logs in to the source site as usual
- 03zkTLS proof generated
- 04Proof verified on-chain or in your backend
- 05Action unlocked
Compare packages
| Package | Starter$350 | Business$900 | Scale$2,200 |
|---|---|---|---|
| What it is | One Reclaim provider in your web app with proof verification in your backend | Up to 3 providers, on-chain verification, custom claims and gated actions | Custom providers, multi-chain verification, sybil checks, dashboard and docs |
| Data providers (bank, social, payroll…) | 1 | Up to 3 | Up to 8 |
| Verification in your backend | âś“ | âś“ | âś“ |
| On-chain verification (EVM or Starknet) | – | ✓ | ✓ |
| Custom claims (thresholds, date ranges) | – | ✓ | ✓ |
| Actions gated on proofs | – | ✓ | ✓ |
| Custom provider for a site not yet covered | – | – | ✓ |
| Duplicate and sybil checks | – | – | ✓ |
| Verification dashboard | – | – | ✓ |
| Delivery | 5 days | 10 days | 20 days |
| Revisions | 2 | 3 | 4 |
Add-ons
- Faster delivery+30% of the package
- Internal security review with written findings+$250
- Written documentation for your team+$50
- 30 days of support after delivery+$90
Built before
Who it's for
- Lending and credit apps
- Airdrops and community campaigns
- Marketplaces and gig platforms
- Rental platforms
- Web3 games and loyalty
What I'll need from you
- The fact users need to prove, and the website it lives on
- What the proof should unlock
- Target chain, or backend only
- Your app's stack and repository access
Questions, answered
What can users prove?
Facts they can see when logged in to a website over HTTPS: an income figure, an account's age, followers, a purchase, a degree, an exchange balance. The proof reveals only the claim you ask for, such as income above $2,000, not the statement itself.
Does it replace KYC?
It's strong evidence of a specific fact, and many products use it instead of screenshots and uploads. Regulated KYC still follows your licence's rules, and proofs can sit alongside it.
Which chains can verify proofs?
Reclaim publishes verifier contracts for Starknet and for EVM chains such as Base, Arbitrum and Optimism, among others. Backend verification works anywhere.
Who owns the code and accounts when we finish?
You do. Code goes to your repository, and services run on accounts in your name, so you are never locked to me. I hand over logins, keys and a short guide.
What if my project doesn't fit a package?
Send a message describing what you need. I reply with a custom offer priced to the actual scope, often after a short call.
The thinking behind it
Tools and tags
- Reclaim Protocol
- zkTLS
- TypeScript
- Solidity
- Cairo
- starknet.js
- Next.js
- #zktls
- #reclaimprotocol
- #zeroknowledge
- #proofofincome
- #web3identity
