Mining dashboards, ASIC firmware, and solo-mining interfaces frequently display a field labeled "Best Difficulty" or "Best Share." Many new miners assume a rising number signals that a block is imminent. It does not. Best difficulty is a record of the single highest-difficulty share found or recorded during a defined tracking period. It is distinct from Bitcoin's network difficulty and does not change it, but the two can be compared to determine whether a recorded share met the network's proof-of-work threshold. Best difficulty does not accumulate toward finding a block.
This article separates three measurements that are often confused on mining dashboards: best difficulty, pool share difficulty, and Bitcoin's network difficulty. Understanding how they differ is necessary to read any pool or solo-mining dashboard correctly.
Read best-share difficulty
Most pool accounts, ASIC web interfaces, and solo-mining dashboards report a "best share" or "best difficulty" value for each worker. This number represents the highest-difficulty share found during the dashboard's stated tracking window—commonly since the device last restarted, since a worker was created, or since a solo-mining session began.
The scope is implementation-specific. An ASIC's local display may reset its best-share counter on reboot. A pool account page may track best share per worker, per account, or across a longer retained history. Braiins Academy's documentation on solo mining describes best share as "the highest-difficulty share found during [a] mining session," which illustrates one common scope among several possible implementations (Braiins Academy). Readers should check the exact label and time window shown on their own dashboard rather than assume a universal definition.
Best-difficulty values are usually abbreviated with SI-style suffixes such as M, G, and T—for example, 1G or 1T. These suffixes describe the numerical difficulty value of that single share, not a hashrate. A best share of 1T does not mean the device is hashing at 1 TH/s; the two figures are unrelated units describing different things.
Separate three difficulty measures
Three distinct values appear in mining contexts, and conflating them is the most common source of confusion.
| Measure | What it describes | Scope |
|---|---|---|
| Network difficulty | A relative measure of how hard it is to find a Bitcoin block, expressed against a baseline difficulty of 1 | Bitcoin network consensus |
| Pool share difficulty | The difficulty threshold a pool assigns so a worker can submit frequent, verifiable proof of work | A pool connection or worker |
| Best difficulty (best share) | The highest-difficulty share recorded during a stated period | A device, worker, account, or session |
Bitcoin's consensus rule does not reference "difficulty" directly; it references a target. A valid block header must hash to a value at or below the current network target. Difficulty is simply a human-readable way of expressing how far that target sits below the baseline target used at difficulty 1 (Bitcoin Developer Glossary). A lower numeric target is harder to satisfy, which corresponds to higher difficulty—these two figures move in opposite directions.
Pool share difficulty works on the same scale but is set far easier than network difficulty. Expressed as difficulty rather than target, the pool's share difficulty is lower than network difficulty, even though its numeric target value is higher. Pools use these frequent, easier shares to estimate a worker's contributed hashing effort and to calculate rewards under whatever payout method the pool uses; shares are an accounting mechanism, not a sequence of attempts that add up toward a block (Bitcoin Developer Documentation: Mining).
For example, suppose the assigned share difficulty is one-hundredth of network difficulty and both remain fixed. The same worker would find about 100 shares meeting the assigned threshold, on average, for each result that also meets the network's proof-of-work threshold. This does not mean the worker submits 100 shares every time the network finds a block, nor does the hundredth share guarantee a block.
Solo-mining services can also use an easier share target to monitor hashing activity and provide feedback. Solo CKPool, for example, documents an adjustable share difficulty used for this purpose (Solo CKPool FAQ). A solo dashboard can compare best-share difficulty with network difficulty while still using lower-difficulty shares for operational statistics. Whether rewards are shared and whether easier shares are tracked are separate questions.
Compare to the network target
Because both a best share and the network's required threshold are expressed on the same difficulty scale, they can be compared directly:
Best-share percentage = (best-share difficulty ÷ network difficulty at the time of comparison) × 100
For illustration, assume a network difficulty of 132.72T. This is a hypothetical example, not a claim about the current network difficulty. Bitcoin's network difficulty adjusts every 2,016 blocks—about every two weeks—as the protocol retargets to keep the average block interval near 10 minutes.
Using that assumed difficulty, consider a few hypothetical best-share values:
| Best share | Percentage of 132.72T network difficulty | Interpretation |
|---|---|---|
| 1G | ≈ 0.00075% | A valid pool share if it met the assigned share target, far below block difficulty |
| 1T | ≈ 0.753% | A comparatively strong share, still far from a block |
| 10T | ≈ 7.53% | A notable share, but not a block |
| ≥132.72T | ≥ 100% | Meets the network threshold; if the block is otherwise valid, it is a block candidate |
The 10T example is about 7.53% of the assumed network difficulty. It does not mean the worker is "7.53% of the way" toward finding a block.
This comparison only describes how one past hash measured against the network threshold at a given moment. Because network difficulty changes over time, a historical best share should ideally be compared against the network difficulty in effect when that share was found, where that timestamp is available, rather than against today's figure.
Why a record is not a countdown
Each hash a miner computes is an independent, memoryless attempt to find a value at or below the required target. Finding one unusually strong share does not change the probability that the next hash will succeed, in the same way that one favorable coin flip does not change the odds of the next flip.
This matters because a rising best-difficulty figure can look like progress toward a goal. It is not. It is simply the record of the single best outcome observed so far. A worker's chance of finding a block over a given period depends on the number of hash attempts it completes and the network difficulty applicable to those attempts. Sustained hashrate and mining duration determine how many attempts it can make; a past best share does not improve the success probability of subsequent attempts (Braiins Academy).
As a rough sense of scale, the expected number of hash attempts needed to reach a given difficulty value D is approximately D × 2^32 (roughly 4.295 billion hashes per unit of difficulty). This is a long-run statistical average, not a guarantee for any individual device or time window; actual results vary considerably around that average because each attempt is independent and probabilistic. Dividing that expected hash count by a worker's hashrate gives an estimate of average time to reach a target difficulty, assuming that difficulty and hashrate remain constant—again, an average, not a prediction for a specific miner or a specific block.
When reviewing mining logs or dashboards, best difficulty is most useful alongside other operational data—hashrate, uptime, and rejected-share rate—rather than as a standalone indicator of performance or payout. It answers one narrow question: what is the hardest single share recorded in the period shown? Hashrate, pool-estimated contribution, and realized rewards each answer different questions and should be read from their own respective metrics.
FAQ
Is a high best-difficulty share a sign that a block is close?
No. Each hash attempt is independent, so a high best share reflects one past result and does not change the probability of finding a block on subsequent attempts.
Does best difficulty measure my hashrate?
No. Best difficulty describes the difficulty level of a single share; hashrate is a separate measurement of computational speed, typically expressed in hashes per second (e.g., TH/s). The two use different units and should not be inferred from one another.
Why is pool share difficulty lower than network difficulty?
Pools assign an easier share target so miners can submit frequent, verifiable proof of work. This lets the pool estimate each worker's contribution and calculate rewards without requiring every submission to meet Bitcoin's much harder block threshold.
Does best difficulty reset over time?
It depends on the dashboard or device. Some reset the figure on restart; others track it per worker, per account, or across a longer retained period. Check the specific label and time window shown on the interface being used.
Can a share with high best difficulty become a Bitcoin block?
Yes, if its difficulty meets or exceeds the network difficulty applicable when it is found and the resulting block is otherwise valid and timely. Most recorded best shares fall well below that threshold.