Difficulty Adjustment Calendar — Solo Mining

In solo lottery mining, when you mine affects your odds almost as much as how much hashrate you run. Network difficulty sets how hard it is to find a block, and after a downward adjustment the same hashrate has measurably better odds for a while. This guide explains how difficulty adjusts on each SoloFury coin, how to spot a drop, and how to time a hashrate burst around one — with honest math on whether a rented burst actually pays (on average, it does not).

If you do not yet have rental capacity, read the Owned vs Rental Cost Comparison and the NiceHash Solo Mining Guide first; this guide assumes you can deploy short bursts.

Key Takeaways

• A difficulty drop raises your odds proportionally: block-finding probability per hash scales with hashrate ÷ difficulty, so a 5% lower difficulty is a 5% better chance per hash.
• BTC adjusts every ~2,016 blocks (about two weeks) in a hard step; BCH, BC2, BCH2, and XEC use a per-block DAA that drifts continuously.
• Rental bursts are negative-EV on average. Timing a drop improves your odds within that lottery — it does not make renting hashrate to solo mine profitable.
• Total hashrate-time deployed dominates. Difficulty timing is a small multiplier (roughly 5–15%) on top of consistent baseline mining, not a substitute for it.
• The next SHA-256 halvings are around April 2028, which tends to bring a stretch of downward difficulty adjustments as thin-margin miners drop off.

How do difficulty adjustments work?

Bitcoin and its derivatives target a constant average block time, so the network periodically adjusts difficulty based on how fast recent blocks were found. If blocks came too fast (hashrate rose), difficulty goes up; if too slow (hashrate left), difficulty goes down. When difficulty falls, the same hashrate finds blocks more easily — the most predictable edge a solo miner can act on.

The relationship is direct: your block-finding probability per unit time is proportional to your hashrate divided by network difficulty. So if difficulty drops 5% and you deploy hashrate before it climbs back, your odds for that window are about 5% higher. That is the entire mechanic this guide builds on.

How does each SoloFury coin adjust difficulty?

The adjustment mechanism differs by coin, and the difference shapes your timing.

BTC changes difficulty every 2,016 blocks (about 14 days). At that moment the network difficulty steps by whatever the last fortnight’s block pace requires — usually a few percent, occasionally larger. Because the timing is known in advance, you can plan around it.

BCH, BC2, BCH2, and XEC use a per-block Difficulty Adjustment Algorithm that smooths difficulty over a rolling window. Each change is small, but they happen every block, so difficulty drifts continuously as hashrate enters or leaves — you react to a trend in real time rather than waiting for a scheduled step.

Do difficulty-timed rental bursts actually pay?

This is the question to settle before spending money. The honest answer: renting hashrate to solo mine is negative-EV on average, and difficulty timing improves your odds within that lottery rather than reversing it.

Here is why. When you rent hashrate you pay roughly its fair market value (the hashprice) plus a platform fee, while the expected value of the blocks that hashrate might find is roughly that same fair value minus the pool fee. So on average a rented burst costs a little more than the rewards it can be expected to produce — you will usually spend the rental money and find nothing, occasionally hit a block. A difficulty drop tilts the odds in your favor for the window, which narrows the gap, but it rarely turns a burst genuinely profitable once fees are included.

Where do you watch for difficulty drops?

A few free tools track upcoming adjustments. For BTC, mempool.space/mining shows current difficulty, time to the next adjustment, and the estimated direction based on current block pace. For the DAA coins, SoloFury’s live stats page shows per-coin network hashrate and difficulty, and per-coin explorers (Blockchair for BCH, explorer.e.cash for XEC) show recent blocks and their difficulties. For any coin, you can set custom Telegram alerts for drops past a threshold.

The single most useful habit: open the SoloFury stats page once a day, scan the five-coin difficulty board, and note any coin that has fallen 3% or more from the previous day.

Reactive vs scheduled: the two timing strategies

Reactive (DAA coins — BCH, BC2, BCH2, XEC). Because the DAA drifts continuously, you act on current conditions: check the stats board daily at a consistent time; if a coin’s difficulty has fallen 3% or more in 24 hours, treat it as a signal; deploy a burst within the next day or two; and mine until difficulty climbs back to baseline (usually 24–72 hours). This works because the low-hashrate window that caused the drop is often still open — other miners have not reacted yet.

Scheduled (BTC). BTC’s adjustment lands on a predictable block height every ~14 days. Check mempool.space/mining for the estimated direction; if a meaningful downward step is projected, plan a 24–72 hour burst starting at the adjustment, and line up the rental ahead of time for that exact window. The biggest edge is in the first 6–12 hours, before other miners reconfigure.

Worked example: a BCH2 burst after a drop

Suppose the stats board shows BCH2 down 5% in difficulty over 18 hours.

First, confirm the drop is sustained, not a blip — check the 24-hour trend and that recent block times have been longer than target. Second, size the edge: 5% lower difficulty is about 5% better odds per hash, and a burst that is a large fraction of network hashrate concentrates that edge. Third, deploy — rent the hashrate for a fixed window and point it at BCH2’s SoloFury endpoint, remembering that BCH2 uses port 8585 and the bitcoincashii: address prefix:

Pool:    stratum+tcp://bch2.solofury.com:8585
Worker:  bitcoincashii:q...your_BCH2_address.burst_20260629
Password: x

Use your closest region by adding the eu- or asia- prefix. Fourth, monitor on the SoloFury dashboard during the burst. Fifth, iterate: extend if the drop persists, or stop once difficulty has climbed back and the window has closed. The same pattern applies to BCH, BC2, and XEC — only the port and address prefix change.

A recurring solo-mining schedule

For a disciplined routine: daily, spend a few minutes scanning the five-coin difficulty board and flag any coin down 3% or more. Weekly, review recent block activity, check the next BTC adjustment estimate, and plan any bursts. Monthly, review your overall results, recompute your effective hashrate (owned plus any rental average), and note whether a coin’s economics have shifted with price or an approaching halving. Around halvings, expect an extended run of downward adjustments and pre-budget for a few bursts over the following weeks.

When are the next halvings?

Halvings push thin-margin miners offline, which causes a sustained stretch of downward difficulty adjustments on the halved coin. The SHA-256 family is on a roughly synchronized schedule.

The weeks following a halving are the period when difficulty-drop timing has the most raw opportunity — but, again, each rented burst is still negative-EV on average, so treat it as improved odds, not free money. For context on the post-2024 environment, see the Bitcoin Halving 2024 Aftermath article.

What mistakes should you avoid?

Chasing every dip. A 1–2% wobble is noise. Wait for a 3%-or-more drop sustained over 12-plus hours before committing rental money.

Bursting on the wrong coin. If BCH2 falls 5% but BCH falls 8% and you have the scale, BCH may be the better target. Match the coin to your deployable hashrate with the Coin Selection Guide.

Bursting too small to matter. Renting 0.5 PH/s against a multi-PH/s network barely moves your odds. To shift the lottery meaningfully, the burst should be a noticeable fraction of network hashrate.

Forgetting fees. Rental platforms add fees on top of the headline rate — include roughly 3–5% effective cost when you weigh a burst.

Bursting into rising difficulty. If difficulty is trending up (miners coming online), it will be higher by the time your burst lands. Read the trend, not just the snapshot.

How do you monitor a burst in real time?

During an active burst, watch the delivered hashrate on the rental platform and confirm SoloFury’s worker stats show a matching pool-side hashrate. Keep reject and stale rates under 2%, watch that network difficulty is still in its drop window, and keep an eye on the block feed. If pool-side hashrate is well below what the platform reports (say the platform shows 5 PH/s but SoloFury sees 3.5 PH/s), you have a stale-share problem — switch to a closer SoloFury region using the eu- or asia- prefix.

The long-run view

Difficulty timing is a marginal optimization. The real predictors of solo-mining outcomes are total hashrate-time deployed, efficiency (cost per PH/s/day — see Owned vs Rental and Undervolting), coin selection matched to your hashrate (see the Coin Selection Guide), consistency, and accepting that lottery wins take time. Executed with discipline, timing adds maybe 5–15% effective edge over the long run — smaller than the gains from efficiency tuning, and far smaller than simply running more hashrate consistently.

Next Steps

• Check the SoloFury stats board daily for difficulty changes across the five coins.
• Set up rental access before you need it — see the Owned vs Rental Cost Comparison and the NiceHash Solo Mining Guide.
• Refresh the underlying math in the Solo Mining Variance article.
• Match the right coin to your hashrate scale with the Coin Selection Guide.
• Confirm AsicBoost is active (it already is on modern firmware): AsicBoost Guide.
• Verify your bursts in real time with Reading Your Worker Stats.