01
Privyields
Confidential Qualified Yield Market
A Zama-powered demo for private access control, encrypted allocation, encrypted reward accounting, and user-controlled disclosure.
- ZK proves qualification
- FHE protects allocation amounts
- cUSDC carries encrypted value
02
Problem
Qualified yield access leaks too much
Traditional qualified-investor workflows reveal identity, wealth signals, allocation sizes, and portfolio movement across many operational systems.
- Qualification and allocation are usually coupled
- Sensitive balances become operational data
- Users lose control over what is disclosed
03
Solution
Separate eligibility from private capital movement
Privyields keeps eligibility as a proof, then routes allocation and reward flows through confidential token handles.
- Asset threshold proof without publishing asset amount
- Encrypted deposit into selected yield products
- Encrypted rewards that only the user can decrypt
04
Architecture
Five on-chain building blocks
The demo composes a mock USDC rail, a confidential cUSDC wrapper, a qualification registry, a yield product market, and a confidential vault.
- MockUSDC for demo funding
- ConfidentialUSDC for encrypted balances
- ConfidentialYieldVault for private principal and reward state
05
User Flow
From proof to encrypted claim
A user proves qualification, wraps public demo USDC into cUSDC, encrypts a deposit amount, routes it to a product, decrypts their own reward, and claims cUSDC.
- Submit demo ZK commitment
- Encrypt deposit with Zama Relayer SDK
- Request and perform user decrypt for reward
06
Market
Ten yield product lanes
The app presents a multi-product marketplace: T-bills, tokenized real estate, staking, mining cashflow, private credit, basis strategies, DeFi credit, compute revenue, equities, and money markets.
- Product metadata is public
- User amount remains confidential
- APR updates can be published by the strategy operator
07
Demo Scope
Built for a live hackathon demo
The current deployment runs a production Next.js frontend behind Caddy, with demo contracts and local-server mode for fast iteration.
- Next production server on privyields.xyz
- Server-local Hardhat demo chain
- Sepolia path documented for live FHE flow
08
Next Steps
Move from demo to production architecture
The roadmap is to replace the demo registry with a real verifier, deploy to Sepolia or mainnet-compatible environments, and harden strategy custody and publishing permissions.
- Wire production ZK verifier
- Use live Zama Sepolia coprocessor contracts
- Add operational monitoring and permissioning