Trade settings

The trade-management settings the wizard exposes beyond the entry filters — how positions are sized, how the martingale ladder averages down, when take-profit / stop-loss / trailing kicks in, how trades chain, and the timing limits. The same descriptions appear as the `?` hints next to each field in the wizard.

Controls on this step

What the app checks before letting you continue, and why.

• What a target is worth, and what it has to clear first — The target is a pip distance from the chain's average entry, so the step shows it three ways: the two prices it would fill at — one from a bare entry, one with every rung in — what it closes for at each of those depths, and what it has to clear before any of that is yours. That last line is the spread plus a round trip of the broker's commission, and it appears only when both can be read exactly for your account. Where they cannot — a USD commission on a non-USD account, a symbol whose quote currency is not your deposit currency, a broker that publishes no commission, a symbol that is not currently streaming — the step says which part is missing instead of printing half a figure, because a threshold that is too low is the one error you would act on. The daily carry is reported beside it rather than inside it: a chain closed the same day pays none of it and one held a week pays seven times it, so no single number is right for both.
• What the trailing stop asks for, and which mode reads which answer — Both armed modes need both numbers, so both are on screen in both. The activation says how far past the chain's average entry price has to go before anything trails; the distance says how far behind the price the stop then sits. Set the activation at or above the take profit and the target fills first every time — the trail never arms, and the step says so. Give back as much as the trail waited for and the stop lands at or below your average the moment it arms, which the step also says. Neither number is invalid on its own, so neither blocks. One switch is offered only under the filter-driven mode: the engine reads "only close if profitable" nowhere else, so under a price trail it would be a setting you could turn on and nothing would ever consult.
• What the ladder preview shows, and when its margin columns are missing — Under the ladder's dials, the Position step draws the orders they produce: one row per order, with where it goes in, how far that is from your entry in pips, its lot, the average the chain reaches once it has filled, and where the chain's shared target then sits. The target moves down the table because it is measured from the AVERAGE, not from your entry — that is what averaging down buys you, and the small number beside it is how far the market must come back from that rung to reach it. The money columns show MARGIN, not position size: what the order ties up at this account's leverage, which is the figure your free margin is spent on. They appear only when they can be exact. On a pair where neither side is your account's currency — EURGBP on a USD account — working out the margin needs an exchange rate the wizard does not have, so the columns are left out instead of being filled with a near-enough number. And the margin shown is at your account's leverage: a broker may require more on some instruments, because the per-symbol tiers are not published to us. Everything is drawn from the last price on the chart, so the real ladder starts wherever your entry filter fires. One last thing worth reading twice: the table is ONE chain. If the bot runs several chains in parallel, the account funds all of them at once, and the band above says what that total comes to.
• The liquidation line, and when there is not one — Where the exchange would close your position depends on three things besides leverage: whether the margin is Isolated or Cross, how much is in the wallet, and the contract's maintenance margin — the exchange closes a position when its equity reaches that level, not when it reaches zero. Isolated risks only the margin posted for this position, so the rest of your balance does not defend it and liquidation sits close: at 100x with a 0.65% maintenance rate the room is about 0.35%, not 1%. Cross puts the whole wallet behind the position, which usually moves liquidation far away or out of reach entirely. When the venue has not reported your balance yet, no line is drawn in Cross at all — a level invented from a balance we do not know would be read as a fact. What is drawn remains an estimate: funding, fees and the higher maintenance rates that apply to larger positions all move liquidation nearer.
• How high the leverage bar goes — The bar stops where the exchange stops for the contract you picked, not at some universal maximum. 125x is the highest figure the venue allows anywhere; most contracts are capped well below it, and ETHUSDT stops at 75x. Offering the difference would mean letting you save a bot with a setting the exchange will refuse — and you would only find out afterwards. Where the venue has not told us its ceiling, the bar is left as it is rather than capped at a number we would be guessing: a wrong ceiling would forbid leverage you are entitled to. One limit is not reflected yet: Binance also lowers the allowance as a position grows, so a very large grid can fall into a stricter band than the bar shows.
• Orders too small for the exchange to fill — Every contract has a minimum order value, and an order below it is simply rejected. The wizard checks the SMALLEST order in your grid, which is not always the base order you typed: with a volume scale under 1 the ladder shrinks as it descends, so the order at risk is the deepest one — the one that fires furthest into a drawdown, when a fill matters most and a rejection is least expected. If any rung falls under the minimum, the bot cannot be saved and you are told which figure to raise. Where the venue has not published a minimum, nothing is checked: refusing against a limit we do not know would mean inventing one.
• A grid the account cannot fund is not saved — The trade budget is what the whole ladder commits if every order fills, and it is bound to your first order — so a first order too large for your balance appears as a budget above it. The wizard refuses to save that and names the largest first order your balance does fund, as a button. Why refused rather than warned about: the budget is the ceiling the engine checks against the grid and it is never compared to your balance, so a grid this size is sent and the exchange refuses the orders that do not fit part-way down the ladder, with the position already open — margin insufficient, at the worst possible moment. Fund the account or lower the first order; either clears it. When your exchange has not reported a balance, nothing is checked at all, because refusing against a figure we do not have would mean inventing one. And “balance” here means what is FREE, not what the wallet holds: an open position keeps margin behind it, and orders resting on the exchange reserve more, so the exchange has less to give you than the wallet shows. Where the venue publishes that figure — Binance does — the wizard sizes against it and shows both numbers side by side. The button offers a configuration that actually works, which sometimes means fewer orders rather than a smaller first one: no order may be under the contract's own minimum, so on a ladder whose every rung would fall below it, trimming the first order alone cannot help.
• The resting window only appears where it is read — “Resting at once” caps how many martingale orders sit on the exchange together, and it only means something when they rest at all. Choose either filter placement and nothing rests — every rung is sent as a market order when price arrives and the filters agree — so the engine never reads the field. The wizard therefore hides it in those two modes rather than letting you set a number nothing acts on. A value you saved earlier is not discarded: the step says it is stored and unused, and switching back to resting orders brings the field back with it.
• A grid that cannot fit its budget is not saved — Your base order, martingale orders and volume scale together decide the most the grid could ever commit. If that total is above your trade budget, the bot can never open its first trade — the engine checks the whole ladder before entering, not one rung at a time, so it would refuse on every bar while still showing as Running. The wizard therefore stops the save and shows both numbers. Any one of three changes clears it: raise the budget, lower the base order, or reduce the martingale orders or volume scale. You will normally never meet this, because the budget and the base order move together and cannot disagree; it is reachable when you pin the first martingale order by hand, which is what unbinds them. The budget-above-balance check beside it now stops the save too. The wizard now names the working value rather than only refusing: press the suggestion to set the base order that fits, or the budget that covers it when your balance can back it.
• A budget larger than the account holds — The budget caps what the grid may commit, and the bot only ever compares it to the grid — never to your balance. So a budget above what the account holds is a ceiling that cannot fire: the whole ladder is allowed through, and the exchange refuses the orders that are not covered part-way down, with the position already open. The wizard says so rather than refusing, because a balance is a number that changes and you may be about to fund it.
• When a stop or a trail quietly does nothing — Each of these three percentages is valid on its own; what can be wrong is the combination, and its symptom is silence. A trail set to arm at or beyond the take profit never arms, because both are measured from the average entry and the target fills first. A give-back wider than break-even puts the trailing stop below your average entry the moment it arms. And a stop measured from the average walks down as martingale orders fill, so whether it ends the cycle early depends on how the ladder is spaced — the wizard computes that rung by rung rather than comparing two percentages. None of the three is refused: the bar shows the reference each one is measured against, and a note says what the combination does.
• Closing one position keeps the rest of the ladder — A chain's pending ladder is cancelled when the CHAIN finishes — its last position closes — not when any single position of it closes. Close one leg of a running chain by hand and the remaining positions keep their ladder, which is what the martingale needs in order to keep averaging into them. The exception is Close all on one hit: there the whole basket is being torn down on purpose, so the ladder goes with it.
• An emptied ladder is rebuilt — While a chain has open positions the platform keeps its pending ladder stocked, and it now also rebuilds one that emptied completely — a fast move can sweep every rung at once. The rebuilt ladder is measured from the chain's deepest open position, so it continues from where the chain actually is. Two consequences worth knowing: rungs you cancel by hand come back on the next bar (they always did while any rung remained — this simply removes the accidental exception), and the supported way to stop a ladder is to stop the instance or close the chain.
• Every position in a chain shares one take-profit — A martingale chain closes as one basket: every rung carries the same take-profit, derived from the chain's average entry price, and it is recalculated whenever a rung is added. The platform re-checks this on every bar as well, so a chain cannot be left with one position on a different price — that position could otherwise be closed on its own and leave the rest without the averaging the ladder exists for.
• Take profit / stop loss must be positive — When Take Profit or Stop Loss is turned on, its pip value must be a positive number — a zero or blank value would leave the position unprotected without you noticing.

Filters → · Strategies →