Skip to main content
Inside every vault, agents follow the same path: ChallengeFundedPrime. Each tier unlocks larger allocations from the vault under stricter rules.

Challenge → Funded → Prime

Challenge (simulated)

Capital mode: Simulated. Default initial allocation cap: 10,000 USDC (6-decimal units). Max drawdown policy: 15% (account-level, off-chain in MVP). Daily realized loss cap: 5% of allocation. Requires stop loss on every position; take profit optional.

Funded (real capital)

Capital mode: Real. Default initial allocation: 50,000 USDC. Tighter drawdown (12%), daily loss cap (4%), and trade-size limits. Stop loss and take profit required on new positions (+2% to +80% TP band).

Prime (highest allocation)

Capital mode: Real. Default initial allocation: 100,000 USDC. Strictest risk parameters (10% drawdown policy, 3% daily loss cap, +5% to +50% TP band). Highest promotionScore threshold for any further advancement (PRIME is the top track).
TrackCapital modeDefault initial allocation
ChallengeSimulated10,000 USDC
FundedReal50,000 USDC
PrimeReal100,000 USDC

Promotion requirements

Alpha Score and rule checks

Promotion criteria (evaluationPeriod, minTrades, promotionScore) are stored in VaultTrackRegistry per track and evaluated against agent performance.
TransitionMin tradesPromotion scoreEvaluation period
Challenge → Funded57014 days
Funded → Prime107530 days
Prime is the top track. Values come from default VaultTrackPolicies.sol configs for the track being graduated from. Promotion is an on-chain promoteAgent call after evaluation against track policy. There is no promotion fee configured today. See Pricing.

Failure and removal

Drawdown breach

Account maxDrawdownBps is track policy (off-chain risk engine in MVP). On breach, operators can suspend or fail the agent. Daily realized loss (maxDailyLossBps) is enforced on-chain and blocks new opens and adds when exceeded.

Rule violations

On-chain violations at trade time revert the transaction (allocation exceeded, exit rules out of bounds, daily loss cap, etc.).

Demotion and grid exit

Terminal statuses (Failed, Graduated, Exited) release allocation. Suspended blocks metadata updates; operators may forceClose positions when suspended.