Privacy Pools & Shielded Payments
I will add privacy pools and shielded balances to your crypto app or treasury
About this gig
On a public blockchain, anyone with your address can read your balance, your revenue and your payroll. For a business, that's a disclosure nobody agreed to.
I add privacy that's honest about its limits. On Starknet, Tongo wraps tokens such as USDC into encrypted balances using zero-knowledge proofs, with optional auditor keys. On Ethereum, Privacy Pools by 0xbow screens deposits through an association set, so users can show their funds aren't linked to flagged sources. Every build starts with a written threat model: what's hidden, from whom, and what isn't.
What you get:
- A threat model in plain language
- Shielded deposit, transfer and withdraw flows
- Shielded balances shown in your app
- Auditor or viewing keys for compliance
- Gasless flows through a paymaster
- Clean accounting exports, recorded before funds are shielded
In WeSelling, businesses can move resting USDC into a Tongo pool on Starknet. The product says plainly that this hides the balance from the public chain, not from the platform that holds the keys.
Tell me what you hold, who shouldn't see it, and who must.
Use cases
Private treasury
A business keeps its resting USDC shielded so revenue and reserves aren't public reading.
Private payroll
Staff and contractors get paid without every salary showing up on a block explorer.
Supplier payments
Pay suppliers without revealing to each one what you pay the others.
Compliant withdrawals
Withdraw from a Privacy Pool with a proof that funds aren't linked to flagged sources.
What changes
Today
- Anyone with your address can read your revenue, balances and payroll on a block explorer
- Competitors and suppliers see what you hold before every negotiation
- Mixers carry legal risk you can't take
- Privacy features get bolted on without anyone saying what they protect and what they don't
After
- Resting balances moved into a shielded pool, unreadable on public explorers
- Deposits screened through an association set, so funds stay provably clean
- Optional auditor keys for your accountant or regulator
- A written threat model: what's private, from whom, and what isn't
How it works
- 01Funds arrive in the clear
- 02Recorded in your books
- 03Moved into the shielded pool
- 04Amounts hidden on transfer
- 05Withdraw when needed
Compare packages
| Package | Starter$700 | Business$1,800 | Scale$4,500 |
|---|---|---|---|
| What it is | Threat model plus shielded deposit, transfer and withdraw for one token | Shielded balances in your app with auditor keys, gasless flows and accounting export | Tongo or Privacy Pools across products, screening rules, payouts and review |
| Written threat model | ✓ | ✓ | ✓ |
| Shielded deposit, transfer and withdraw | ✓ | ✓ | ✓ |
| Tokens | 1 | Up to 3 | Up to 6 |
| Shielded balances in your app | – | ✓ | ✓ |
| Auditor or viewing keys | – | ✓ | ✓ |
| Gasless flows (paymaster) | – | ✓ | ✓ |
| Accounting export | – | ✓ | ✓ |
| Privacy Pools (Ethereum) integration | – | – | ✓ |
| Association-set screening rules | – | – | ✓ |
| Internal security review | – | – | ✓ |
| Delivery | 8 days | 18 days | 30 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
- 90 days of support and small changes+$240
Built before
Who it's for
- Businesses holding stablecoins
- DAOs and treasuries
- Payroll and payout platforms
- Wallets
- DeFi protocols
What I'll need from you
- What you hold and on which chains
- Who must not see balances, and who must (accountant, regulator)
- How keys are held today (self-custody, embedded wallets, custodian)
- Your app or treasury setup
Questions, answered
Is this legal?
Privacy Pools were designed for compliance: deposits are screened through an association set, and users can prove their funds aren't linked to flagged sources. Tongo supports auditor keys. Rules differ by country, so confirm with your lawyer before launch.
Who can still see the balance?
Whoever holds the viewing key. If your platform holds users' keys, it can read their balances, and I make sure the product says so instead of overpromising.
Which chains?
Tongo runs on Starknet. Privacy Pools by 0xbow runs on Ethereum mainnet, with assets including ETH, USDC, USDT and DAI.
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
- Tongo
- Starknet
- Privacy Pools (0xbow)
- Cairo
- Solidity
- AVNU paymaster
- TypeScript
- #privacypools
- #shieldedpayments
- #tongo
- #cryptoprivacy
- #zkprivacy
