Skip to main content
Save the reserve-deposit strategy inactive before opening Simulation for that vault. Simulation uses persisted definitions and synthetic execution outcomes; it does not submit OMS intents or onchain transactions.

​
Run and review

  1. Choose Backtest and From / To, or Look Ahead and Horizon (hours). Review Seed Price (optional) when applicable.
  2. Review selected strategies. Select only the saved strategy IDs you intend to compare; the initial selection can include other loaded definitions.
  3. Review Execution Model, including fill ratio, slippage, rejection/failure probabilities, and latency. These assumptions affect the result.
  4. With manager authority, choose Run Backtest or Run Forward Simulation.
  5. Inspect the charts, Simulation Outcomes, per-strategy results, and Commands. A run is useful only if its inputs and commands exercise the condition you meant to test.
Selected CREATED and IDLE definitions run in the model, without changing their production state. Do not activate a strategy to make it selectable. Unsaved editor changes are not part of the run. These are review expectations, not captured results from a completed reserve-strategy run. Backtests depend on available history and can use fallback seeding; a successful model result is not transaction preflight.

​
Save and load

Choose Save Simulation to retain a named result, or Discard to clear it. Keep the strategy ID/version, rule, size, time range, and model settings with the comparison. Existing simulation found. Running will load cached results. means Load Existing Result retrieves a previous result rather than computing a fresh run. Confirm the loaded scope and assumptions before comparing it with an edit. For the reserve exercise, a deposit should leave the modeled reserve and the next unchanged snapshot should no longer trigger. Fees, price changes, competing strategies, and live settlement can change that outcome. After an approved activation, use Intent History to verify the real fill and idle balance. Endpoint details are in the Strategy Engine API.