Position Sizing When Stops May Not Fill

MemeScope editorial · 2 minute read

Keep the planned loss and the total-loss exposure visible at the same time.

A stop-distance model is conditional

A common planning calculation divides a risk budget by the intended stop distance. That arithmetic assumes the position can actually be exited near the planned level. A gap, liquidity collapse, restrictive token behavior, or failed transaction can invalidate the assumption. The resulting position size is not a guarantee that losses stay inside the budget.

Use two loss scenarios

Write down both the planned stop loss and the amount exposed if the entire position becomes worthless. Consider your total speculative exposure across tokens and related narratives. Ten positions can behave like one concentrated bet when they depend on the same attention cycle or liquidity source. Position caps should be explicit rather than inferred from how confident a chart looks.

Size after investigating execution

Larger size can change the trade itself through price impact and exit difficulty. Check routes and conditions for the intended order, and reduce or skip when the assumptions are not supportable. Educational calculator defaults are examples, not personalized recommendations. A realistic total-loss amount may be the binding constraint even when the stop-distance calculation allows more.

Put it into practice

1. Calculate the planned risk budget.
2. Show total position loss beside the stop estimate.
3. Review correlated exposure across holdings.
4. Reassess size when liquidity changes.

A worked research example

With hypothetical capital of 1,000, a 1% budget is 10. A 10% stop-distance model implies a 100 position. If the token becomes unsellable, the exposed amount is 100, not 10. Both numbers belong on the trade plan before entry.

Source for further investigation: Official documentation or resource. Provider mechanics change; recheck before acting.

Use the planning tools · Record your research · Read the methodology

Found an error? Request a correction.