You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since not all exchanges have support for native SL, we need a configuration for each connector to handle the SL on the bot side:
classExchange{features={// One cancels the other: // - Entry order handled by the bot// - Exit order (TP + SL) handled by the exchangeoco: true,// Same as above, but entry order is also handled by the exchangeocoAttached: true,// Entry order + OCO (TP + SL)// If OCO is unsupported, we can use StopOrder. However, only one order can be placed at a time (due to locked funds), // either TP or SL. Workflow: Place SL order immediately after entry, then monitor the ticker. Once the price nears TP, // cancel SL and place the TP order.stopOrder: true,// If neither OCO nor StopOrder is supported, TP and SL must be managed on the bot side.// Simulate the Stop order for SL: monitor the ticker, and when it hits the stop price, place the SL order on the exchange.}
The text was updated successfully, but these errors were encountered:
Some exchanges support native stop loss https://docs.ccxt.com/#/?id=stop-loss-orders
Since not all exchanges have support for native SL, we need a configuration for each connector to handle the SL on the bot side:
The text was updated successfully, but these errors were encountered: