SL / TP / Trailing stop

HookTrader places STOP_MARKET and TAKE_PROFIT_MARKET algo orders on Binance USDⓈ-M Futures and keeps them aligned with your strategy's actions. This section explains the moving parts.

Articles:

• How brackets work — what's placed on entry, how scale-ins and partials are tracked.
• Trailing stop — activation, ratchet, autonomous enforcement.
• Partial fills — what happens when an order fills in pieces.
• Commissions — gross vs net, the MIXED asset edge case.

At a glance

entry alert
  ↓
MARKET entry order  → fill captured
  ↓
SL  bracket: STOP_MARKET reduceOnly       sized to entry qty
TPs bracket: TAKE_PROFIT_MARKET reduceOnly per pre-staged TP level (up to 8)
TPmax:       TAKE_PROFIT_MARKET reduceOnly full-close
  ↓
HookTrader monitors the live price feed
  ↓ on each tick
  ├─ check TP thresholds → run action lists if crossed
  └─ check trail SL      → close if trail_active and price crossed trail_sl

Two layers of enforcement

Every active trade has redundant protection:

1. Exchange-side algo orders — fire on the exchange independent of HookTrader. Survive HookTrader restarts. The default safety net.
2. Autonomous price monitor — HookTrader checks every price tick against the trade's SL / trail / TP levels, and emergency-closes if something is missing or didn't fire.

This means a trade is still protected if:

• The Binance algo order fails to fire (rare).
• HookTrader restarts mid-trade (open trades are automatically re-armed on startup).
• The price feed connection drops (HookTrader automatically falls back to a secondary price source).

What if HookTrader is temporarily unavailable?

Your exchange-side stop-loss and take-profit orders remain active on Binance regardless. When HookTrader reconnects, it picks up where it left off and reconciles any fills that happened in the meantime. See Troubleshooting → Open-trade state loss for edge cases.