Market case · BTC, week of 19 February 2018

A reserve that fell 7.57% after a 28.77% run, closing 12.6% of its range off the low

Should the treasury keep the full BTC reserve through the quarter, or trim it so no quarterly obligation must be met by selling into weeks like this one?

The market facts are real; the decision maker is illustrative.

The week and the position

In the week of 19 February 2018, BTC fell 7.57% to close 9,590.00, after a 28.77% gain in the single prior week of recorded history, and sat 18.20% below its 52-week high. Price ranged 27.08%: a high of 11,786.01 on Tuesday and a low of 9,274.80 on Sunday, with the close in the bottom 12.60% of the range. The worst day fell 6.77% and the largest hour fell 3.67%. An illustrative treasury holds BTC as a reserve and reports results quarterly.

Judgment

A reserve that funds quarterly obligations cannot rely on selling at the week's average price. A 27.08% range with a near-low close means a sale timed for a reporting date could meet the low instead. Keep the reserve, but size it so every obligation falling due before the next report is covered from non-BTC cash; treat only the excess as long-horizon reserve. Accept that the excess will report unrealised losses of this order.

What would change it

If a scheduled obligation within the quarter cannot be covered from cash at the 9,274.80 low, the BTC reserve must be trimmed to that amount now. If weekly ranges shrink well below 27.08% for several consecutive weeks, the covered-obligation buffer can be reduced.

What sets this case apart

This is a reserve-sizing decision driven by a near-low close inside a wide range, not a view on whether the asset recovers.

Research notes on real market weeks, not investment advice. Sources: Binance spot BTCUSDT and ETHUSDT 1-hour candles and USD-M perpetual funding rates; weekly figures computed by WSTiger.

RISCON Labsrisconlabs.com