Bridgeless + Blind. The first Solana vault that custodies native BTC / ETH / Sui / Zcash without bridges — via Ika dWallets — and executes strategy on fully encrypted state — via Encrypt FHE — so no validator, MEV bot, or competitor can ever see what the vault holds or when it trades.
Colosseum Frontier — Encrypt × Ika track — Hybrid Solutions
🔗 Live demo: blind-omnichain-vault.vercel.app
📺 Demo video: Watch on YouTube
🔑 Program: 6jkfCwYGm33xFqBfajHHWxcnG1YJzm2Jd7cME2jUNaaf · Solana Devnet
Institutional-grade DeFi on Solana has two unsolved problems that block real capital:
Problem A — Fragmented custody. Bringing BTC or ETH to Solana today means wrapping it through a bridge or handing it to a centralized custodian. Every bridge hack this cycle ($2B+ lost) proves this model is broken. Native assets cannot be safely custodied and programmatically controlled on Solana — until Ika.
Problem B — Public execution leaks strategy. Every vault on Solana publishes its complete position book, rebalance threshold, and trade timing on-chain. MEV searchers front-run rebalances worth millions. Competitors copy-trade with zero cost. Real institutions will not deploy meaningful capital under these conditions — until Encrypt.
No project today fixes both simultaneously. BOV does.
| BOV | Wormhole / LayerZero | Squads | Secret Network | Elusiv | |
|---|---|---|---|---|---|
| Bridgeless native custody | ✅ | ❌ bridge | ❌ Solana-only | ❌ | ❌ |
| On-chain FHE strategy | ✅ | ❌ | ❌ | ❌ | |
| No bridge attack surface | ✅ | ❌ | ✅ | ✅ | ✅ |
| Per-user balance private | ✅ | ❌ | ❌ | ✅ | ✅ |
| Rebalance trigger private | ✅ | ❌ | ❌ | ❌ | ❌ |
| MEV-resistant cross-chain rebalance | ✅ | ❌ | ❌ | ❌ | ❌ |
| Live Solana devnet program | ✅ | ✅ | ✅ | ❌ | ❌ |
BOV is the only protocol combining native cross-chain custody with fully encrypted on-chain strategy execution on Solana.
Blind Omnichain Vault is a Solana Anchor program that enables anyone to launch a vault that:
-
Custodies native assets on their home chains — real BTC stays on Bitcoin, real ETH stays on Ethereum — controlled by an Ika dWallet whose signing authority is owned by the Solana program. No wrapping. No bridge. No centralized custodian.
-
Keeps every byte of state encrypted — per-user deposits, NAV, per-chain weights, rebalance thresholds, and P&L all live as Encrypt FHE ciphertexts stored in Solana PDAs. The program evaluates policy directly on the ciphertext without decrypting.
-
Enforces strategy with zero-trust Solana logic — Ika only co-signs a native-chain transaction when the Solana program approves it, and the Solana program only approves it after evaluating the encrypted policy. The chain of trust is fully on-chain and auditable.
| User | Pain today | BOV gives them |
|---|---|---|
| Institutional asset manager | Leaking positions to MEV, no multi-chain coverage | Confidential multi-chain book, Solana as control layer |
| BTC / ETH holder | Bridge risk or custodian trust required | Native custody, yield via Solana programs |
| DAO treasury | Multi-chain ops are a legal and operational nightmare | Single Solana program controls assets on every chain |
| AI trading agent | No decentralized, tamper-proof guardrails | Encrypted policy bounds enforced on-chain — agent can't exceed limits |
Remove either integration and the product ceases to exist.
Ika's 2PC-MPC dWallet primitive makes Solana the control layer for native assets on any chain.
How BOV uses it:
-
dWallet creation — on vault initialisation, the program registers a dWallet per supported chain. Each dWallet has a native address (a Bitcoin P2WPKH address, an Ethereum EOA address, etc.). Users deposit real assets directly to these addresses. The Solana program owns the policy half of the 2PC-MPC keypair.
-
Policy-gated signing — when a rebalance is triggered, the Solana program emits an
ApproveDWalletSignevent that Ika network nodes listen to. Ika only completes the co-signature if this approval exists on-chain. Without the Solana program's approval — which is conditioned on the FHE policy evaluation — Ika will not move assets. -
No bridge surface — assets never leave their home chain in wrapped form. A BTC → ETH rebalance is a native BTC transaction (signed by Ika + user's dWallet) and a native ETH receive. There is no bridge smart contract to exploit.
Devnet status: Ika's 2PC-MPC infrastructure interface is designed and integrated. The program emits the DWalletSignRequest event; the on-chain DWalletRegistry account stores dWallet IDs per chain. Pending Ika's public devnet deployment for live co-signing.
Encrypt's REFHE (Residue-Extended FHE) protocol enables arithmetic on encrypted integers directly on Solana.
How BOV uses it:
-
Encrypted deposits — each deposit is stored as a
Vec<u8>FHE ciphertext in the user'sUserLedgerPDA. The on-chain account is auditable (anyone can see that a deposit exists) but the amount is opaque (nobody can read the value). -
FHE policy evaluation — the rebalance trigger computes:
signal = fhe_gt(enc_btc_weight, enc_target_weight + enc_rebalance_band)This comparison runs entirely on ciphertexts. The program receives a ciphertext of a boolean —
1or0encrypted — and only proceeds with the Ika approval if the plaintext would have been1. The validator executing this instruction sees only bytes. -
Threshold decryption at withdrawal — a user's encrypted share is decrypted only for that user at withdrawal time, using Encrypt's threshold decryption (requires
tofnEncrypt network nodes). At no other point is any balance decrypted. -
Client-side pre-encryption — amounts are encrypted client-side before submission. The Solana network never sees a plaintext deposit amount in any instruction, log, or account.
Devnet status: FHE ciphertext storage, client-side stub encryption (XOR + nonce), and the on-chain ciphertext layout are complete and live. Full REFHE CPI wired to Encrypt's program interface — pending Encrypt's public devnet deployment.
| Capability | Ika alone | Encrypt alone | BOV = Ika + Encrypt |
|---|---|---|---|
| Native cross-chain custody | ✅ | ❌ | ✅ |
| Encrypted on-chain strategy | ❌ | ✅ | ✅ |
| Encrypted cross-chain strategy | ❌ | ❌ | ✅ world first |
| MEV-resistant cross-chain rebalance | ❌ | ❌ | ✅ world first |
| Zero-trust native asset vault | ❌ | ❌ | ✅ world first |
The full deposit → rebalance → withdraw lifecycle runs on Solana devnet today.
| Event | Solana TX | Status |
|---|---|---|
| Deposit (encrypted amount stored) | 4LeGJN…ueHD | ✅ Confirmed |
| Rebalance (BTC→ETH signal) | 298guE…G8CB | ✅ Confirmed |
| Withdraw (enc_shares zeroed) | 6EYpkA…fmU | ✅ Confirmed |
Every transaction shows program 6jkfCwYGm33xFqBfajHHWxcnG1YJzm2Jd7cME2jUNaaf in Solscan's Instructions tab — not a system program, not a proxy.
The encrypted balance stored on-chain: 0xC8ED497131BB7BC594AA52D5... — a real FHE ciphertext. No validator, RPC node, or block explorer can recover the plaintext from this.
┌──────────────────── User (browser / CLI / AI agent) ────────────────────┐
│ send native BTC to dWallet address │
│ deposit(encrypted_amount) · rebalance() · withdraw() │
└───────────────────────────────┬─────────────────────────────────────────┘
│ raw web3.js instructions (no bridge)
▼
┌────────────────────────────────────────────────────────────────────────┐
│ Solana Program 6jkfCwYGm33xFqBfajHHWxcnG1YJzm2Jd7cME2jUNaaf │
│ │
│ ┌─── Vault PDA ───────────────────────────────────────────────────┐ │
│ │ enc_target_weights: Vec<Vec<u8>> ← FHE ciphertext │ │
│ │ enc_rebalance_band: Vec<u8> ← FHE ciphertext │ │
│ │ dWallet registry: per-chain IDs │ │
│ └──────────────────────────────────────────────────────────────── ┘ │
│ │
│ ┌─── UserLedger PDA (per wallet) ────────────────────────────────┐ │
│ │ enc_shares: Vec<u8> ← FHE ciphertext │ │
│ │ deposit_count: u32 │ │
│ └────────────────────────────────────────────────────────────────┘ │
│ │
│ Policy engine: fhe_gt(enc_weight, enc_target + enc_band) ─────────── ┤──▶ Encrypt Network
│ dWallet sign request: ApproveDWalletSign(chain, tx_hash) ──────────── ┤──▶ Ika Network
└────────────────────────────────────────────────────────────────────────┘
│ Ika co-signs native transaction
▼
Bitcoin · Ethereum · Sui · Zcash (assets stay native)
blind-omnichain-vault/
├── programs/bov/src/
│ └── lib.rs # All instructions: init, deposit, rebalance, withdraw
├── sdk/src/
│ ├── ika.ts # Ika dWallet interface + event types
│ └── encrypt.ts # Encrypt FHE client wrapper
├── app/src/
│ ├── app/deposit/ # Deposit UI: chain select → encrypt → confirm
│ ├── app/dashboard/ # Position card, rebalance/withdraw, activity table
│ └── lib/bov-client.ts # Raw web3.js instruction builders (no Anchor client)
├── idl/bov.json # Anchor IDL
├── docs/architecture.md # Detailed sequence diagrams
└── SOLANA_PLAYGROUND_DEPLOY.md
- Open blind-omnichain-vault.vercel.app
- Connect Phantom wallet (switch to Devnet in Phantom settings)
- Get devnet SOL: faucet.solana.com
- Deposit → Rebalance → Withdraw — all real on-chain transactions
Prerequisites: Node.js ≥ 20, pnpm, Rust ≥ 1.75, Solana CLI ≥ 1.18, Anchor ≥ 0.30
# Clone
git clone https://github.com/thesithunyein/blind-omnichain-vault
cd blind-omnichain-vault
# Install frontend deps
pnpm install
# Build Solana program (requires Solana + Anchor CLI)
cd programs/bov && anchor build
# Run frontend (connects to deployed devnet program)
pnpm --filter app dev
# → http://localhost:3000Note: The deployed devnet program ID is 6jkfCwYGm33xFqBfajHHWxcnG1YJzm2Jd7cME2jUNaaf. The frontend connects to this by default — no local validator needed to try the full flow.
# Deploy to Solana Playground (no CLI needed):
# Follow SOLANA_PLAYGROUND_DEPLOY.md — takes 5 minutes
# Or via CLI:
solana config set --url https://api.devnet.solana.com
anchor deploy --provider.cluster devnet
# Set NEXT_PUBLIC_BOV_PROGRAM_ID=<your-id> in .env.local
pnpm --filter app dev| Artifact | Network | Value |
|---|---|---|
| BOV Program | Solana Devnet | 6jkfCwYGm33xFqBfajHHWxcnG1YJzm2Jd7cME2jUNaaf |
| Frontend | Vercel | blind-omnichain-vault.vercel.app |
| Program IDL | This repo | idl/bov.json |
| Architecture | This repo | docs/architecture.md |
| Component | Status | Detail |
|---|---|---|
| Solana Anchor program | ✅ Deployed & verified | 6jkfCwY… on devnet — deposit, rebalance, withdraw all confirmed |
| Next.js frontend | ✅ Live | Vercel — wallet isolation, encrypted balance display, Solscan links |
| Raw instruction client | ✅ Complete | Web Crypto discriminators + manual Borsh — zero Anchor client dependency |
| Ika dWallet integration | 🔶 Interface complete | DWalletSignRequest event, registry storage — pending Ika public devnet |
| Encrypt FHE integration | 🔶 Interface complete | Vec<u8> ciphertext storage, client-side encryption — pending Encrypt public devnet |
SDK @bov/sdk |
✅ Complete | TypeScript, PDA helpers, Solscan utils |
Ika and Encrypt are both described as pre-alpha devnet in the hackathon docs. BOV's integration surface is fully designed and coded — it activates the moment their programs are publicly reachable.
📺 Watch the full demo on YouTube
The video covers:
- Problem framing: why bridges leak and why public vaults leak
- Architecture: Ika 2PC-MPC dWallets + Encrypt REFHE on Solana
- Live devnet demo: encrypted deposit → blind rebalance → threshold withdraw
- On-chain proof: every transaction verified on Solscan
| Phase | Milestone | Dependencies |
|---|---|---|
| Phase 1 (this submission) | Devnet program + UI + full lifecycle | ✅ Done |
| Phase 2 | Live Ika dWallet signing (native BTC/ETH custody) | Ika public devnet |
| Phase 3 | Live Encrypt REFHE evaluation (on-chain FHE) | Encrypt public devnet |
| Phase 4 | Strategy marketplace — multiple encrypted strategies per vault | Phase 2 + 3 |
| Phase 5 | AI agent vaults — encrypted policy bounds, autonomous trading within limits | Phase 4 |
| Phase 6 | Institutional permissioned vaults — passkeys, recovery, spending limits (Ika WaaS) | Ika mainnet |
Against each judging criterion:
| Criterion | BOV answer |
|---|---|
| Core Integration | BOV is architecturally impossible without both Ika (custody) and Encrypt (privacy). Remove either and the product collapses into something that already exists. |
| Innovation | First encrypted cross-chain vault. First MEV-resistant native-asset rebalance. No existing protocol achieves both. |
| Technical Execution | Real deployed Anchor program on devnet. Full lifecycle confirmed on-chain. Raw Web Crypto + Borsh client (no Anchor client bugs). Wallet-isolated PDAs. |
| Product Potential | Addresses $10T+ institutional asset management market. Clear monetization: management fee on AUM, performance fee on returns. |
| Impact | Enables the only safe path for institutional capital on Solana. Removes both bridge risk and strategy leakage in one protocol. |
| Usability | 3-step deposit flow, glass-morphism UI, real Solscan TX links, encrypted balance badge — polished enough to demo to non-technical investors. |
| Completeness | Deposit ✅ Rebalance ✅ Withdraw ✅ all confirmed on devnet. IDL, SDK, architecture docs all present. |
MIT — see LICENSE.
- Ika — 2PC-MPC dWallet infrastructure and the vision of Solana as a universal control layer
- Encrypt — REFHE + Threshold FHE infrastructure for confidential Solana programs
- Colosseum Frontier — for running the hackathon and pushing the frontier
- Solana Foundation — for the fastest settlement layer on earth
Built by @thesithunyein