How to configure a mining worker name? (Dashboard)

Understanding Worker Name Configuration

1. A worker name is a unique identifier assigned to each mining device connected to a pool dashboard. It allows operators to distinguish between individual rigs in a multi-device setup.

2. The naming convention typically follows alphanumeric rules, with underscores or hyphens permitted but spaces and special characters prohibited.

3. Worker names appear directly in real-time hash rate charts, error logs, and uptime metrics on the dashboard interface.

4. Misconfigured names may cause duplicate entries or missing statistics if the pool interprets two devices as one due to identical identifiers.

5. Some dashboards auto-generate default names like 'rig001' or 'worker_123', but manual override is strongly recommended for operational clarity.

Accessing the Dashboard Settings Panel

1. Log into the mining pool dashboard using valid credentials and two-factor authentication where enabled.

2. Navigate to the 'Workers' or 'Devices' section, often located under a top-level menu labeled 'Mining' or 'Dashboard'.

3. Locate the specific worker entry requiring reconfiguration—this may involve filtering by IP address, user agent, or last seen timestamp.

4. Click the gear icon or 'Edit' button adjacent to the worker row to open the configuration modal.

5. Confirm that the session has sufficient permissions; read-only accounts cannot modify worker names.

Formatting Rules and Restrictions

1. Maximum length is usually capped at 32 characters, though some pools enforce stricter limits of 20 or fewer.

2. Uppercase letters, lowercase letters, digits, underscores (_), and hyphens (-) are universally accepted.

3. Symbols such as @, #, $, %, &, *, /, \, :, ;, ', ', , ?, |, and spaces trigger validation errors upon submission.

4. Leading or trailing whitespace is automatically trimmed, but embedded whitespace causes rejection.

5. Reusing an existing worker name within the same account triggers a conflict warning and blocks the update.

Applying Changes Across Mining Software

1. After saving the new name in the dashboard, restart the miner software to ensure synchronization with the pool’s registry.

2. For CGMiner-based setups, verify the --user parameter includes the updated worker name appended to the wallet address (e.g., wallet.workername).

3. In T-Rex Miner, confirm the -u flag reflects the revised identifier in the startup script or config.json file.

4. HiveOS users must update the 'Worker Name' field in the rig’s 'Settings → General' tab, then reboot the rig OS instance.

5. Failure to align local miner configuration with the dashboard name results in rejected shares and zero reported hash rate.

Frequently Asked Questions

Q: Can I change the worker name while the miner is actively submitting shares?A: Yes, but the change only takes effect after the miner reconnects. Pending shares submitted under the old name remain attributed to it until the next connection handshake.

Q: Does renaming a worker affect historical statistics?A: No. All past data—including accepted shares, rejected shares, and uptime—is permanently tied to the original worker name used during those submissions.

Q: Why does my newly named worker appear offline for several minutes after renaming?A: The pool requires time to de-register the old identity and register the new one. This process usually completes within 90 seconds unless network latency or firewall rules interfere.

Q: Is it possible to assign the same worker name to rigs under different user accounts on the same pool?A: Yes. Worker names are scoped per account. Two separate users may both use 'rig01' without conflict since the pool distinguishes them via wallet address and API key boundaries.