Candleread
Crypto and DeFi · Trading Crypto vs Forex

Position sizing inside crypto's wider ranges

Show how to translate the same R-based position-sizing formula into crypto by lowering risk per trade when stops are wider.

3 min read+25 XPLesson 72 of 79
Start reading

Lesson path

Crypto and DeFi

Trading Crypto vs Forex

Lesson 72 of 7991%
Lesson 72 of 79Crypto and DeFiTrading Crypto vs Forex

Today's tiny win: make one idea click.

Show how to translate the same R-based position-sizing formula into crypto by lowering risk per trade when stops are wider.

Learn itSpot itPass the check

Same formula, different inputs

The good news in crypto is that the position-sizing formula does not change. It is the same identity you used in forex. Risk per trade equals account equity times risk percent. Position size equals risk per trade divided by stop distance. Two lines of arithmetic, same on every screen-based market on earth. The bad news is that one of the inputs — stop distance — is usually a lot bigger in crypto, and if you do not adjust another input, your dollar risk balloons quietly.

Wick shows a calculator reading $2.50 under a bubble saying $500 times 0.5% equals $2.50 risk, a worked default for sizing crypto trades.$500 × 0.5% = $2.50 risk$2.50
Wick saysOn a $500 account, 0.5% risk is $2.50 per trade, and it is supposed to feel small.

Consider a $500 account. In forex you might risk 1% per trade — that is $5 of risk — and use a 30-pip stop on EUR/USD. The position-size math gives you a tidy micro position. Now bring the same trader to BTC where, to survive normal noise, your stop has to sit 2 to 3% away from entry. If you keep risk at 1% of equity, the dollar risk is still $5 — which is fine — but the position size becomes much smaller in BTC terms because the stop is wider. Many beginners try to fix this by increasing risk percent so the position size feels bigger. That is the trap.

Here is a defensible default for a $500 crypto account. Risk 0.5% per trade in crypto when you would have risked 1% in forex, simply because the typical stop is wider. That works out to $2.50 of risk per trade. It feels small. It is supposed to feel small. The win column of a small account is built one survival trade at a time. A trader who blows up on a single bad alt trade does not get to deploy the next ten setups that would have made the month.

Two cards: a green card says stop twice as wide, risk half as much, a coral card says raise risk % so size feels bigger, naming the common sizing trap.Do thisStop twice aswide, risk half asmuchNot thisRaise risk % sosize feels bigger
Wick saysWhen the stop is twice as wide, risk half as much, not twice as much.

One more refinement. If you are trading mid-cap or low-cap alts where stops can be 5 to 10% wide, that is not a place to risk a normal 0.5%. Scale risk down again. Some seasoned crypto traders use 0.25% or less on the wildest names. The pattern is consistent. As stop distance grows, risk percent has to shrink to keep dollar damage constant. The math will tell you. The discomfort of small position sizes is the price of staying in the game.

Wick points at a chalkboard: forex 1%, BTC 0.5%, wild alts 0.25%, showing risk per trade shrinking as the stop distance grows.Wider stop, less riskForex: 1%BTC: 0.5%Wild alts: 0.25%
Wick saysAs stops get wider, risk percent shrinks: about 1% forex, 0.5% BTC, 0.25% or less on wild alts.

Recap. Sizing formula is identical between forex and crypto. Crypto stops are usually wider, so risk per trade should be lower — start at 0.5% on a $500 account, lower for wilder names. Same one R of risk, kept in dollar terms you can actually survive.

Knowledge check

Answer before moving on.

0 / 2 answered

1. On a $500 account, you used to risk 1% per trade on EUR/USD. Your typical crypto stop is roughly twice as wide as your forex stop. What is the cleanest adjustment?

2. What does the position-sizing formula stay constant across forex and crypto?

Lesson handoff

Pass the check before saving.

Use the knowledge check first. After you pass it, this card turns into the save-and-continue handoff.