How to Name Solo Mining Workers (Bitaxe & ASIC)
Worker naming best practices for solo mining: the address.worker format, safe characters, and a prefix convention that auto-groups your Bitaxe and ASIC fleet.
What a worker name is (and what it is not)
When you point a miner at a solo pool, the stratum username carries two things: your wallet address, and an optional worker name after a dot.
bc1qyourwalletaddress.rack1_s19-01
└──── wallet address ────┘ └─ worker ─┘The address is what matters for money: when your miner finds a block, the coinbase pays that address directly. The worker name matters only for you — it is the label the dashboard uses to show each device as its own row, with its own hashrate, best share and last-share time.
Leave the worker name out and every device you own collapses into one entry. You still see the total hashrate, but you can no longer tell which S19 is the one that just dropped to half speed.
Why naming matters more as your fleet grows
One Bitaxe does not need a naming convention. Twenty devices do. At that scale the workers table becomes a wall of similar rows, and the questions you actually ask are about groups: is the garage rack all online? Are the four S21 Plus units performing the same? Which of the client machines has stopped?
A naming convention answers those questions before you open a single detail panel, because a dashboard can read structure from the name itself — if the structure is there.
The convention: prefix first, hardware after
Use this shape for every worker:
<prefix>_<hardware>-<number>- prefix — where the device is, or who it belongs to:
rack1,garage,office,clienta. This is the part that defines the group. - hardware — the model family, short:
s19,s21p,gamma,ultra. - number — a two-digit index so names sort cleanly:
01,02, …12.
Examples from a mixed home fleet:
| Worker name | Group | Reads as |
|---|---|---|
rack1_s19-01 | rack1 | first S19 in rack 1 |
rack1_s19-02 | rack1 | second S19 in rack 1 |
garage_gamma01 | garage | Bitaxe Gamma in the garage |
garage_ultra01 | garage | Bitaxe Ultra in the garage |
office_s21p-01 | office | S21 Plus in the office |
clienta_s21-03 | clienta | third S21 hosted for client A |
The underscore after the prefix is the separator the dashboard looks for. The hyphen before the number is just for readability.
Characters: what is safe everywhere
Firmware fields and pool parsers are not all equally forgiving. The intersection that works everywhere:
- letters
a-zA-Z - digits
0-9 - hyphen
-and underscore_
Avoid spaces, @, :, /, #, quotes and anything decorative. Keep the whole worker name short — roughly a dozen characters is plenty, and long names get truncated in narrow firmware screens and mobile tables.
Case is preserved as you type it, but treat names as case-sensitive when you compare them: Rack1_s19-01 and rack1_s19-01 are two different workers to a dashboard.
How SoloFury turns names into groups
On your miner dashboard, the workers table has a Group by control with four modes. Two of them read your naming convention directly:
Family — the default once you have more than six workers. For each name, the dashboard takes the text before the first underscore as the group. No underscore? It strips the trailing number instead, so S21Plus01, S21Plus02, S21Plus03 still gather under S21Plus. Each group header shows the summed hashrate, online count, best difficulty and the most recent share, and collapses with a click.
Region — groups by the stratum region each device connects through, useful when a fleet is spread across locations.
Custom — drag one worker onto another, name the group, done. Multi-select with checkboxes works the same way on mobile. Custom groups are saved in your browser per wallet address and coin, so they are there the next time you open the page.
None — the flat list, for small setups.
The point of the naming convention is that Family needs nothing from you. Name devices consistently once, and every browser, phone or tablet you use to check the dashboard shows the same groups — the grouping lives in the names, not in a setting.
Bonus: outlier detection inside a family
Grouping does more than tidy the table. When several devices of the same family sit in one group, the dashboard compares each one to the group’s median hashrate. A device running well below its siblings gets an Attention marker with the percentage gap — the kind of thing you would otherwise notice only after a week of slightly lower totals.
This only works when families are real: mixing an S19 and a Bitaxe in one group makes the median meaningless. Keep the hardware part of the name honest and the comparison stays honest too.
Setting the worker name on common hardware
Bitaxe / NerdAxe / AxeOS — open the device web interface, go to the stratum settings, and enter address.worker in the Stratum User field. The fallback pool has its own user field; give it the same name. Save and let the device restart.
Antminer, Whatsminer, Avalon — in the miner configuration, the pool Worker (or User) field takes address.worker. The password field is not used for authentication; any value works.
NerdMiner and similar — wallet address and worker name are usually two separate fields; put only the label in the worker field.
The Solo Start configurator generates the full username for you: paste your address, type the worker name, and copy the result into the firmware.
Key takeaways
- The username is
address.worker; the address gets paid, the worker name gets you a row on the dashboard. - Use
prefix_hardware-number. The prefix is the group; keep it about place or owner. - Letters, digits, hyphen, underscore. Nothing else, and keep it short.
- On SoloFury, Group by Family reads the prefix automatically — no setup, and it follows you across devices.
- Consistent hardware naming makes the per-family outlier check meaningful.
Naming is the cheapest monitoring upgrade a growing fleet can get: a few seconds per device, and the dashboard does the rest.
Frequently Asked Questions
What is a mining worker name?
A worker name is an optional label appended to your wallet address in the stratum username, separated by a dot: address.worker. The pool uses the address for payouts and the worker name only to tell your devices apart on the dashboard. It has no effect on rewards.
Do I have to set a worker name?
No. Your wallet address alone is a valid username. But without worker names, every device you own appears as a single merged entry, so you cannot see which one dropped hashrate or went offline. With more than one miner, a worker name per device is strongly recommended.
Which characters are allowed in a worker name?
Stick to letters, digits, hyphen and underscore. Avoid spaces, @, colons, slashes and any symbol that firmware or pools might reject. Keep names short and readable: a handful of characters is enough to identify a device.
Why use a prefix like rack1_ or garage_ in the worker name?
The prefix before the first underscore tells the dashboard which devices belong together. SoloFury's Family grouping reads that prefix and groups workers automatically — rack1_s19-01 and rack1_s19-02 land in a group called rack1 without any configuration, on every device you use to check the dashboard.
What happens if I do not use a prefix?
The dashboard falls back to the hardware family: it strips the trailing number, so S21Plus01, S21Plus02 and S21Plus03 still form an S21Plus group. The prefix convention simply gives you control over the grouping instead of leaving it to the model name.
Can I rename a worker later?
Yes. Change the stratum username on the device and it reconnects under the new name. The old name disappears from the online list once it stops submitting shares; historical statistics are kept per worker name, so the new name starts a fresh history.
How do I set the worker name on a Bitaxe?
Open the AxeOS web interface, go to the stratum settings and put address.worker in the Stratum User field — for example your bc1 address followed by .garage_gamma01. Save and let the device restart. The same field exists for the fallback pool.
Where do I see the groups on SoloFury?
On your miner dashboard, above the workers table. Group by Family uses your naming convention automatically; Group by Region splits devices by the stratum region they connect through; Custom lets you drag workers into groups you name yourself. Your choice is remembered per wallet address and coin.