A mining pool worker name is the label that identifies a specific miner under your pool account. It helps the pool connect submitted shares, hashrate data, and worker status to the right machine. In most setups, it is not your wallet address or the mining pool URL. It is an identifier entered in your ASIC dashboard or mining software.

Clear worker names make it easier to monitor multiple miners, spot an underperforming unit, and locate the machine that needs attention.

What a Mining Pool Worker Name Means

A worker name identifies one mining device or mining instance. The pool uses it alongside your account, sub-account, or payout address to record the work your machine submits.

For example, a pool may expect a value such as `accountname.workername`. In that format, `accountname` identifies the account, while `workername` identifies the individual machine. A miner named `homefarm.asic01` might be the first ASIC in a home mining setup.

Worker name vs. pool URL and wallet address

These fields serve different purposes:

• The pool URL, often a Stratum address, tells the miner where to connect.
• The worker name identifies the account and device the miner represents.
• A wallet address may be used for payout on some pools, or as part of the worker credential in wallet-based setups.
• The password field may be used for authentication, a device setting, or simply a required placeholder, depending on the pool.

Always follow the exact format in the coin-specific pool guide. A valid format for one pool or coin is not automatically valid for another.

How a Worker Name Connects Your Miner to a Pool Account

Mining pools combine hashrate from many participants. Your miner receives work from the pool and sends back shares, which are proofs that it is performing hashing work. The pool records accepted shares and applies its reward rules to the account connected to that worker.

How shares are tracked

When a miner connects successfully, the pool reads the credentials in its configuration. If the account and worker portions are correctly formatted, the pool can associate submitted shares with that worker.

A worker name does not change the hashrate your machine produces. Its role is identification and tracking. Results still depend on equipment performance, uptime, network conditions, rejected shares, pool rules, and the coin being mined.

Why one account can have many workers

A single miner can use a simple name such as `miner01`. A larger operation may use dozens or hundreds of names. Distinct labels help operators isolate problems: worker-level data can reveal which unit has low hashrate or frequent interruptions.

Common Mining Pool Worker Name Formats

The exact syntax depends on the pool, coin, and setup method. These are common patterns, not universal instructions.

Account-based formats

Many pools use an account or sub-account followed by a period and a worker label:

• `account.workername`
• `subaccount.workername`
• `username.workerID`

ViaBTC mining guides for several supported coins use a period to separate the username or user ID from the worker name. For example, an account called `viabtc` could use a worker such as `viabtc.001`, subject to the current rules for that coin.

Wallet-based formats

Some pools use a wallet address as the main identifier. The worker field may then look like this:

• `walletaddress.workername`
• `walletaddress`

Do not assume that an account-based worker name works on a wallet-based pool. Enter the complete credential exactly as the pool’s current setup instructions require.

How to Set a Worker Name on Your Miner

Setting a mining pool worker name usually takes only a few minutes, but a single incorrect character can prevent a successful connection. Before you begin, open the current official mining guide for the coin and pool you selected.

1. Log in to your miner’s web dashboard or open your mining software configuration.
2. Select the correct coin and pool endpoint. Make sure the miner hardware and pool URL use the same mining algorithm.
3. Find the field labeled Worker, Username, User, or similar. Some dashboards combine the account and worker into one field.
4. Enter the required full value. If the pool uses `account.workername`, enter both parts rather than only the device label.
5. Use a short, recognizable worker label. For example, `sitea-rack2-03` is more useful than a random string because it identifies the device location.
6. Enter the password only as specified by the pool or your miner firmware.
7. Save the configuration and restart or apply the settings if the device requests it.
8. After the miner establishes a stable connection, check the pool’s worker page for hashrate, accepted shares, and worker status.

A newly connected worker may take time to appear in the dashboard. Timing varies by coin, dashboard, and network conditions, so check the current pool documentation if the worker remains missing.

How to Name Workers for Easier Monitoring

A good worker name describes the machine without exposing sensitive information. Use a convention you can apply consistently across every location and device.

Useful naming patterns

Choose labels based on information you need when diagnosing an issue:

• Location: `garage-01`, `siteb-12`, or `rack3-04`
• Hardware type: `s19-01` or `gpu-rig-02`
• Physical placement: `row2-slot7`
• Role: `test-unit` or `backup-asic`

You can combine these details. For example, `sitea-rack1-s19-03` gives a technician enough context to locate the machine quickly.

Names to avoid

Avoid duplicate names whenever possible, as they make it harder to identify the correct device in a dashboard. Do not put passwords, private keys, recovery phrases, or personal data in a worker name. A worker label is an operational identifier, not secure storage.

Check permitted characters and length before saving. Some ViaBTC guides specify worker ID requirements, while rules can differ by coin or product. The current guide for your selected coin is the controlling reference.

Troubleshooting a Missing or Offline Worker

If your mining pool worker name does not appear in the dashboard, start with the configuration fields rather than changing multiple settings at once.

First, confirm the pool URL and port. The endpoint must match the coin and mining algorithm. Next, compare the worker credential character by character with the official format. Common mistakes include omitting the account prefix, using the wrong separator, entering an email address instead of a pool username, or copying an extra space.

Then inspect the miner’s local status page. Look for connection errors, authentication messages, rejected-share warnings, or a hashrate reading of zero. If the miner is connected but sends no accepted shares, investigate network connectivity, firmware settings, hardware temperature, and the selected pool configuration.

Use this quick checklist:

• Confirm that the account, sub-account, or wallet identifier is correct.
• Confirm that the worker label follows the required character and length rules.
• Confirm that the primary and backup URLs are for the same coin and algorithm.
• Check whether the miner is receiving work and submitting accepted shares.
• Allow time for the pool dashboard to detect a newly stabilized worker.
• Review the pool’s current documentation before changing ports or passwords.

Key Takeaway

Use the exact credential format required by your selected pool and coin, whether it is an account-based value such as `account.workername` or a wallet-based format. If a worker is missing, first check the pool URL, port, account prefix, separator, and miner status for accepted shares.