Difficulty Pressure (hafeer)
What it measures
Every proof-of-work chain aims at a target block time. When blocks run slower than target, the protocol will push difficulty down; faster, and it pushes difficulty up. Difficulty Pressure compresses the last 2,016 blocks of pace into one bounded number:
- +1.0 — blocks running far slower than target: strong downward pressure on difficulty (relief for surviving miners, often after hashrate leaves the network)
- 0.0 — pace exactly on target: equilibrium, no pressure either way
- −1.0 — blocks far faster than target: strong upward pressure (a headwind — new hashrate is joining faster than difficulty has caught up)
It is the same physical axis as the dashboard's next-adjustment estimate, mapped onto a bounded energy scale so one number is comparable across chains and across time.
The exact recipe
ratio = elapsed_seconds(last 2016 blocks) / (2015 × target_seconds)
(guard: if ratio < 0.1 or > 3.0 → value is 0; protects against bad timestamps)
g = √(2 × ratio), clamped to the interval [0.542826…, 3.684419…]
(the positive root of x² + πx − 2 = 0 and its Vieta partner 2/root;
the two bounds multiply to exactly 2)
E = (g² − 2) / (π × g) → bounded in [−1, +1]
Effective range note: with the bad-data guard at ratio 3.0, the largest positive reading the instrument can publish is ≈ +0.52 (g = √6); the −1.0 end is reachable (ratios near 0.1 clamp to the lower bound). Displayed values therefore live in [−1.0, ≈+0.52]; the ±1.0 scale above defines the units, not the attainable extremes.
| chain | window | target | note |
|---|---|---|---|
| BTC | 2,016 blocks | 600 s | the protocol's own retarget epoch |
| LTC | 2,016 blocks | 150 s | the protocol's own retarget epoch |
| DOGE | 2,016 blocks | 60 s | chosen window — DigiShield retargets every block, so DOGE has no protocol epoch; we state the window rather than imply one |
Published thresholds
The dashboard shows the raw number (rendered as ≈0 below 0.05). Wherever words appear for this signal — here or there — these are the only words, and these are the cutoffs:
| |E| | label |
|---|---|
| < 0.05 | at equilibrium |
| 0.05 – 0.25 | mild pressure |
| > 0.25 | strong pressure |
Lineage & validation status — plainly
The bounded energy transform E(g) comes from a proprietary engine family developed on Monero and migrated to Bitcoin; the hafeer measurement itself was introduced on Bitcoin in April 2026 inside our trading pipeline, where it has run live since. The transform and every constant published here are identical to that deployed engine. One input differs, and we state it plainly: the deployed engine only ever saw a 300-block buffer, while this page feeds the full 2,016-block window the specification calls for — that windowing is new as of this publication and has no separate live track record of its own.
What is verified: the math is machine-checked on every pipeline start — root identities of x² + πx − 2 = 0 to 1e-10, E(target pace) = 0, output bounds [−1, +1] — and the pipeline refuses to publish if any check fails. Underlying pace data is spot-checked against independent explorers: LTC on 2026-09-18 — difficulty 0.0000% difference, hashrate within 0.93%. (DOGE compares a day-average against snapshot-based references on a per-block-retarget chain, so we publish our own value with its recipe rather than claim a same-number match; BTC receipts follow now that our node is at the chain tip, reached 2026-09-27.)
What is not claimed: hafeer has not been independently backtested as a predictor of price or profitability, and we don't present it as one. It is a measurement of protocol state — like a tachometer, not a route planner. If we ever publish predictive claims for it, the backtest will be published first.