The Dashboard The Gallery Calculators About
indicates pages with interactive tools
 trend the Dashboard → the Power Law →

The Bitcoin Rundown

Bitcoin’s position in its long-run channel — and what a position like it has meant for the question you came with.
Today’s price
Trend price today?What the long-run power law puts bitcoin at today. It moves slowly and with time, not with the market — it is the yardstick, not a target.
Position?Today’s price as a multiple of that trend price, and the gap between them. Everything on this page is read from this one number.
Times at the floor since 2014?An approach: an episode in which price came within 1% of the 0.42× floor, with a gap of more than about 100 days starting a new one. Being below trend is ordinary — most of the record. Reaching the floor is not. Closes below the floor are a separate, rarer event, tracked on The Bitcoin Floor, whose definition this is.

Everything below is conditional on the power law holding · examined on the Power Law page → ·

The briefing

Your situation, and your question

Two numbers and one question. They stay in your browser, they change which record is read and how it is read, and they never turn a record into advice.

Stays on this page — never stored or sent.

Everything you enter stays in your browser — never stored on a server, never sent. The year and the income are remembered on this device only while their own toggle is on; your stack has no toggle and is forgotten when you close the tab.

What brought you here?

This filters which modules render. It changes no figure and issues no recommendation.

Where this position sits · shown for every question

When has price been here before?

What return does buying here imply, if the trend holds?

10 years

Both figures are conditional arithmetic on the model, not a forecast. Neither says the floor will be reached. What would break this →

The Bitcoin Hurdle Rate →

Sources. The shared Power Law module at today’s live price. The Bitcoin Hurdle Rate prints the trend bar at each horizon in its default view, so that figure reproduces there exactly. It draws the floor case as a curve rather than printing it — read it off that chart at the same horizon. The rate from today’s actual position is the third line on that page, and it is the same arithmetic as the reversion module in the Deploy cluster, which is why it is published once rather than in both places.

There is capital to deploy. Has deploying at a position like this one beaten waiting for a lower entry?

Historical, at this position — not a prediction. The record contains no instance of the floor giving way: a limit of the sample, not evidence about the world.

Wait, or Deploy Now? →

Sources. The shared channel-entry engine — the same one Wait, or Deploy Now? and How Much Cash? publish from. Matched on today’s position with the sub-floor clamp that engine applies before matching, a two-year forward window, measured in coins acquired. It excludes everything before 2014 as bitcoin’s pre-exchange era. The counter-case, the sensitivity and the position slider are at the destination.

All at once, or ladder in — and does starting a DCA now change that?

Historical, at this position — not a prediction. No engine conditions a DCA’s start date on position; a ladder begun today is the closest available comparison.

Lump Sum or Ladder In →

Sources. The shared ladder-advantage module, the same one Lump Sum or Ladder In draws its curve from, at that page’s own defaults — the post-2020 era and a ~1-year ladder — so these figures are what that page shows on arrival. Widen the era there and they move. Read on the unclamped channel position, because that page does not clamp. Its neighbourhood is a fixed ±0.075 of position and does not widen when thin, unlike the pooled engine above — two modules, two neighbourhoods, said here rather than assumed.

What is the discount worth, if it reverts?

A conditional projection, not a forecast: the reverting path is illustrative, with the baseline and never-reverts paths beside it. What would break this →

Discount, or Premium? →

Sources. The shared Power Law module at today’s live price — the reverting rate is the trend price at your chosen date over today’s price, annualised; the baseline is the trend’s own slope over the same window. Discount, or Premium? publishes both, and owns the full chart, the dollar framing and the caveats.

Selling here, meaning to rebuy lower — what has that done?

Historical, at this position — not a prediction. Raising cash for a bill or a deadline is a different question, and the record has no view on it.

How Much Cash? →

Sources. The shared channel-entry engine at its default rebuy rule — the first lower entry within two years, which is where How Much Cash? sits with its own slider untouched. Matched on today’s clamped position, 2014 onward, measured in coins. The win rate is the figure Wait, or Deploy Now? prints as its headline for the same position. The median coins-back figure is the engine’s own, before the share of stack sold and the tax rate are applied — How Much Cash applies both and prints a lower number at its defaults, which is the point of going there.

If you run bands, how far are they from triggering here?

Where price sits now against the tool’s own standard settings — not a prediction, and not your bands unless you have set them there.

Disciplined Rebalancing →

Sources. Disciplined Rebalancing’s standard preset — sell at the 80th percentile of the historical price-to-trend ratio, rebuy at the 50th — computed from the same record that page ranks, and priced against today’s trend. Move either slider there and these lines move with it. Nothing here reads or changes what you have set on that page.

What stack would your target need, read from here?

A conditional projection, not a forecast: each figure names the case it assumes, with the alternative beside it. This models bitcoin alone; your other assets and income sit outside it. What would break this →

Bitcoin Escape Velocity →

Sources. The shared retirement engine’s own threshold solver — the smallest stack whose real value stops falling for every year of the plan. Bitcoin Escape Velocity is where it is published; the retirement flagship does not compute it. To reproduce these figures there, set the same year and income and switch the price basis to “today’s gap to trend persists” for the first, or set the site-wide growth model to the floor case for the second. The horizon is fixed here at 30 years and is adjustable there.

What have drawdowns from this zone looked like?

Historical, at this position — not a prediction. Shallow falls from here are close to arithmetic, so long as the floor holds: an entry near the floor has less room beneath it than one near the trend line. What would break this →

The Retirement Stress Test →

Sources. The shared channel-entry engine — drawdown frequency, median depth and the never-fell share over a two-year forward window, matched on today’s clamped position, 2014 onward. A “drawdown” here is a fall of 20% or more, and the window is two years; both are the engine’s own constants. The Stress Test is a what-if tool for a fall of a size you choose, not the source of these figures and not where they are checked.

What is not here yet

Modules appear when an engine exists to compute them from and their figures reproduce on the page that owns them. These do not exist yet, and a module that guessed would be worse than no module. The item bearing on your chosen question is marked.

  • Whether to start a DCA now, on its own terms. What Daily Conviction Bought runs a DCA from a start date you choose, but nothing in it varies with where price sits in the channel. The ladder module above is the closest available comparison, not a substitute for one.
  • What rebalancing from this position has historically done. The bands module above is a now-read: it says where the lines sit today. Asking whether triggering here has paid needs the protocol run from each historical entry in the zone, which no engine does.
  • Sequence risk conditioned on this position. The threshold module asks what a plan needs; it does not ask what starting a withdrawal plan from this position has meant for the order returns arrived in. That needs the withdrawal loop run from each historical entry in the zone — a real piece of work, and the most valuable of these three.
  • Selling for a reason that is not timing. Need, risk reduction and sticking to a plan are legitimate and none of them is a mistake. The record has no view on any of them, and a module built from it would be answering a question nobody asked.

A map, growing — never a matrix, padded.

What would break this

This is the most model-dependent page on the site. Every figure above rests on one model, and there is no second method here quietly agreeing with the first — if the power law is not a real long-run structure, the position this page is organised around is not a position, and the visits it counts are not visits.

The floor is the model’s own tripwire. The Bitcoin Floor states the criterion in advance — how far below, for how long — and reports against it. That criterion is the one this page would fail with, and it is stated there rather than restated here so it has one home rather than two wordings.

The unsampled scenario is the important one. The record behind this page contains no instance of the floor giving way and staying gone, so nothing above is evidence that it cannot. The shared engine goes further and clamps sub-floor positions before matching entries at all, which means a sustained break is not merely rare in this data — it is structurally absent from it. An absence in a sample is not a property of the world, and breaks run in both directions.

Common questions

What happens to what I enter here?

Everything you enter stays in your browser. Nothing is sent to a server, nothing goes into an analytics event, and there is no account. The retirement year, the target income and your chosen question can each be remembered on this device if you switch that field’s toggle on — they are written to one browser storage key and to nowhere else, and “clear everything” removes that key outright rather than blanking it. Your stack is treated differently and more strictly: it has no toggle at all. It lives in the page for as long as the tab is open and is forgotten when you close it — never stored, never put in the link, never sent. That is the same rule every other page on this site that asks for a stack already follows.

Why does the page ask what I’m trying to do?

To decide what to show you, and for nothing else. Choosing a question filters which modules render; it does not change a single number, and it does not produce a recommendation. Every module computes the same figures whichever question is selected — picking one is you saying what you came for, not the page issuing an answer. If you would rather see only the position read, “just looking” shows the always-on modules and nothing else.

Is this page telling me what to do?

No. Each module shows what the historical record says about a decision from a position like today’s — how often each path worked out, by how much, and the times it didn’t. Which path fits a particular situation, horizon and tolerance is the reader’s to decide, and the tool linked from each module exists so it can be tested with real numbers. The inputs personalise which record is shown and the arithmetic that reads from it; they never turn a record into advice.

Why is the same figure not repeated from the pages this links to?

Because every element on this site has exactly one canonical home, and this page is not the home of any of them. It owns the composition — your position, your situation, your question — and each module carries a compact echo plus a route. The full counter-case, the sensitivity, the controls and the sources live at the destination. A briefing is assembled from the file room and arranged for the person reading it; it never pretends to be the file room.

How is this different from technical analysis?

Technical analysis reads price against its own recent pattern. This page measures price against an independent yardstick — the long-run power law trend — the way equity investors measure price against earnings. The yardstick moves slowly, is fitted on the whole record, and is falsifiable: the Power Law page states what would break it. Whether that yardstick deserves trust is examined there, not assumed here.

Some modules show one or two past cases. Why not a median?

Because a median over two cases is a statistic with the honesty removed. Where the record behind a module holds fewer than three independent episodes, the module names them individually and says so rather than publishing a distribution that would look far more solid than the evidence under it. Where a figure is pooled across many matched samples it is labelled as pooled, and the two are never spliced together — that would produce numbers which are individually defensible and collectively incoherent.

Why does the page say it has nothing for me if I reject the power law?

Because it is accurate rather than dismissive. Every figure here is conditional on the channel being a real long-run structure. A reader who has examined that claim and rejected it is not being told they are wrong — they are being told this particular map is drawn on a projection they do not accept, which makes it the wrong map for them. That is the page working as designed. The examination itself lives on the Power Law page.

Why is there nothing here about borrowing against bitcoin?

Because timing, leverage and individual circumstance together make the most dangerous combination on the site, and this page deliberately does not condition borrowing on channel position. Bitcoin as Collateral covers what borrowing against a stack involves, on its own terms and without a position attached. That separation is a design decision, not an oversight.

Get the essays and tool updates

A few emails a month when something new ships — an essay, a new tool, a meaningful update. No funnel, nothing for sale, unsubscribe anytime.

Subscribe on Substack
Share this page
X LinkedIn Facebook