A fixed crypto sleeve faces a 32.27% weekly range and a 44.19% gap below the high
Should the allocator keep the crypto sleeve at its fixed weight and rebalance by rule, or cut the sleeve after a fourth down week and a -14.02% day?
The market facts are real; the decision maker is illustrative.
The week and the position
In the week of 2 February 2026, BTC fell 8.62%, from 76,968.22 to 70,330.38, inside a 32.27% range: it traded to 79,360.00 on Monday, then to 60,000.00 early Friday, a -14.02% Thursday followed by a +12.19% Friday. Volume ran 2.28 times the prior 12-week average and realised volatility reached 91.9% annualised. Three of the four prior weeks were down, and BTC sits 44.19% below its 52-week high. An illustrative allocator runs a small fixed crypto sleeve inside a larger fund, set before these moves.
Judgment
The sleeve's weight, not the weekly return, is the decision. Rebalance to the fixed weight at the week's close, and let the rules-based trade absorb a range this wide; cutting after the -14.02% day and adding after the +12.19% day would trade the same week twice at its extremes. Accept that the sleeve can lose value for months in a drawdown already at 44.19% below the high, and that its small size is the limit, not a prediction. Set any reduction from the sleeve's stated maximum loss, dated before this week.
What would change it
If the fund's mandate sets the crypto sleeve from a volatility target rather than a fixed weight, the 91.9% realised volatility itself triggers a cut and should be followed. If a rebalance is priced far from the week's midpoint range, execution should wait for volume near 2.28 times its average.
What sets this case apart
The allocator decides a rebalancing policy in a two-sided violent week, not a direction; the extremes are one week's range, not a trend signal.