This is the trilogy’s whether/when page. Lump Sum or Ladder In? teaches the general lesson; Your Bitcoin Deployment Plan models deploying today. This page owns the question the others deliberately leave alone: from a given position in the channel, did waiting for a lower entry historically leave you with more Bitcoin — or did the dip you were waiting for usually never come?
Waiting, here, is position-based — not about timing. “Wait” means hold out for a lower channel position, capped at two years. It is never a signal or guarantee that price will drop; it is a read on what history did at this position.
—
From this position, did waiting pay?
—Drag the slider to explore any channel position — the dashed line and blue dots on the chart move with it, and the answer below updates together. The ▲ today marker is where Bitcoin sits right now.
The Power Law channel across history. The dashed blue line is the position you’re exploring; the blue dots are the historical entries near it the answer is built from.
Historically, waiting for a lower entry left you with more Bitcoin this often.
—
of entries here fell at least 20% within two years.
median worst drawdown — —.
Likelihood and depth together — both drawn from history at this position, not a forecast. Past patterns can’t predict future prices.
—
—
—
The general lesson — how channel position shifts the lump-vs-ladder choice. Start here.
Model your own deployment today — lump, ladder, or hybrid — and the forward-looking Projection. This page is retrospective by design; that is where the forward view lives.
This page is the trilogy’s most timing-adjacent, so its guardrails are the strictest. It is a read on what history did at a position — never a signal that price will fall, and never a call to wait for a dip.
Historical, not predictive
Every figure here is computed from what happened at this channel position since 2014. The Power Law is an empirical regularity, not a law of nature; past patterns cannot promise future prices. Use this to understand risk at a position, not to forecast the next move.
“Waiting” is a position read, not a market call
Waiting here means holding out for a lower channel position, capped at two years — and the whole point is that the dip often never came. Nothing on this page tells you price will drop. When the waiting-paid rate is low, the clear reading is to deploy decisively.
Laddering is the response to risk, not a timing bet
High in the channel, the case for laddering or patience is a drawdown hedge — it trades some expected upside for staying power. It is not an attempt to call the top. If a drawdown would push you to capitulate, that hedge is worth more than the numbers show.
- Channel position: the log-space location between the 0.42× floor and the 3× upper band, shown only as a ×-trend multiple and its plain-language label — the same vocabulary as the rest of the trilogy.
- Waiting (position-based): from an entry at position P, “wait” means hold out until channel position drops at least 0.15 below P, capped at two years. If no lower entry arrives in that window, the waiter deploys at the two-year price — waiting failed. We report two separate things: how often a lower entry arrived at all, and — only among the entries where one did — how much more Bitcoin the same dollars then bought (measured as 1 / price, waiter versus deploy-now). Keeping these separate avoids conflating “a dip rarely came” with the size of the forward run that followed the rare deep bottoms.
- Waiting-paid rate: the share of historical entries near a position where waiting ended with more Bitcoin. Never-arrived: the share where no lower entry came within two years.
- Drawdown: likelihood is the share of entries that fell at least 20% within two years; depth is the median worst drawdown. Its coins-equivalent is how much more Bitcoin the same dollars would buy at that trough.
- Sample: post-2014 only (the pre-$15 curiosity era is excluded), and only entries with a full two-year forward record, so “wait” and “drawdown within two years” are never truncated by the edge of the data. Figures are recomputed live every page load.