LucraX prefers native SL/TP (attached to the position at the exchange) whenever the venue supports it. Native means the exchange enforces the stop / target, so a brief LucraX outage or network blip can't leave a position unprotected.
Native support by venue
| Venue | Native SL | Native TP | Notes |
|---|---|---|---|
| Binance Futures | Yes | Yes | STOP_MARKET / TAKE_PROFIT_MARKET |
| ByBit | Yes | Yes | Position-attached |
| BitMEX | Yes | Yes | execInst: "Close" |
| Hyperliquid | Yes | Yes | TPSL order type |
| LNMarkets | Yes | Yes | Set on trade open |
| Interactive Brokers | Yes | Yes | Bracket orders |
| Tradovate | Yes | Yes | OSO / OCO |
| TradeStation | Yes | Yes | BRK order group |
Client-side fallback
When native isn't supported (rare in modern setups), the engine watches the WebSocket price feed and submits a market close when the level is breached. Less reliable - depends on the engine being healthy and the WS feed being current.
What the engine guarantees
When an entry attaches native SL/TP, the engine suppresses client-side stop/target signals from the interpreter to prevent double-closes. Custom exit conditions (e.g. RSI exit) still fire - they're a different category from stops/targets.
Pitfalls
- Mixing native and client-side intentions by editing exit rules mid-trade can produce ambiguous behavior. Wait for the position to close before changing exit logic.
- Some exchanges silently reduce stop precision to their tick size; the engine rounds to fit.