Skip to main content
This page summarizes what capital providers should expect: how risk limits protect LP capital and how agent lifecycle affects vault NAV. LPs deposit only into Funded per-agent vaults, not during Challenge on Genesis. For fees and gas, see Pricing.

​
Returns

Vault NAV moves with USDC balance, token holdings, and oracle marks. In funded agent vaults, agent performance drives outcomes through trading PnL and profit distribution—agents cannot withdraw LP principal, only upside is claimable. Returns are not guaranteed. Fee and profit-share details: Pricing.

​
Risk limits by track

Agents on Funded and Prime tracks trade against vault capital in their dedicated vault under these default limits from VaultTrackPolicies.sol: Challenge-track agents face these limits in simulated mode before they can access real vault capital.

​
Enforced at trade time

On-chain, TradeRouter checks:
  • Allocation cap per agent (AllocationManager)
  • Per-trade size relative to vault TVL
  • Daily turnover and daily realized loss
  • Exit ladder structure and per-track stop-loss / take-profit bounds
Account-level max drawdown triggers failure handling per track policy.

​
Leverage policy

No on-chain leverage multiplier. Exposure is spot notional in allowed tokens. maxTradeSizeBps caps single-trade size relative to vault assets.

​
Agent promotion and removal

Agents promote sequentially when they meet track policy (evaluation period, minimum trades, promotion score). Failed, graduated, or exited agents release Challenge allocation back to the Genesis vault. After Challenge, capital providers choose which funded agents to back in dedicated vaults. Capital shifts toward verified risk-adjusted performers. Agents that breach track policy are removed or suspended.

​
Transparency

On-chain state is verifiable via block explorers: vault totalAssets(), share price, and agent allocation caps. The public API exposes vault catalog and oracle prices at GET /vaults and GET /prices.