A worker name is the label a mining pool uses to distinguish one miner, or one mining instance, from another within the same pool account. It has no effect on hashrate, payout method, or BTC revenue. Its only function is operational: it lets an operator and the pool's monitoring dashboard tell machines apart. For an operator running a single ASIC, worker naming is largely cosmetic. For an operator running dozens or hundreds of machines, a consistent naming approach is often the difference between resolving an offline-worker alert in minutes and spending an afternoon checking every rack.
This article explains what a worker name does, why its allowed format is controlled by the pool rather than by any universal protocol standard, and how to build a naming convention that stays useful as a mining operation grows.
The Four Fields in a Mining Connection
When a miner is configured to connect to a pool, four distinct fields are typically involved, and it is easy to conflate them:
- Pool URL — the server address and port the miner connects to.
- Account identifier (username) — the pool account that receives credit for submitted shares.
- Worker name (worker ID) — a label that distinguishes a specific miner or mining instance under that account.
- Password field — a credential required by the connection protocol; on many pools this field is not the account login password, and some pools make it optional.
These fields serve different purposes and should not be combined. The worker name identifies the machine; it does not authenticate the account and does not determine how rewards are calculated.
Pool Documentation Controls the Allowed Format
There is no single industry-wide rule for how a worker name must be written. Each pool defines its own syntax, character restrictions, and length limits, and these rules can differ in ways that cause a configuration to fail silently or submit shares under the wrong label if copied from another pool.
For ViaBTC's BTC mining service, the worker field follows the structure userID.workerID. The workerID portion must use lowercase letters and numbers only, with a maximum length of 64 characters, and the password field is optional (ViaBTC Help Center, BTC Mining). Other pools apply different conventions. Braiins Pool documents a case-sensitive worker name with its own permitted-character pattern under the same userName.workerName structure (Braiins Pool, Worker Management FAQ), while f2pool's logged-in mining format uses accountname.workername but specifies that the worker-name portion must not contain a period or underscore (f2pool Help Center, How do I add a worker and set a worker name).
The practical implication is straightforward: check the current documentation for the specific pool before applying any naming convention, including the recommendations below. A hyphenated or mixed-case name that works on one pool may be rejected, or interpreted differently, on another.
Core Principles for a Usable Worker Name
Give each physical miner a distinct worker name when individual visibility matters. A unique identifier per device allows the pool dashboard to show per-machine status rather than aggregating activity under one entry. This is most useful when an operator wants to identify a specific unit behind an offline alert or an unexpected drop in reported hashrate.
Keep the name short. A worker name is read during troubleshooting, often from a dashboard list containing many entries. A compact identifier that still conveys location or sequence is easier to scan than a long descriptive string.
Keep the structure consistent across the fleet. A fixed pattern — for example, a short site code, a rack reference, and a unit number — makes it possible to sort, filter, or search the worker list predictably as the number of machines grows.
Avoid information that changes frequently or that does not belong in a label. A worker name is not an asset register, configuration file, or maintenance log. Firmware version, pool endpoint, fan curve, overclock setting, technician initials, full serial number, or an exact street address are better tracked in a separate inventory record than embedded in the name itself. Where broader classification is useful, many pool dashboards, including ViaBTC's, support grouping workers for filtering rather than requiring a longer name (ViaBTC Help Center, How to Manage Workers).
Do not place sensitive information in the name. The worker name is configuration data visible in pool dashboards and logs; it should not contain a password, recovery phrase, private key, or personal information.
Device-Based or Location-Based Naming
An operator generally has two reasonable approaches, and the choice is an operational preference rather than a pool requirement.
A device-based name stays attached to a specific ASIC and travels with it if the unit is relocated. This keeps historical worker data associated with the same machine, but requires a separate record if the operator wants to know where that machine is currently installed.
A location-based name helps a technician find a machine quickly on-site but may need to be updated if the unit moves to a different rack or room. A balanced option combines a short location reference with a stable internal unit number, so the name remains reasonably informative without becoming a full address.
If miners are moved between racks or sites with any regularity, it is worth maintaining a simple spreadsheet or inventory system that maps each worker name to the miner's serial number and current location, rather than relying on the worker name alone to track the physical device.
Example Naming Patterns
The following examples use only lowercase letters and numbers, consistent with ViaBTC's BTC worker-ID restriction; always confirm the current rule for the pool in use before applying them.
Small setup (a few miners):
youruserid.asic01
youruserid.asic02
A sequential label is sufficient when the operator can visually locate one of a handful of machines without additional reference points.
Multi-rack operation:
youruserid.tx1r02u014
Here tx1 can represent an internal site code, r02 a rack reference, and u014 a unit number. The exact meaning of each segment should match the operator's own inventory system rather than a fixed external standard.
Temporary or test deployment:
youruserid.labtest03
A role-based label can be clearer than a location label for a unit used for short-term evaluation. If a test unit is later put into permanent service, it is simpler to retain the existing worker name and update the separate inventory record than to rename it and lose the history associated with that worker entry.
Patterns to avoid on ViaBTC BTC mining:
youruserid.asic
youruserid.default
youruserid.tx-site-rack-2-unit-14
The first two are not distinct enough for a multi-device operation, since a generic label applied to several miners prevents the dashboard from distinguishing between them. The third uses hyphens, which fall outside ViaBTC's documented lowercase-letters-and-numbers rule for the worker ID.
Configuring and Verifying the Worker Name
After entering the pool URL, account identifier, and worker name in the miner's configuration page, it is good practice to verify the setup rather than assume it is correct:
- Confirm the pool URL, port, account identifier, and full worker name match what the pool documentation specifies.
- Check the miner's local status page for connection errors or share-submission failures.
- Allow the connection to stabilize before checking pool-side status. ViaBTC's documentation suggests checking the Workers and Earnings pages after roughly 10–15 minutes of stable operation (ViaBTC Help Center, BTC Mining).
- Confirm the expected worker name appears in the pool dashboard with a reported hashrate.
When a miner is also configured with a backup pool address for failover, it is advisable to keep the same account identifier and worker name in both the primary and backup entries. This represents the same physical miner using the same worker credential across two connection endpoints, rather than two separate workers; using a different name in the backup configuration would make the machine appear as a new, unrelated entry if failover occurs.
Maintaining Worker Names Over Time
As a fleet grows, the worker list on a pool dashboard can accumulate entries from decommissioned machines or past tests. ViaBTC's dashboard classifies a worker as offline if it reports no hashrate for a period between 20 minutes and one day, and as inactive if it reports no hashrate for more than one day (ViaBTC Help Center, How to Manage Workers). These are status definitions specific to ViaBTC's dashboard rather than universal measures of miner downtime, but they are useful as a basis for periodically reviewing and removing worker entries that no longer correspond to an active machine.
Where a pool supports grouping workers, such as ViaBTC's worker-group feature, organizing workers by site or rack can reduce the need to encode that information directly into each name, keeping individual labels short while still allowing filtered views of the fleet.
FAQ
What is the difference between a pool account identifier and a worker name?
The account identifier is the pool account that receives credit for submitted shares and determines payouts. The worker name is a label under that account used to distinguish one miner or mining instance from another; it does not affect which account is credited.
Does changing a worker name affect hashrate or earnings?
No. A worker name is an identifier used for monitoring and troubleshooting. It does not change the mining algorithm, share submission, or how rewards are calculated for the account.
Can I use the same worker name for multiple miners?
Most pools will accept it, but doing so causes those miners' activity to appear as a single entry on the dashboard, which reduces the ability to identify a specific machine during troubleshooting.
Should I include the miner's serial number in the worker name?
It is not necessary and can make the name harder to read. A shorter identifier combined with a separate inventory record that maps the worker name to the serial number is generally easier to maintain.
Do worker naming rules differ between pools?
Yes. Allowed characters, case sensitivity, separators, and length limits vary by pool. Always check the current documentation for the specific pool before applying a naming convention designed for a different platform.