Understand the fundamentals
Separate destination from identity
A pool endpoint tells the miner where and how to connect. It usually has three parts. The protocol is the communication method, such as Stratum, which most pools use. The hostname is the pool server’s name. The port is a number that picks the right service on that server. The pool’s and firmware’s documentation give the exact format. The worker field tells the pool which account or worker gets credit for the work the miner submits. So the endpoint answers where to connect, and the worker field answers who gets credit.
The miner’s local IP address is how an approved computer reaches the miner’s web interface. A payout address is the Bitcoin address that receives payment, and it is part of the pool’s payment settings. Do not type either one into the worker field just because it looks like an ID. Follow the pool’s instructions for what goes there.
Read a pool entry one field at a time
Swipe sideways to follow the full diagram →
See how it works
Use the approved naming plan
A worker name can label one machine, one rack or another group of machines. A separate name for each machine makes each one easier to watch. A shared name adds the work of several machines together, so one stopped machine can be hard to spot. The site should keep a record that links each worker name to physical equipment. Then a pool alert can be traced to a real machine.
Many miners let you enter more than one pool. The extra entries are fallbacks, or backups. Which entry the miner uses, and when it switches, depend on the firmware and its settings. A miner on a backup pool may be working as designed because the main pool is down. It may also point to an unplanned settings change. Record which pool entry is actually active.
Connect it to the field
Example: work appears under the wrong label
A miner reports accepted shares, but its expected worker shows no activity on the pool. At the same time, work under a different worker name starts rising. The first idea to test is an attribution mismatch: the work is being credited to the wrong name. Do not jump to a failed hashboard. Compare three things over the same time period: the approved settings, the settings active on the miner, and the pool account records.
Only authorized staff should change live account settings. Keep the before and after values in a protected record. Leave passwords and other secrets out of general tickets. The fix is confirmed only when accepted work appears under the correct worker name after the approved change.
Terms used in this lesson
- Endpoint and port
- Where the miner sends its pool connection.
- Worker identifier
- The name the pool uses to credit submitted work to an account or worker.
- Fallback
- A backup pool entry. The firmware decides when the miner switches to it.
Optional references & further reading
Use current manufacturer instructions for the exact equipment and your site’s approved procedures. Course levels do not grant task authorization.