Best difficulty meaning (Bitaxe, NerdQAxe): all-time best, session best and what to expect
That number on the AxeOS dashboard is your machine’s record: the best hash it has ever computed, expressed as a difficulty. It measures neither your earnings nor any progress toward a block. Here is exactly what it counts, all-time best versus session best, how to reset it, the value to expect for your machine and mining time, and what pools show.
Published 2 November 2026, updated 14 November 2026 · by Pixel · 11 min read
5:09
Best difficulty is the difficulty of the best hash your machine has found. AxeOS 2.15.4 shows two: all-time best, saved in memory, and session best, which resets at every restart. A block needs the network difficulty, 134.8 T as of 14 November 2026; a Bitaxe Gamma typically reaches about 24 M in a day.
Contents 8 parts and a FAQ · 11 min read
- What does “best difficulty” mean on a Bitaxe?
- All-time best vs session best: what is the difference?
- How do you reset best difficulty?
- What best difficulty should you expect after a day, a month, a year?
- Is a best difficulty above the network difficulty a block?
- Why does the pool not show the same best as my Bitaxe?
- Is it the same number on a NerdQAxe or a NerdMiner?
- Is best difficulty good for anything?
1. What does “best difficulty” mean on a Bitaxe?
Every attempt the chip makes produces a hash A 64-character code computed from the block. Impossible to predict: you have to try.: a 256-bit number nobody can predict. Its difficulty How many attempts it takes on average to find a block. It adjusts itself about every two weeks. Difficulty explained measures how small, and therefore how rare, it is. AxeOS The open-source Bitaxe software, set from a browser: pool, frequency, voltage, fan. Update it computes it by dividing the difficulty 1 target, the easiest one Bitcoin knows, by the hash it got (calculation code). A difficulty 1 hash comes up on average roughly once every 4,294,967,296 attempts (2 to the power of 32, about 4.3 billion); a difficulty 1,000 hash a thousand times less often. So the chance that a hash reaches difficulty d is about 1 in d times 4.3 billion.
Best difficulty, or best diff, is simply the record: the difficulty of the best hash the machine has found. AxeOS shortens it with the K, M, G and T suffixes (thousand, million, billion, trillion); hover over the number to see the full value. Do not confuse it with the pool A server that machines connect to. A regular pool shares the earnings, a solo pool does not. Solo or pool? difficulty, the threshold at which a result counts as a share An attempt good enough to be counted by the pool. It proves your machine is working, even if it is not enough to find a block., or with the network difficulty, the threshold for a block. The other dashboard cards are explained in my Bitaxe troubleshooting guide, and network difficulty in mining difficulty explained.
2. All-time best vs session best: what is the difference?
The Best Difficulty card in AxeOS 2.15.4, the latest version (21 October 2026), shows two numbers (dashboard code):
- all-time best: the record since the very first start. AxeOS writes it to its settings memory (NVS), under the key
bestdiff, every time it is beaten (system.c). It therefore survives restarts, power cuts and updates. - session best: the best since the last boot. It only lives in RAM and goes back to 0 at every restart.
The Bitaxe’s small screen shows both on one line, Best: session/all-time, session first (screen.c). Since version 2.14.0 of 4 June 2026, the Scoreboard menu also lists the 20 best results with their date, saved in memory as well (release notes), and the Swarm page, which groups your machines, shows both numbers for each of them. The record has been saved since version 2.0.2 of November 2023 and session best has existed since 2.1.5 of May 2024; before 2.1.4, released the same month, the record could not go above 4.29 G (2.1.4 release notes).
Explanations online disagree on one point, and the code settles it: AxeOS counts every result the chip returns for a job still in progress, before the pool has any say. The record is updated right after the share is sent, if it is sent at all, whether or not that result reached the pool difficulty and whether the pool accepts or rejects it (asic_result_task.c). It is the best hash found, not the best one accepted. For your scripts, the /api/system/info endpoint returns the same values as bestDiff and bestSessionDiff.
3. How do you reset best difficulty?
Session best starts again from zero at every restart: the Restart button in AxeOS, or unplug and plug back in.
A Bitaxe’s all-time best has no button and no command in AxeOS 2.15.4. In the settings table, the bestdiff key has no API name, unlike the pool or the frequency, so the PATCH /api/system endpoint cannot change it (nvs_config.c). The only way to clear it is to flash the factory image with the Web Flasher, with Keep configuration unticked, which also wipes the Wi-Fi, the pool, your settings and the Scoreboard. A zero record, together with the self-test flag the factory image sets, is in fact the sign AxeOS uses to recognise a factory flash: it then runs its self-test at boot (self_test.c). The steps are in the reset part of the troubleshooting guide.
On a NerdQAxe, it is built in. Since version 1.1.1 of its firmware, released on 31 October 2026, the dashboard’s Reset Session Stats button resets shares, session best and errors; the “Also reset all-time stats (best difficulty, found blocks). This cannot be undone.” box clears the record and the block counter too (1.1.1 release notes). The same works through the API, POST /api/system/reset-stats?allTime=1, with the OTP code if it is enabled (API documentation).
Nothing forces you to do it: clearing the record changes nothing about your odds, since every attempt has the same chance as the one before, record or not.
4. What best difficulty should you expect after a day, a month, a year?
Since every hash has about 1 chance in d times 4.3 billion of reaching difficulty d, the record climbs with the number of attempts. The rule fits on one line: after H hashes, the typical best difficulty is about H divided by 4,294,967,296. A Bitaxe Gamma at 1.2 TH/s (rated figure) makes about 104 quadrillion hashes a day; divided by 4.3 billion, that gives about 24 M. Same calculation for a Thor P2 at 10 TH/s (measured at the wall, overclock Pushing the chip's frequency and voltage for more hashrate. It draws and heats noticeably more: on the Thor X1, +50% hashrate for 2.1 times the power. The review profile).
| Mining time | Bitaxe Gamma | Gamma: times below the network | Thor P2 | Thor P2: times below the network |
|---|---|---|---|---|
| 1 day | about 24 M | 5.6 million | about 201 M | 670,200 |
| 30 days | about 724 M | 186,200 | about 6.0 G | 22,300 |
| 1 year | about 8.8 G | 15,300 | about 73 G | 1,840 |
It is an order of magnitude, not a promise. By this calculation, you have about a 63% chance of beating the value in the table, about 10% of going 10 times higher and about 1% of going 100 times higher. Half of all machines beat 1.44 times that value: that is the median, the one in the troubleshooting guide’s table. The calculation holds for any SHA-256 The hash calculation Bitcoin uses, and so mining. Bitcoin Cash uses the same one: the same machines mine either. machine, whatever its software: only the number of attempts matters.
Two consequences. First, the record moves more and more slowly: to multiply it by 10, you have to mine 10 times longer, so a record stuck for weeks is nothing unusual. Second, the gap column is no coincidence: over a year, the Gamma’s gap to the network, 15,300, is exactly the number of years it needs on average to find a block, that is 1 chance in 15,300 per year (network as of 14 November 2026). The solo mining calculator runs this for your machine.
A benchmark for session best. After 24 hours without a restart, a Gamma really running at 1.2 TH/s has only about 1 chance in 22,000 of staying below a tenth of the typical value, that is 2.4 M. A lower session best after a full day is no longer bad luck: check the real hashrate Computing power: the number of attempts per second of a machine or of the whole network. The higher it is, the more tickets you play in each draw. and the error rate.
5. Is a best difficulty above the network difficulty a block?
Yes. The network required 134.8 T as of 14 November 2026: a hash at that difficulty or above makes a valid block. AxeOS runs the comparison itself on every result, against the difficulty of the block being mined: when it is reached, it counts a block and the screen shows “!!! BLOCK FOUND !!!” next to session best (system.c). The pool is the one that broadcasts the block; in solo mining, the reward goes to the address in the User field.
A real example: block 957,382, found on 10 July 2026 on public-pool.io by a machine that identified itself as a Bitaxe. Its hash starts with twenty zeros, 00000000000000000000f4f8c9…, and is worth a difficulty of about 294 T, more than twice the 133.9 T the network required that day (the block on mempool.space). On 2 November 2026, that number still topped the High Scores table on public-pool.io: that miner’s best difficulty is its block. This block and those of other small miners are listed in blocks found by solo miners.
Conversely, “coming close” pays nothing. A best of 100 T earns nothing and does not bring the next block any closer: every attempt has the same chance as the one before, and the record only says how far luck has taken you.
On Bitcoin Cash the bar is much lower: 476 G on 18 November 2026, read from my own node, about 283 times less than on Bitcoin. A Thor P2’s typical one-year best difficulty, 73 G, is then only about 6 times short (Bitcoin Cash solo mining).
6. Why does the pool not show the same best as my Bitaxe?
Because the pool does not see everything. It only receives results that reach its share difficulty, and only since your machine connected to it. AxeOS also keeps a record set on another pool, or one rejected because it arrived just after a new block. With two pools at once, each one only sees its part of the work (fallback pool and dual pool). And some pools wipe everyone’s records at each block they find.
| Software | What is counted | What is shown | Reset |
|---|---|---|---|
| AxeOS 2.15.4 (Bitaxe) | Every chip result, sent to the pool or not, accepted or not | Best Difficulty: all-time best and session best; Scoreboard of the 20 best | Session: at every restart. All-time: only through a factory flash |
| NerdQAxe firmware 1.1.1 | Every chip result, accepted or not | Best Difficulty (all-time best); best per pool (since connect) | Reset Session Stats button, with or without the record |
| NerdMiner v2 | Only shares the pool accepts | Best diff on the screen | At every restart, unless the Save mining statistics to flash memory option is ticked (off by default) |
| public-pool (public-pool.io) | Shares the pool receives from you | Best Difficulty for the address and each machine; High Scores: the top 10, with device and date, no address | Every address’s best, when the pool finds a block (code) |
| ckpool (solo.ckpool.org) | Shares the pool receives from you | bestshare and bestever, for the address and each machine | bestshare: when the pool finds a block. bestever: never |
Public-pool sums it up in a tooltip on its home page: “A submitted difficulty above the current Bitcoin network difficulty is a valid block candidate.” On solo.ckpool.org, your statistics open when you add your address to raw.stats.ckpool.org/users/, and the minimum share difficulty is 10,000.
On FindMyBlock, the solo pool I built (0% fee on Bitcoin), your address shows each machine’s best share. The home page ranks the best difficulties of the week, the month and all time, and the Leaderboard page has leagues by machine type (Bitaxe, NerdQAxe, NerdOctaxe, CPU miners) with prize challenges. Addresses there are always shortened, never shown in full. To connect: solo mining on FindMyBlock.
7. Is it the same number on a NerdQAxe or a NerdMiner?
NerdQAxe, NerdOctaxe, NerdQX: their firmware, ESP-Miner-NerdQAxePlus, is derived from ESP-Miner and counts the same way, every chip result, accepted or not, with the record saved under the same bestdiff key (version 1.1.1 code). The interface shows Best Difficulty labelled all-time best, and the best for each pool labelled since connect (interface strings). A “Best difficulty found” alert can also notify a webhook, Discord for example, at every new record.
NerdMiner v2: the best diff on its screen is only updated when the pool replies that it accepts the share (mining.cpp). So it is the best accepted share, not the best hash computed. It is only kept across a restart if the “Save mining statistics to flash memory” box is ticked in the setup, and it is not by default (storage.h). At about 24 to 250 kH/s depending on the board, that record stays millions of times below a Bitaxe’s: NerdMiner v2 setup gives its real odds, board by board.
8. Is best difficulty good for anything?
For three things, no more.
- Checking that the machine works. A session best that rises over the hours, in the order of magnitude of the table above, shows the attempts are real.
- Knowing where you stand. The network difficulty divided by your record says how far short you fell; over a year of mining, that ratio gives, give or take your luck, the order of magnitude of the number of years you would need on average for a block.
- Having fun. Solo pool leaderboards and challenges make the wait a little less quiet.
It says nothing about your earnings. In a regular pool you are paid by the number of shares, not by the record. In solo mining, only a result at network level pays, and yesterday’s record does not change tomorrow’s odds. The number that really matters in solo is your odds per year: the calculator gives them for each machine, at the current difficulty.
Frequently asked questions
My best difficulty has stopped moving: is my Bitaxe broken?
No. Each new record takes about ten times longer for a number ten times higher. Look at session best instead: after 24 hours, a Bitaxe Gamma at 1.2 TH/s almost always goes above 2.4 M, and the typical value is about 24 M.
Does an AxeOS update erase best difficulty?
No. All-time best is kept in the settings memory, under the bestdiff key, which an update from the Update page does not touch. Only flashing the factory image with Keep configuration unticked erases it, along with the Wi-Fi and the pool.
What is a good best difficulty for a Bitaxe Gamma?
By calculation, a Gamma at 1.2 TH/s typically reaches 24 M in a day, 724 M in a month and 8.8 G in a year. The rest is luck: after a year, about one machine in ten goes above 88 G, far from the 134.8 T of a block.
Why is my best difficulty lower on the pool than in AxeOS?
The pool only sees the shares you have sent it since you connected, and only part of them if you mine on two pools. Some pools, such as public-pool and solo.ckpool.org (for its bestshare number), also wipe everyone’s records at each block they find.
Are best difficulty and pool difficulty the same thing?
No. Pool difficulty is the threshold the pool sets to count a share: 1,000 suggested by default on a Gamma 601, at least 10,000 on solo.ckpool.org. Best difficulty is your best result, thousands or millions of times higher.
Can you reset a NerdQAxe’s best difficulty?
Yes, since firmware 1.1.1 of 31 October 2026: the dashboard’s Reset Session Stats button, with the Also reset all-time stats box ticked. On a Bitaxe, AxeOS 2.15.4 has no equivalent: it takes a factory flash.
Sources
- ESP-Miner (AxeOS) 2.15.4: best difficulty update, storage and block detection
- AxeOS 2.15.4 dashboard: Best Difficulty card
- AxeOS 2.15.4: every chip result counts toward the record
- NerdQAxe firmware 1.1.1 release notes, 31 October 2026
- NerdMiner v2: best difficulty updated on accepted shares
- public-pool: home page, High Scores table
- ckpool: bestshare and bestever, reset at each block
- Block 957,382 on mempool.space, 10 July 2026
A question about this guide? Ask it on the Discord, several of us answer there.
Other guides
-
Why you almost never find a block: mining difficulty explained
The zeros, the target, and why the network adjusts itself every two weeks.
2 min read · updated 14 Nov 2026 -
Bitaxe not hashing: hashrate at 0, pool unreachable, reboots, the fixes in order
Hashrate at 0, rejected shares, power fault: every AxeOS message and its fix.
15 min read · updated 14 Nov 2026 · new -
Bitcoin solo mining: the complete guide
Your real odds, the small miners who won, the pool and the settings.
11 min read · updated 14 Nov 2026 · new -
How long does it take to mine one bitcoin? The math, machine by machine
Centuries in a pool, a lottery solo: the math for each machine reviewed here.
12 min read · updated 14 Nov 2026 · new