Skip to content
Doefin
All articles

Testing a difficulty-growth assumption

Higher difficulty reduces expected BTC production from the same fleet. With other assumptions unchanged, less revenue remains to recover the initial cost.

Educational article2 min readReviewed

Concept / Alternative assumptions
In this article 3 sections

Why higher difficulty reduces production

At the same fleet hashrate, higher difficulty means more work is needed to find a block. With uptime and block rewards unchanged, expected BTC production falls over the same period.

For an illustrative month, suppose the fleet is expected to produce 1 BTC at unchanged difficulty. If difficulty is 10% higher throughout that month, expected production is 1 ÷ 1.10 ≈ 0.909 BTC, about 9.1% less. Hashrate, uptime and block rewards stay the same. This compares two difficulty levels for one month; it is not a monthly growth rate.

How growth changes payback

A fixed growth rate describes a scenario over a stated period. In the fleet payback model, the rate applies each month to the previous month’s difficulty, so growth compounds. It is an assumption, not measured historical data or a dated forecast of what the network will do.

At an unchanged Bitcoin price, less expected BTC production means less expected mining revenue. The model starts below zero by the amount spent on the fleet. It adds each month’s mining revenue after power costs. Payback is the first month the balance reaches zero or more.

Keep fleet hashrate, power cost, uptime, capital cost and Bitcoin price the same when comparing difficulty paths. A later payback date under faster growth shows that lower production leaves less cash to recover the same initial cost. The gap between the results shows how much the payback estimate depends on the growth assumption. It does not show which path will occur.

What the comparison cannot decide

If no month reaches a cash balance of zero or more, the model shows no payback within the chosen period. A negative ending balance can also follow an earlier recovery if later power costs exceed revenue. Read the first payback month and the full cash-balance path together. These are simplified estimates; actual production and costs can differ.

A sensitivity comparison cannot decide whether a difficulty position suits your objectives or makes economic sense. That also depends on timing, transaction costs, available liquidity and operational constraints. This article provides no measured threshold at which an operation should hedge.

Continue from here

Apply the idea

Test your payback assumptions

Change the growth assumptions and read the resulting cash balances.

Related reading

Reading a hashrate chart

A change in estimated network hashrate can reflect the observation window. The estimate and its uncertainty need to be read together.

All articles