Miru

Miru is the first copy trading bot built on DeepBook's on-chain CLOB—mirror top makers via Telegram while keeping full custody of your funds.

The Problem: Copy trading on CEXs and most Telegram bots requires handing over your keys or depositing into custodial vaults. You're trusting a black box with your assets.

Our Solution: A Telegram bot that plugs directly into Sui's DeepBook V3 CLOB, using TradeCap delegation for trustless order mirroring:

• /connect — Sign in with Google via zkLogin (no seed phrase, no extension)
• /pools — Browse live DeepBook trading pools
• /discover SUI_USDC — Find top makers ranked by win rate
• /copy <maker> <pool> 25 — Mirror their orders at custom ratio percentage size
• /setup_trading — One-command BalanceManager + TradeCap setup
• /fund_trading — Deposit SUI/DEEP into your on-chain BalanceManager
• /my_funds — Check your BalanceManager balances
• /positions — Track active copy positions, stop anytime
• /revoke — Revoke the bot's TradeCap instantly

Your funds live in a BalanceManager you own. The bot holds only a TradeCap—it can place orders but cannot withdraw.

How It Works: Sign in with Google (zkLogin) → /setup_trading creates your BalanceManager and grants TradeCap in one step → /fund_trading deposits into your BalanceManager → /discover finds top makers → /copy starts mirroring → Bot listens to DeepBook events and places matching limit orders on your behalf → You keep full custody, revoke anytime.

Why It Matters: DeepBook is Sui's native order book, but there's been no way to copy its best traders without giving up your keys. Miru is the first bot to combine zkLogin onboarding, TradeCap delegation, and real-time event monitoring to bring trustless copy trading to an on-chain CLOB. Bot trades, you own. No custody risk.

Miru is built on four Sui-native primitives that don't exist on other chains:

1. Object Capabilities (TradeCap + MirrorCapability) DeepBook V3's TradeCap is a Sui object — the bot must own and present it to place orders. We also deploy a Move contract with MirrorCapability objects (with expiry and size limits) for position-level delegation. Capabilities can be revoked by deleting the object.

2. zkLogin (Google OAuth → Sui Address) Users authenticate via Google. We generate an ephemeral Ed25519 keypair, bind it to the OAuth token via a nonce, fetch a ZK proof from Mysten's prover, and assemble a zkLoginSignature. The user's Sui address is deterministically derived from their Google sub claim — same user always gets the same address, no seed phrase needed.

3. Programmable Transaction Blocks Every user action is a composed PTB. Setup is one atomic transaction: createAndShareBalanceManager() → depositIntoManager() → mintTradeCap() → transferObjects([tradeCap], botAddress). Intermediate results pass between calls — the TradeCap minted in step 3 is the exact object transferred in step 4. No multicall contract needed.

4. Owned vs. Shared Objects BalanceManagers are shared objects (so both owner and TradeCap holder can access them). MirrorPositions are owned objects (enabling parallel execution across users). ProtocolConfig is shared (global pause). This object topology enables concurrent trading without contention.

Stack: DeepBook V3 SDK, Move contract for position tracking, Supabase, Telegram bot (Telegraf), TypeScript. Dual-client architecture: gRPC for transactions, JSON-RPC for event monitoring . Deployed on mainnet.