Market & hashprice

Hashrate Index September 26 snapshot highlights spot hashprice and the forward curve miners must read separately

Source report: 2026-09-26 · Editorial analysis published: 2026-09-28

Hashrate Index dated its live Bitcoin Hashprice Index and forward-curve view September 26. The dashboard distinguishes spot revenue per PH/s/day from contracts trading at premiums or discounts, giving operators a way to compare today’s mining income with market expectations without treating the curve as a forecast guarantee.

Analysis and practical implications

This section is our analysis and illustrative calculations, separate from the source report.

The dashboard separates spot and forward hashprice

Hashrate Index’s Bitcoin Compute Data page was dated September 26, 2026 and presents spot hashprice alongside a live forward curve. Spot hashprice estimates current miner revenue per unit of hashrate, while a forward contract fixes or references revenue for a future delivery period. The page expresses forward prices as a premium or discount to spot. These are related measures, but they answer different questions: one describes current economics and the other describes terms available in a market for future hashrate.

Hashprice combines four moving inputs

The index methodology explains that hashprice depends on Bitcoin price, network difficulty, transaction fees and the block subsidy. Bitcoin price and fees raise revenue when other inputs stay constant, while higher difficulty reduces the expected reward for each unit of hashrate. A miner cannot manage all four variables, but it can manage power cost, efficiency, uptime and treasury policy. Operators should avoid attributing a daily hashprice move to one cause until they compare the underlying price, difficulty and fee data.

The 144-block average smooths short noise

Luxor’s index uses a trailing 144-block simple moving average to account for transaction fees. Roughly one day of blocks reduces the effect of an unusually large fee in a single block, but the measurement still changes continuously. A farm invoice or daily pool payout may differ because of pool method, luck, stale shares and timing. The index is a benchmark for comparable economics, not a promise that every PH/s will receive the same amount. Reconcile it with actual accepted shares and pool statements.

Contango and backwardation need careful language

The dashboard calls a future price above spot contango and a future price below spot backwardation. A premium does not prove that miners will earn more later, and a discount does not guarantee deterioration. The curve reflects traded or indicated terms, liquidity, risk preference and expectations embedded in the market. Before using it for a budget, record contract size, settlement formula, collateral, counterparty, fees and bid-ask spread. A headline percentage without those details is not an executable hedge.

A forward contract changes risk, not machine output

Selling future hashrate revenue can reduce uncertainty in fiat cash flow, but it does not improve ASIC efficiency or prevent downtime. The operator still has to deliver the contracted exposure or settle according to the agreement. If a site curtails, loses connectivity or suffers hardware failure, the mining operation and hedge can move differently. Risk limits should compare expected physical production with contracted volume, leaving a buffer for outages and seasonal power events instead of hedging nameplate hashrate at one hundred percent.

Compare the curve with the power contract

A miner’s most important spread is revenue per unit of energy minus the marginal cost of that energy. Convert hashprice through measured joules per terahash and include facility overhead, pool fees and firmware charges. Then compare future revenue terms with fixed, indexed or interruptible power costs for the same delivery months. A forward hashprice can reduce one side of the margin while leaving electricity exposed. The hedge decision should consider both legs and the collateral needed when markets move.

Fleet efficiency changes the meaning of one index

Two farms observing the same hashprice can have very different outcomes because their ASICs consume different energy for each terahash. Newer machines may continue profitably through a decline that forces older units to curtail. Mixed fleets should calculate break-even hashprice by model, power profile and cooling overhead. Managers can then map the forward curve to the portion of the fleet likely to run in each month rather than applying one corporate average to every rack.

Use dated snapshots for audit and planning

Because the dashboard is live, an operator should save the observation time, units, spot value and each contract month used in a decision. Later comparisons must use the same convention and avoid mixing USD per PH/s/day with BTC-denominated values. Preserve the associated Bitcoin price, difficulty and fee assumptions. A dated internal record makes it possible to explain why a hedge, hardware purchase or curtailment rule looked reasonable with the information available on September 26.

The practical use is disciplined comparison

The September 26 view is most useful as a common reference for current revenue and market-implied future terms. It cannot remove basis risk, guarantee future difficulty or replace a site budget. Miners should combine the index with pool-side production, metered power, contract terms and fleet efficiency, then stress-test price, difficulty, fees and outages. The goal is not to predict one exact hashprice, but to know how much margin remains across plausible outcomes and what action follows each threshold.

Source: Hashrate Index ↗