Private Banking Infrastructure for Ethereum & L2s
Transaction privacy without sacrificing compliance. UTXO notes in privacy pool, private transfers, and auditor access. Testnet live on Avalanche Fuji & Base Sepolia. Mainnet coming soon.
Your Customers' Transactions Are Exposed
On public blockchains, every transaction is visible. Your customers' financial activity is an open book for competitors, hackers, and anyone with a block explorer.
- Customer balances and transaction history fully exposed on public blockchains
- Competitors can analyze your payment volumes, customer behavior, and business metrics
- Growing regulatory requirements for data protection (GDPR, CCPA, financial privacy laws)
- Customer trust erodes when their financial activity becomes public knowledge
- KYC-linked wallet addresses create permanent, traceable financial histories
What's Visible Today
Balance: $47,832.50
Sent $5,000 → 0x7a3...
Received $12,000 ← 0x9b1...
Owner: John Smith
Privacy That Works for Banks
NixProtocol provides encryption at the account level with regulatory-compliant disclosure mechanisms.
With NixProtocol
Balance: [ENCRYPTED]
myBalance = decrypt(ciphertext)
// → $47,832.50
auditor.decrypt(customer, timeRange)
Key Capabilities
- Encrypted Balances - Only account holders see their true balance
- Private Transfers - Transaction amounts hidden from public view
- Auditor Access - Regulators can verify when legally required
- Non-Custodial - Customers control their own keys
- Stablecoin Native - USDC, USDT, and any ERC-20 supported
Built on Proven Primitives
| Component | How Neobanks Use It |
|---|---|
| NixPool Contract | UTXO notes in privacy pool - process transactions with zero-knowledge proofs |
| Noir Circuits | Grumpkin, ECIES, Poseidon2 primitives for ZK proofs and cryptographic operations |
| Nix Wallet | NixAddress (Grumpkin public key) with Nix Account ID for privacy-preserving customer onboarding |
| Nix Relayer | Relayer-managed gas for smooth UX and selective compliance disclosure |
| NixPool SDK | High-level SDK for integrating private payments with enterprise access controls |
Real-World Scenarios
See how NixProtocol enables privacy across different banking operations.
Private Customer Balances
A neobank customer deposits $10,000 USDC. The balance is encrypted on-chain - only the customer can see their balance. Competitors, hackers, and the public see only encrypted ciphertext.
Benefit: Customer privacy, reduced targeting risk
Confidential Peer-to-Peer Transfers
Customer A sends $500 to Customer B. The transaction is verified on-chain, but the amount is hidden. Both customers see the correct balances in their apps.
Benefit: Transaction privacy, no amount leakage
Compliant Regulatory Reporting
A regulator requests transaction records for a specific customer. The neobank's compliance team uses their auditor key to decrypt only that customer's transactions and generates a report.
Benefit: Meet regulatory requirements without exposing all customers
Private Merchant Payments
A customer pays a merchant for goods. The payment is processed privately - the merchant receives funds but observers cannot link the customer to the purchase.
Benefit: Customer purchase privacy, merchant revenue privacy
Batch Payroll Processing
A business customer runs payroll for 100 employees through the neobank. Each employee receives their salary privately - coworkers cannot see each other's compensation.
Benefit: Salary confidentiality, reduced workplace friction
Cross-Border Transfers
A customer sends $5,000 to a family member abroad. The transfer is compliant (auditor can verify if required) but private from public observers.
Benefit: International privacy, compliance-ready
Integration Flow
Security Model
Security audit in progress. Contact us to discuss enterprise pilot programs.
Ready to Add Privacy to Your Bank?
Private balances and transfers with auditor compliance, live on testnet. Talk to us about a pilot.