Skip to content
Doefin

Tool guide

How difficulty changes your expected BTC production

Compare expected BTC production under your own difficulty assumptions. Costs and contract payouts need separate calculations.

Doefin Research ·

At the same hashrate and over the same period, higher difficulty reduces expected BTC production, all else equal. This calculator compares constant-difficulty scenarios. The spread between two scenarios is not a financial loss, a forecast, a contract payout or a position size.

Use this if you mine BTC with your own machines and want to compare difficulty scenarios within the calculator’s input range. Fleet size alone does not decide whether a production change matters to your business; your income and obligations matter too. Hosting businesses can model machines they own, but need another model for fee-only income. Holding or selling mined BTC does not change expected production. Fixed-output commitments and sold hashrate need separate analysis.

How to use it

  1. Enter your fleet’s expected average hashrate in EH/s. Divide TH/s by 1,000,000. If the pool average includes downtime, do not deduct it again.
  2. Use How far ahead to choose the number of modelled epochs. Each represents 2,016 target block intervals, about two weeks. Actual epoch dates can differ.
  3. Check a trusted source and enter its value in Starting difficulty. Older calculator views also accept ?diffT= in the address. The default 127.48T is illustrative.
  4. Choose an easier and a harder difficulty for the whole period. The defaults −2.4% and +7.0% are illustrative assumptions, not forecasts or a confidence interval.
  5. Enter Expected fees as average transaction fees per block. The model adds the fixed 3.125 BTC subsidy and holds both constant. It excludes pool fees and cannot model a subsidy change.
  6. Compare expected production at unchanged difficulty with each scenario. The harder case versus the starting case shows lower production, not a cash-flow loss.
  7. Bitcoin price converts the scenario spread to a USD illustration; it changes no BTC result. Copy the URL to save your inputs. Anyone with the link can read them.

What each setting means

Every number the calculator asks for, what it is, and where to find yours.

Hashrate

Expected average fleet hashrate in EH/s. One EH/s is 1,000,000 TH/s.

Where to find it: Use pool records and adjust only for changes not already represented in that average, such as planned additions or future downtime.

Input limits and sample: The input accepts 0.01–30 EH/s. The illustrative default is 1 EH/s. These are input limits, not eligibility rules.

How far ahead

The number of approximately two-week modelled epochs.

Where to find it: Choose the time window you want to compare.

Input limits and sample: The input accepts 1–13 modelled epochs, approximately 2–26 weeks. The illustrative default is four epochs, about eight weeks.

Expected fees

Average transaction fees in BTC per block, added to the fixed 3.125 BTC subsidy.

Where to find it: Pool records or block data can inform an assumption. No future fee level is supplied by this page.

Input limits and sample: The input accepts 0–0.5 BTC per block. The illustrative default is 0.05 BTC per block.

Bitcoin price

Your chosen USD price for converting the difference between the two production scenarios. It stays constant.

Where to find it: Choose and record your own scenario price. This page does not supply a live price or predict a price path.

Input limits and sample: The input accepts $20,000–$200,000 per BTC. The illustrative default is $64,000 per BTC. Slider steps are $1,000.

Difficulty change · easier case

A lower constant-difficulty scenario, applied from the start of the modelled horizon.

Where to find it: Choose a change to test. Historical data or a separately sourced forecast can help you choose, but neither guarantees what will happen.

Input limits and sample: The input accepts 0–15% lower difficulty. The illustrative default is 2.4% lower, not a forecast.

Difficulty change · harder case

A higher constant-difficulty scenario, applied from the start of the modelled horizon.

Where to find it: Choose a change for the whole period. Extending How far ahead does not automatically widen this scenario.

Input limits and sample: The input accepts 0–15% higher difficulty. The illustrative default is 7% higher. The limit does not cover every possible future change.

Starting difficulty

The starting network difficulty in trillions. The model uses it to estimate network hashrate at the target block interval.

Where to find it: Check current difficulty with an independently selected block data source.

Input limits and sample: The input accepts 1T–1,000T. The illustrative default is 127.48T, not current network difficulty.

Reading the answer

Production difference

Expected production in the easier case minus expected production in the harder case. With the sample inputs, the difference is about 2.525 BTC.

So: The difference includes both higher production in the easier case and lower production in the harder case. It is not the shortfall against unchanged difficulty.

Harder case vs starting case

The harder scenario minus production at unchanged starting difficulty. With sample inputs the difference is about −1.836 BTC.

So: This estimated production difference is before pool fees and operating costs. It does not tell you how much to reserve for bills or whether to trade.

Production at each difficulty

At 1 EH/s, four modelled epochs, 127.48T and 0.05 BTC fees per block: approximately 28.057 BTC unchanged, 28.747 BTC at −2.4% and 26.222 BTC at +7%.

So: These values use constant hashrate, constant rewards and a whole-horizon difficulty change. A gradual path produces different results.

Network hashrate

The network hashrate implied by difficulty at ten-minute blocks: difficulty × 2³² ÷ 600 hashes per second, about 912.54 EH/s at the sample baseline. It is not a live measurement of mining activity.

So: Compare with pool records using consistent periods and fee treatment.

An illustrative 0.80 EH/s fleet over four modelled epochs

Use 0.80 EH/s, four epochs, 127.48T, 0.05 BTC fees per block, −2.4% and +7.0% scenarios, and a $64,000 conversion price. These are educational inputs, not an operational forecast.

  1. At unchanged difficulty, modelled production is 22.446 BTC.
  2. At 2.4% lower difficulty, it is 22.998 BTC. At 7.0% higher difficulty, it is 20.977 BTC.
  3. The spread is 2.020 BTC, approximately $129,303 at the assumed price. It is the difference between the two scenarios, not a loss.
  4. The harder scenario produces 1.468 BTC less than the unchanged baseline, approximately $94,000 at the assumed price. No power, hosting, financing, tax or trading cost is included.

This comparison shows how difficulty alone changes expected production under the stated assumptions. To decide what it means for your business or whether to act, you need information beyond this calculator.

Mistakes people make

  • Treating the scenario spread as a loss. Compare the harder scenario with unchanged difficulty when asking about lower production.
  • Treating sample inputs as a forecast or the harder slider as a guaranteed worst possible outcome. The supported slider range is finite.
  • Assuming the model follows difficulty changes over time. It applies each scenario difficulty for the entire horizon.
  • Deducting downtime twice when expected average hashrate already includes those lost hours.

What it does not tell you

  • The calculator models expected BTC production, not profit or cash flow. It excludes power, hosting, hardware, financing, tax and pool fees.
  • The defaults are illustrative. The calculator does not supply live network difficulty or a forecast.
  • The model fixes the subsidy at 3.125 BTC and assumes constant hashrate, average fees and target block timing. It does not model subsidy changes or a changing difficulty path.
  • A difficulty contract observes one specified block and pays a binary amount in its collateral currency. That payout can be zero even when your production is lower; a winning payout may over- or under-offset production changes. Position cost and trading fees are outside this calculator, and you can lose the full amount paid for a position.
  • This page contains no executable price, liquidity, contract sizing or hedge-economics test. Fleet size alone cannot establish whether a contract would cover its costs.

Continue exploring

The research and reference library are open to read. Preview research email preferences and report delivery; this demo sends no emails and saves no personal details.

Last reviewed . Figures marked illustrative are placeholders, not live data.