Is a Bitaxe a Solo Miner? No — Solo Is a Setting
The devices are marketed as solo miners, which has convinced a lot of people that solo is something the hardware does. It is not. It is one text field, changeable in thirty seconds, and the same board can mine solo this morning and on a shared pool tonight. Here is what actually changes.
A Bitaxe is not a solo miner. It is a miner. Solo versus pool is one text field in the web interface, changeable in about thirty seconds, and the same board can mine solo this morning and on a shared pool tonight. The marketing name created a hardware category that does not technically exist.
The question comes up constantly, and it was put well on a German Bitcoin forum: they are called solo miners, but pool mining should be possible with them too, right? Yes. And understanding why clears up most of the confusion around what these devices actually are.
Key takeaways
- Solo and pool are the same hardware. Same chip, same firmware, same hashrate, same wattage, same noise. Only the destination changes.
- Three fields change: stratum host, port, and the username, which is your payout address on a solo pool and an account name on a shared one.
- Expected value is nearly identical. At 1.2 TH/s a pool grosses about $14.07 a year before fees, against a solo expectation of about $13.90. The difference is the shape, not the size.
- Minimum payout thresholds are the real obstacle to pool mining a small board — roughly 4.5 years to reach a common 0.001 BTC minimum. Lightning payouts remove it entirely.
- Your device shipped pointing somewhere. Preset credentials vary by manufacturer, and some default pools require a registered account rather than a bare address.
- The word “solo” has three competing meanings, which is why people talking about it often disagree without noticing.
What changes, and what does not
Switching between solo and pool mining touches nothing physical. Here is the honest split.
| Changes | Stays exactly the same |
|---|---|
| Stratum host and port | Hashrate |
| What goes in the username field | Power draw and electricity cost |
| Who is credited if a block is found | Temperature, fan speed, noise |
| How often you get paid, and how much | The ASIC and its firmware |
| Whether a third party holds a balance for you | Your odds per hash |
That last row on the right is worth stating plainly, because it is the most common misconception underneath the first one. Pointing at a solo pool does not improve your chance of finding a block. Every hash has the same probability of being the winning one regardless of where the work came from. What solo changes is what happens if it lands: the whole reward instead of a proportional share.
The three meanings of “solo”
Here is where the confusion actually lives, and it is not the reader’s fault. The word is used for three different things, sometimes on the same website.
| Definition | What it emphasises | Who uses it this way |
|---|---|---|
| 1. You keep the whole block | Payout structure | Most solo pools, most coverage |
| 2. You run your own node and build your own templates | Infrastructure and sovereignty | Node-focused vendors, the DATUM community |
| 3. A small device pointed at a solo pool | Scale and variance | Often called “lottery mining” instead |
One major retailer’s FAQ uses definition 2 and explicitly contrasts it with what it calls lottery mining, while another page on the same site describes a solo pool as infrastructure that lets individuals compete for the full block reward, which is definition 1. Neither is wrong. They are answering different questions with the same word.
The practical consequence: when someone tells you a Bitaxe “is not really solo mining”, ask which definition they mean. If they mean definition 2, they are right and it is a fair point about template construction, which our architectures piece covers in detail. If they mean definition 1, they are simply wrong.
The thing to check before anything else
This is the section with real money attached.
Devices do not arrive blank. They ship with preset pool credentials, and those defaults vary by manufacturer. If you never changed the username field, a block found by your device would credit whatever address or account was in there when it left the factory.
There is a second version of this trap. Some devices ship pointing at a pool that requires a registered account rather than a bare Bitcoin address — entering your address alone in the username field will not work, and depending on the pool your shares may simply be rejected or credited to nobody useful.
The check takes fifteen seconds:
- Open the AxeOS dashboard at your device’s IP address.
- Go to Pool Settings.
- Read the Stratum User field. On a solo pool it should be an on-chain address you control. Not a Lightning address, which will not work here.
- Read the Fallback Stratum User field too. It is separate, and it is the one people forget.
If either field contains something you did not put there, change it now. Our Bitaxe setup guide walks the full configuration, and the troubleshooting guide covers what a misconfigured pool connection looks like in the logs.
Same device, two return profiles
Since the hardware is identical, the choice is purely about how you want the same expected value delivered.
| 1.2 TH/s Bitaxe Gamma | Shared pool | Solo |
|---|---|---|
| Typical payout | ~$0.039 per day, gross | Nothing, almost always |
| Annual figure | ~$14.07 before pool fee | ~$13.90 expected |
| What a win looks like | Fractions of a cent, continuously | ~$199,000, once every 14,317 years |
| Who holds it meanwhile | The pool, until you withdraw | Nobody — paid in the coinbase |
| Electricity | Identical | |
Pool figure calculated at a hashprice of $32.10 per PH/s per day (Hashrate Index, 3 August 2026), which is gross revenue before any pool fee. Solo expectation from a difficulty of 126.23 trillion and a block value of 3.125 BTC subsidy plus 0.0249 BTC average fees at a bitcoin price of $63,160. Both move constantly; check the Network Radar for current values.
The two annual figures land within about one percent of each other, and the pool column is gross — subtract its fee and they are effectively the same number. That is exactly what the mathematics predicts, and our solo versus pool comparison goes into why the identity holds and where fee structures break it.
The obstacle nobody mentions
There is a practical reason small boards usually end up on solo pools even when the owner wanted a trickle, and it is not the mathematics. It is minimum payout thresholds.
| Threshold | Value | Time to reach it at 1.2 TH/s |
|---|---|---|
| 0.005 BTC (F2Pool) | ~$315.80 | 22.4 years |
| 0.001 BTC (Foundry, Luxor, Braiins on-chain) | ~$63.16 | 4.5 years |
| 0.0001 BTC | ~$6.32 | 0.45 years |
| 0.00001 BTC via Lightning (OCEAN) | ~$0.63 | 16 days |
| No minimum via Lightning (Braiins) | — | Daily |
Read the top and bottom rows together. A Bitaxe on a pool with a 0.005 BTC minimum would be accumulating a balance it could not withdraw for longer than the device will physically last. At the common 0.001 BTC level it is still most of the device’s useful life.
Lightning payouts remove the problem entirely, and this is the part most setup guides skip. Two pools currently offer it: one with a 0.00001 BTC minimum, and one with no minimum and no fee, processing over a thousand small payouts a day. At that point a Bitaxe on a shared pool receives its fractions of a cent daily rather than theoretically.
So the honest version is not “small boards cannot pool mine”. It is that the threshold decides whether they can, it varies by a factor of 500 between pools, and it is the first thing to check — before the fee, before the hashrate share, before anything else. Our seven criteria cover what else to weigh once that gate is passed.
How to switch, in practice
The mechanics are the same in either direction.
- Get the new pool’s stratum host and port. Both are published; neither is secret.
- Decide what goes in the username. Solo pool: your on-chain payout address, optionally with a worker suffix. Shared pool: the account or worker name you registered there.
- Set the fallback too. A second host means the device keeps hashing if the first is unreachable. There is no reason to leave it blank.
- Save and restart, then confirm on the dashboard that shares are being accepted. Accepted shares climbing is the only proof that matters.
- Check the pool’s own view. Your device saying it is hashing and the pool seeing your worker are two different claims.
Nothing here needs a firmware flash, a factory reset, or new hardware. If a guide tells you that switching requires any of those, it is describing something else.
So which should you choose?
Since the expected value is the same, the question is genuinely about temperament and purpose rather than returns.
- Choose a shared pool if you want to see small amounts accumulate, if watching a number go up is part of why you bought the device, and if you have checked the payout threshold works at your hashrate.
- Choose solo if you want the whole reward or nothing, if you prefer the payout to arrive in the coinbase with nobody holding a balance for you, or if you are mining a smaller chain where the odds are within a human timeframe.
- Choose both. Each device is configured independently, so a mixed fleet is entirely normal. Nothing prevents one board on a pool and two solo.
What matters more than the choice is that it is a choice. The device does not have an opinion, the marketing name is not a technical claim, and the field is right there in the settings. If someone sold you a “solo miner” and you would rather mine on a pool, nothing is stopping you. And if you have never opened Pool Settings at all, that is the one thing worth doing today.
Choosing solo? Here is where to point it.
SoloFury supports all five SHA-256 chains with configurable vardiff for low-hashrate devices. 1% pool fee. 99% direct to your wallet via coinbase — no balance, no threshold, no withdrawal.
Configure your miner →Live Network Radar →Calculate your block odds →Frequently Asked Questions
Can I use a Bitaxe with a normal mining pool?
Yes. A Bitaxe speaks standard Stratum, so it connects to any SHA-256 pool that accepts it. You change the stratum host, the port and the username field, save, and restart. Nothing about the hardware is solo-specific.
Does solo mining use more electricity than pool mining?
No. The chip performs exactly the same SHA-256 computations either way. Hashrate, wattage, temperature and noise are identical. The only thing that differs is which server receives your shares and who is credited for a block.
What actually changes when I switch from solo to pool?
Three fields in AxeOS: the stratum host, the port, and the username. On a solo pool the username is normally your own payout address. On a shared pool it is an account or worker name registered with that pool. Everything else stays as it is.
Which pays more, solo or pool, on a Bitaxe?
Expected value is nearly identical. At 1.2 TH/s a pool grosses roughly $14.07 a year before its fee, against a solo expectation of about $13.90. After a typical pool fee the two land within a percent of each other. The difference is the shape, not the size.
Why can't I withdraw my pool earnings from a Bitaxe?
Minimum payout thresholds. At 1.2 TH/s you earn about $0.039 a day, so reaching a common 0.001 BTC minimum takes roughly 4.5 years. Two pools solve this with Lightning payouts that have no minimum at all, which is the single most useful thing to check before pointing a small board at a shared pool.
Is my Bitaxe mining to someone else's address out of the box?
It may be. Devices ship with preset pool credentials that vary by manufacturer, and if you never changed the username field, a found block would not pay you. Check the Stratum User field in AxeOS before anything else.
What does 'solo mining' actually mean?
It has three competing meanings in current usage: keeping the entire block reward rather than a share, running your own node and building your own templates, or pointing a small device at a solo pool. Most disagreements about solo mining are really disagreements about which definition is being used.
Can I run some miners on solo and others on a pool?
Yes. Each device is configured independently, so a mixed fleet is entirely normal. Some people run their largest board on a pool for steady output and the small ones solo as lottery tickets.