Loss limits: decide the maximum damage before the trade exists

The short answer

A loss limit defines how much capital may be damaged at several levels: one trade, all positions currently open, one session, and a larger drawdown window. It is written before entry, measured consistently, and connected to an action such as reducing size, closing risk, disabling execution, or ending the session.

There is no universal correct percentage. Account purpose, income stability, liquidity needs, strategy variance, market depth, custody, and personal risk tolerance differ. Regulators consistently warn that speculative trading should use risk capital rather than money needed for living expenses, emergencies, or long-term obligations.

Use a hierarchy, not one isolated number

• Risk-capital boundary: the capital pool whose complete loss would not impair required expenses, emergency savings, debt obligations, or essential long-term goals.
• Per-trade loss: the estimated capital loss if the specific invalidation and exit path occur under a documented adverse scenario.
• Total open risk: the combined loss across positions if linked assets, venues, or counterparties fail together rather than independently.
• Session loss: realized loss, relevant costs, and explicitly defined open loss accumulated during the same operating window.
• Drawdown boundary: a multi-session decline that triggers a size reduction, strategy review, or pause before normal risk resumes.

The smaller boundary should fit inside the larger one. If three ordinary losses can exceed the session cap, the position size, number of attempts, or both are inconsistent with the plan.

Define what counts as loss

Choose one account equity source and one time boundary. State whether the session measure includes only realized P&L or also marks open positions to a current executable exit. Include network fees, priority and tip costs, platform fees, token transfer fees, price impact, slippage, failed transactions, bridge costs, and funding or borrow costs where they apply.

Do not let wallet transfers, a new subaccount, a new token, or a switch from SOL to dollars reset the count. Normalize the same economic activity into one base currency and preserve the valuation timestamp and price source.

The planned stop price is not the maximum loss

A stop or alert expresses an intended response. It does not guarantee a fill, route, minimum output, or available buyer. Thin liquidity, a large gap, rapid reserve change, transfer restrictions, congestion, expired blockhashes, or a failed bot can make the realized exit worse than the trigger.

Estimate loss from a current executable quote for the intended size, then apply a documented adverse scenario. Use the liquidity-depth workflow and quote-to-fill record so the risk estimate includes the actual route and costs instead of a chart line.

Aggregate positions by failure path

Five token positions are not five independent risks when they depend on the same market narrative, SOL price, wallet, RPC, bridge, terminal, pool family, creator cluster, or exit route. Group exposures by the events that can make them lose together, then stress the combined exit under reduced depth and higher costs.

Count pending orders and partially filled transactions. Capital committed to a second attempt while the first transaction's status is unknown can exceed the intended boundary even when each ticket looks acceptable alone.

The breach rule is part of the limit

Write the exact trigger, data source, action, owner, and reset condition. A breach may disable quick-buy buttons, cancel open orders, reduce or close positions, remove trading funds from a hot wallet, end the session, and require review before risk is restored. Safety actions should not depend on winning the next trade.

If closing every position immediately would create more harm because liquidity is impaired, define the contingency in advance: which risks close first, maximum residual exposure, allowed routes, and who can override. Document every override as a rule breach or emergency exception, not as a silent new strategy.

Scale down before changing the strategy

A drawdown protocol can move through predetermined states: normal size, reduced size, observation or simulated trading, and full review. The recovery rule should depend on completed review and a defined evidence threshold—not on reaching the old account high through one larger bet.

Separate valid strategy losses from execution errors and rule violations. The account declined in all three cases, but the corrective action differs. Variance may require a larger sample; bad routing may require an execution fix; repeated oversizing may require stronger controls.

A loss-limit setup workflow

1. Ring-fence risk capital. Exclude required expenses, emergency savings, debt obligations, and capital assigned to other goals.
2. Choose the hierarchy. Write per-trade, total-open, session, and drawdown boundaries in one base currency.
3. Define measurement. State treatment of open positions, transfers, partial fills, costs, and valuation timestamps.
4. Model executable loss. Use intended-size quotes, adverse depth, route costs, and operational-failure scenarios.
5. Attach actions. Configure alerts and access controls, then write the close, reduce, pause, and escalation sequence.
6. Test the rule. Rehearse a failed order, unknown transaction, rapid gap, and multi-position loss before live capital depends on the response.

What belongs in the journal

Record risk-capital balance, account equity source, base currency, per-trade and aggregate boundaries, session start and reset time, open-risk groups, intended exit and adverse scenario, all estimated costs, alert and order configuration, realized and marked loss, breach timestamp, actions taken, overrides, transaction uncertainty, residual exposure, and the conditions required before normal size returns.

Primary and official sources