Zkredit
Private Lending, Public Trust.
The problem Zkredit solves
The Problem It Solves
Privacy Crisis in DeFi Lending
Current decentralized lending protocols like Aave, Compound, and Solend suffer from a critical flaw: complete transparency of user positions. While blockchain transparency is valuable for verification, it creates serious problems for users:
1. Front-Running & MEV Exploitation
- Liquidation bots monitor every position 24/7
- Large traders' positions are visible to competitors
- Vulnerable positions get targeted before users can react
- MEV (Maximal Extractable Value) bots extract billions annually from predictable transactions
2. Privacy Violations
- Anyone can see your exact collateral amounts
- Your debt levels are public knowledge
- Competitors track institutional positions
- Personal financial strategies are exposed
- Whale watchers follow and copy every move
3. Institutional Barriers
- Hedge funds can't use DeFi without revealing strategies
- Businesses avoid on-chain lending due to competitive intelligence risks
- High-net-worth individuals fear exposure and targeting
- The $50B+ DeFi lending market is inaccessible to privacy-conscious institutions
Our Solution: Zkredit (Private Lending Powered by Arcium)
True confidential lending powered by Multi-Party Computation (MPC)
What Users Can Do:
For Individual Borrowers
- Deposit collateral privately - No one knows how much you've deposited
- Borrow without exposure - Your loan amounts remain confidential
- Avoid liquidation sniping - Bots can't target your specific position
- Maintain financial privacy - Your health factor is computed on encrypted data
For Institutional Users
- Execute strategies confidentially - Deploy capital without revealing positions
- Protect competitive advantage - Market makers can't front-run your moves
- Comply with privacy regulations - Meet institutional privacy requirements
- Access DeFi safely - Bridge traditional finance to DeFi with proper confidentiality
How It Makes Existing Tasks Safer
Traditional DeFi Lending:
❌ Public collateral: $1,000,000 USDC ❌ Public debt: $750,000 borrowed ❌ Public health factor: 1.33 (at risk!) ❌ Result: Liquidation bots waiting, front-runners watching
Arcium Private Lending:
✅ Encrypted collateral: ██████████ ✅ Encrypted debt: ████████ ✅ Private health factor: ████ (computed in MPC) ✅ Result: Only YOU see your position, protocol stays solvent
Key Benefits
1. Privacy Without Sacrificing Security
- All positions encrypted via Arcium's MPC network
- Protocol can still enforce liquidations when health factors drop
- Solvency is verifiable without revealing individual positions
- Zero-knowledge proofs of financial health
2. Protection From Predatory Behaviors
- Liquidation checks happen in encrypted state
- No more position sniping by bots
- No more front-running of large positions
- No more competitive intelligence leaks
3. Enables New Use Cases
- Corporate treasury management on-chain with confidentiality
- Hedge fund strategies without position exposure
- Privacy-preserving credit scores (prove creditworthiness without revealing amounts)
- Cross-border lending with regulatory compliance
4. Better User Experience
** Implemented (For the hackathon)**
- Real-time analytics - Track your performance without exposing data
yet to be implemented (for the purpose of scaling)
- AI-powered risk predictions - Get warned 3-7 days before liquidation risk
- Gamification & achievements - Earn XP and rewards for healthy positions
- Educational tools - Learn DeFi lending with privacy protection
Real-World Impact
Problem Today:
A whale wants to deposit $10M and borrow $7M on Aave:
- ❌ Everyone sees the position immediately
- ❌ Competitors adjust their strategies
- ❌ Liquidation bots monitor 24/7
- ❌ If market moves 10%, instant liquidation with no privacy
- ❌ Front-runners exploit predictable behavior
With Arcium Private Lending:
The same whale:
- ✅ Deposits $10M - amount encrypted
- ✅ Borrows $7M - debt private
- ✅ AI predicts risk 5 days ahead
- ✅ Receives private alert to add collateral
- ✅ Adjusts position without public panic
- ✅ Maintains confidential strategy
Market Opportunity
- Current DeFi Lending Market: $50+ billion TVL
- Institutional DeFi Adoption: Growing but limited by privacy concerns
- Problem: 83% of crypto users want privacy (Chainalysis 2024)
- Solution: First truly private lending protocol on Solana
Who Benefits:
- Privacy-conscious retail users - Protect personal financial data
- Professional traders - Execute strategies without exposure
- Institutions - Access DeFi with proper confidentiality controls
- Businesses - Manage on-chain treasury privately
- DAOs - Borrow for operations without revealing treasury positions
Challenges we ran into
Major Technical Hurdle: Arcium MXE Cluster Not Initialized on Devnet
The Problem
The biggest challenge I encountered was getting encrypted computations to run on Arcium's devnet. Our smart contract logic worked flawlessly for both withdraw and deposit instructions on devnet, but for the borrow instruction, We faced a major limitation.
The Error
Borrow transactions consistently failed at the queue_computation step with error 0x1772 (MxeKeysNotSet).
What we suspected
The devnet environment had no valid encryption key for the MPC network because:
- No Distributed Key Generation (DKG) ceremony had been completed
- The MXE public key was all zeros towards the end of the array
- Multiple devnet clusters exhibited the same issue (I tested offsets: 768109697, 3726127828, 1078779259)
Root Cause
Arcium's MPC network requires active operator nodes to run a DKG ceremony. Without that ceremony, the MXE (Multi-party Execution) public key is never generated - meaning no encrypted computation can run.
Debugging Process
To confirm the source of the failure, We:
- Inspected MXE account data - confirmed empty/zeroed public keys
- Reproduced the failure on devnet
- Tested multiple cluster offsets - all had inactive operator nodes

Program logged: "AnchorError thrown in programs/arcium/src/instructions/computation.rs:147. Error Code: MxeKeysNotSet. Error Number: 6002. Error Message: The MXE keys are not set, i.e. not all the nodes of the MXE cluster agreed on the MXE keys."
The screenshot above is a failed borrow transaction on the solana explorer with transaction signature: 4B9AjmUWng9xXsMWuqL5XVggzQqDT9AsNFJjsXBNru2cL2bN1YN7RKGE68nh2MYFLtghsNfsBPW3ctr3j5eewKtP
Tracks Applied (4)
General Bounty
Network School
Private DeFi & Trading
Arcium
Private Payments & Transactions
Osmosis
General Bounty
Project Tachyon

