Kuru CLOB

Kuru is a fully on-chain Monad order book with four liquidity sources, including paired KuruAMMVaults, concentrated flip orders and a v2-style backstop AMM. The investable pooled position is not a passive CLOB cash balance: users deposit base and quote assets, receive LP shares and withdraw the inventory left after fills. Kuru calls the receipt an ERC-20 vault for AMM liquidity and warns that adverse markets can cause losses. That exact paired-inventory perimeter fits the version-1 AMM-LP dossier even though trades settle through an order book. The 2026-08-16 survey measured about $1.34M in the shared Monad MarginAccount; direct limit-order trading and Kuru Flow routing are not recommended positions.

Review triggers: events that reopen the verdict
• Kuru ships a genuinely single-asset, non-market-making product whose return and exit do not depend on paired order-book or AMM inventory
• The mandate changes only after an exact vault, pair, share supply, authorities, incident history and proposed-size stressed withdrawal are mapped and compared with direct holdings and conventional AMM liquidity

Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.

The research file

Product perimeter and class fit

Kuru combines external limit orders with public liquidity vaults, flip orders and a backstop AMM in one order book. The KuruAMMVault accepts both base and quote assets, mints ERC-20 LP shares, maintains bid and ask inventory and returns proportional token balances on withdrawal. Its own contract documentation labels the receipt AMM liquidity and notes that withdrawal ratios can differ after fills. The AMM-LP dossier therefore applies to the pooled vault and backstop positions; it does not classify a user’s self-directed limit order or a routed Kuru Flow swap as an LP investment.

Current observation and accounting boundary

The DefiLlama adapter discovers markets from Router MarketRegistered events, then sums all supported token balances in the shared Monad MarginAccount. The 2026-08-16 API read reported approximately $1.34M on Monad. That number includes inventory supporting the integrated trading stack and is not a vault-by-vault NAV or exit measure, so a recommendation would first need an exact market, vault address, token pair, share supply and attributable reserve rather than treating aggregate CLOB TVL as available liquidity.

Control, loss and exit applicability

Vault inventory fills against takers and can become skewed toward one token; virtual rebalancing affects share calculation but does not restore the withdrawn token mix. Kuru warns that adverse market conditions may reduce returns or cause losses and documents a four-day deposit lock for managed vaults. Router and vault implementations are upgradeable, the Router is the default owner of markets, and market states can soft-pause or hard-pause operations. Published Spearbit and Cantina reviews reduce implementation uncertainty but do not remove inventory, upgrade, pause or Monad-chain risk.

Decision and comparison

The pooled claim has the same client-facing problem as other two-sided exchange inventory: fills change the asset mix, range and spread choices alter loss paths, and aggregate TVL does not prove a stressed exit. The shared AMM-LP dossier therefore rejects the exact LP perimeter. Reopen only if Kuru offers a genuinely single-asset non-market-making product or the mandate changes; then identify the exact vault and compare its realized inventory loss, lock and withdrawal path against direct token holdings and a conventional constant-product or concentrated-liquidity pool.

Class rule

The amm lp class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Kuru — integrated liquidity perimeter · primary · accessed 2026-08-16
  Supports: vaults, flip orders, backstop AMM, external market makers, single order book
• Kuru — public vault product · primary · accessed 2026-08-16
  Supports: managed vault, market making, shared PnL, four-day lock, loss warning
• Kuru — KuruAMMVault contract · primary · accessed 2026-08-16
  Supports: paired deposits, LP shares, bid and ask inventory, virtual rebalancing, pro-rata withdrawal, upgrade owner
• Kuru — contract architecture and authority · primary · accessed 2026-08-16
  Supports: Router owner, upgrade authority, MarginAccount, order book, discretized AMM liquidity
• Kuru — audit reports · primary · accessed 2026-08-16
  Supports: Spearbit, Cantina, post-fix reviews, core contract audit scope
• DefiLlama adapter — Kuru MarginAccount accounting · secondary · accessed 2026-08-16
  Supports: Router events, market discovery, MarginAccount, aggregate token balances, Monad
• DefiLlama — Kuru CLOB survey record · secondary · accessed 2026-08-16
  Supports: current TVL, Monad, Dexs category

Inherited controls

The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.