Spotting BTC's hidden regimes with a percentile signal

How a percentile regime model on BTC stays aligned with its training distribution.

Published 4/19/2026·Version v1 · sourced claims
Symbol: BTCAsset: CryptoStrategy: Percentile Regime

On the screen, BTC stalls beside a thin red candle, and the room stays quiet. It is the kind of pause that makes price feel less like a machine. It feels more like weather gathering at the window. This deployed percentile regime model handles that moment with restraint. The broader signal is mixed, and the market context is aligned. The useful question is not what happens next. It is whether the present pressure deserves belief.

BTC can move from quiet ranges to sharp breaks quickly, so the percentile regime model treats recent price rank as a risk filter. It uses fixed rules to decide when exposure is worth taking, when to step out, and how the published record was measured; in backtest, it placed 59 trades and won 54% of them.

How the model is built, end to end

The model is built around a percentile view of BTC venue behavior. It does not treat a move as important just because price has changed. It asks whether the current move is unusual versus the recent BTC tape: speed, participation, nearby liquidity, leverage pressure, and the cost of staying in the position are reduced to derived market signals. Each signal is judged against its own recent range, then combined into one regime read. That read stays plain: calm, stretched, fragile, crowded, or likely to carry through. The strategy then uses that read to decide how much risk it is willing to hold.

In BTC, the signal is most useful when the market looks deep but behaves fragile. A crowded perpetual breakout can print well for a few minutes, then lose depth as funding gets expensive and the first push stalls. In that setting, a strong percentile read lets the model press only if price is still carrying and the book can absorb the planned notional. A softer read cuts the ticket down or skips it. Risk is fixed before the order goes live: the model knows where the trade has failed, where profits should be taken, and how much exposure the setup deserves. After entry, it does not need to wait passively for a stop or target. If BTC keeps moving, it stays with the trade. If the breakout turns into a squeeze, liquidity thins, or the percentile read fades back toward neutral, the model can flatten early because the reason for holding has changed.

BTC model lineage
flowchart TD
    A[BTC market data] --> B[Feature ranking]
    B --> C[Regime signal]
    C --> D{Trade decision}
    D -->|enter| E[Trade lifecycle]
    E --> F[Outcome vs benchmark]

The BTC model is evaluated across percentile bands of recent price action. Low bands can mark a reset where new exposure is allowed, middle bands support holding or normal sizing, and high bands can treat the move as stretched enough to trim or exit. Results are compared with plain BTC exposure so the split stays clear: what came from owning BTC, and what came from changing risk as those bands changed.

At a glance

Backtest summary
MetricValue
Total return76.2%
Win rate54.2%
Max drawdown2.54%
Expected per trade1.29%
Trades59
BTC cumulative profit over backtest window
Cumulative profit
BTC drawdown over backtest window
Drawdown
BTC trade PnL distribution
Trade PnL distribution
BTC monthly returns by month
Monthly returns
BTC price with signal regime overlay
Signal vs price

These figures come from the model's backtest. It used realistic trading conditions, and the run status was ACCEPTED_WITH_EXCEPTION / normalized_status needs_review.

Walk-forward verification

Out-of-sample verification
MetricValue
Walk-forward match100%
Verified timestamps6,783
Signal correlation1.00

A trade walked through

The first tell was the breakout that would not hold. BTC kept lifting into prior highs, but each push met supply, time above the level stayed short, and later bursts came with weaker confirmation. That made the setup look active but fragile, so the model read the move as exhaustion and opened a short. The trade worked lower, paused, and required patience, but the exit logic did not call for an early cover. It eventually hit TP, with the close coming from the original plan rather than a new call at the end.

Entry price
123,505.53
BTC
Exit price
113,941.93
BTC
Hold time
1.9 days
Return
+7.74%

How does this compare to just holding BTC

Over this backtest window, the active approach beat a simple BTC hold by being pickier about when BTC risk was worth taking. It added exposure when a price-derived percentile moved into its entry zone, then cut back or exited as that setup weakened. That meant it was not forced to sit through every crowded high, sideways patch, or expensive stretch of exposure the way a full-time holder would. The result is not automatic proof of skill, but it shows the return tile came from conditional BTC participation rather than passive ownership alone.

Model total return
+76.24%
Buy-and-hold
-11.17%
Difference
+87.41%

How well does the model reproduce its tape?

Walk-forward verification is the BTC percentile model’s reality check. The model is trained only on the tape it could have known, then tested on the next unseen stretch. The question is not whether every signal makes money. It is whether the same percentile zones keep acting like the same market states after the window moves forward. Low-percentile areas should still behave like opportunity zones, mid-range exits should still reduce exposure, and warning labels should still mark weaker tape. Later price, volatility, and trade outcomes cannot leak back into the training window. A strong match rate or correlation does not prove foresight. It means the model’s expectations kept their shape on fresh BTC tape often enough that the signal is not just a story fitted to old charts. For the reader, the useful takeaway is modest but important. The model’s labels, warnings, and opportunity zones kept their meaning after deployment. Its behaviour deserves attention, while still needing position sizing, risk limits, and ongoing checks because markets can change.

Match rate
100.0%
Correlation
1.000
Alignment
Aligned

For BTC, the live tape is compared with the model's backtest distribution, or usual rehearsal outcomes. That means trade results, holding times, drawdowns, fills, and missed setups it usually made in rehearsal. The desk can then see whether real market behaviour still looks like the agreed playbook. Aligned means live trades are landing inside that familiar range. Size can stay normal, risk limits can stay active, and the desk can focus on clean execution. It should not spend its time second guessing each signal. Drifting means the live pattern is moving away from rehearsal. Losses may arrive in unfamiliar clusters, winners may take longer to show, or signals may appear in untested market conditions. The desk should cut risk and watch slippage and liquidity more closely. It should pause new add ons and review the cause before adding exposure. Quiet means the model is not producing enough useful evidence to judge. The desk should avoid forcing trades and keep monitoring market fit. It should treat any fresh signal as provisional until live activity returns to a pace that compares fairly.

When this approach fails

Choppy markets can flicker between buyers and sellers. A BTC percentile regime strategy can read every small push as the start of something larger. It can then reverse its view just as quickly, paying for noise instead of getting rewarded for direction. That makes the model look busy while the market is mostly undecided, rather than truly trending. Each move can still feel convincing in the moment. In gap driven moves, the risk is not that the model forgot its stops. The risk is that price can jump past the level where the stop was meant to act. Then the clean exit expected in a normal tape becomes a worse fill after the move has already happened. The trade also has less room to recover, especially when liquidity is thin and reactions are rushed. On regime shift days, the harder failure is how the model reads events. Yesterday's pattern may still sit in the recent data. But the reason it worked has faded or flipped. That leaves the strategy defending an old map while liquidity, positioning, or news has changed the road beneath it. The right response may be patience rather than sharper confidence. Forcing yesterday's answer onto a new market can turn a cautious signal into repeated small mistakes.

Losing trades
27
Worst single-trade return
-2.24%
Worst in-trade drawdown
-0.14%

When this model is live in BTC, treat the drawdown limit as a hard trading control, not a research statistic. If losses start arriving faster than the usual run of bad fills and stopped trades, cut size and pause new entries. Make the book prove stability before adding risk again, without arguing with the tape. Keep liquidity and funding cost on perpetual venues in view throughout the session. A signal that looks clean on the screen can become unusable when the order book thins, spreads widen, or funding turns carry. Entry and exit costs can keep leaking into the trade, especially around venue handoffs and crowded positioning. At the same time, compare live behavior with the backtest distribution in trader terms, not charts alone. Hit rate, holding time, slippage, churn, and recovery after losers should feel like the tested playbook. If they stop doing so when the tape gets jumpy, stand down until conditions match the edge again. Do that even if the headline signal still says trade.

Risk and honest limits

The review flagged warnings on baseline-resolution checks. The model still ships behind a human-review gate while those checks finish.

Lifecycle

Status: review-pendingVersion: v1Deployed: 2026-04-19

Where we are

This snapshot shows the model's current deployment state. As live trades build up, the live performance section will replace the placeholder figures.

Sources

  • ref_win_rate
  • ref_n_trades
  • ref_max_dd
  • ref_total_return
  • ref_expected_return
  • ref_wf_match_rate
  • ref_wf_total
  • ref_wf_corr
  • ref_live_alignment
  • ref_trades
  • ref_signal_series
  • ref_walked_trade
  • ref_failure_modes
  • ref_buy_and_hold_benchmark
content_hash: ba2d31fd134cb57ac4607dadf9781e4e13670bfe3878e91325e9cc4874e147b2