Simulation limits

A simulation is evidence about a bounded action under a particular model and state reference. It is not a guarantee that the action will execute later or produce the same result.

​

Preview modes

​

Offline model

An offline-model result checks deterministic planning and internal consistency under the engine’s model. It does not execute against live blockchain state and cannot establish that the action will succeed onchain.

​

Pinned-fork simulation

A pinned-fork result executes the prepared sequence against a specific supported chain state in an isolated environment. It can provide stronger evidence for those exact bytes at that state, but it cannot predict later ordering, state changes, MEV, final gas price, or future protocol behavior.

​

Venue preflight

A venue preflight observes configured market identity, lifecycle, fees, account or position state when required, and visible eligible order-book depth. It is not an order submission and cannot prove acceptance, fee stability, ordering, or a future fill.

​

Estimates can change

Results may become stale because of:

• market movement or slippage;
• network congestion and fee changes;
• liquidity changes;
• interest, collateral, or position changes;
• oracle or indexer updates;
• protocol upgrades or pauses;
• bridge delays or destination-chain conditions; and
• transaction ordering or MEV.

​

Hard-stop conditions

Do not soften or ignore:

• a failed simulation;
• configuration_required;
• stale or expired state references;
• unresolved warnings;
• unsupported actions, chains, assets, markets, or vaults; or
• a missing approval capability.

​

Practical rule

Use a simulation to improve review, not replace it. Confirm the current plan and wallet details immediately before any real approval, and expect the final result to differ when chain or market state changes.