Skip to main content

Quanta Exo Trader

Quanta exoTrader General FAQ

Navigation

This FAQ follows the same operating narrative as the full exoTrader documentation set: structured signals, controlled execution and measurable behaviour.

What is exoTrader?

exoTrader is a quantitative trading strategy for Gunbot that combines WaveTrend-led confluence with explicit execution and risk controls.

What outcomes is exoTrader trying to achieve?

exoTrader targets operating outcomes: more disciplined signal quality, tighter exposure control, deterministic order lifecycle management and transparent runtime observability.

These are strategic objectives, not guaranteed financial outcomes.

Why can exoTrader skip or pause trades?

Common causes include timer cooldowns, break-even restrictions, trend protection, minimum notional constraints, side toggles or stale-order safeguards.

How should I size deployment initially?

Start conservatively with TRADE_LIMIT, validate behaviour across multiple regimes and scale only after metrics confirm consistency.

What is partial sell used for?

Partial sell allows controlled profit-taking while retaining strategic exposure. Behaviour is governed by PARTIAL_SELL_RATIO and PARTIAL_SELL_GAIN.

Why might orders be rejected?

Typical causes include exchange minimums, insufficient balances, unsupported order mode/positioning settings or venue-side constraints.

Is verbose mode required?

No. VERBOSE is optional and mainly for diagnostics and tuning.

Can I run multiple pairs?

Yes, but each pair should be treated as an independent risk unit with dedicated validation and sizing discipline.

What should I monitor first in production?

Start with operational health and gating behaviour, then review exposure/volume context, then evaluate PnL quality.

Next steps

Follow this path to compare strategy behaviour, validate results and activate licensing.

Related documentation

Continue through the Quanta Exo Trader knowledge base.

Previous

Quanta exoTrader Configuration

Next

Quanta exoTrader: Regime-Aware Execution With Signal Confluence

Last updated 10 February 2026
← Documentation index