Pool account prefix
Use the subaccount and separator format required by the selected mining pool.
Plan ASIC Worker Names for BTC Tools
Create a stable worker naming convention that maps BTC Tools device records to sites, rooms, racks or inventory identifiers.
Workflow
Worker naming rules
A worker name connects pool-side activity with a physical miner. A durable convention should identify location or asset without depending only on an IP address that may change.
Physical suffix
Encode a useful rack, row, room, or asset identifier in the worker suffix.
Stable records
Keep serial, MAC, model, expected IP, and worker name together in the inventory.
Controlled rename
Test the convention on a small group and confirm pool-side visibility before renaming more miners.
Checklist
Before you continue
Choose a convention that technicians can read and pool dashboards can accept.
- Confirm the pool's allowed separator and characters.
- Keep the account prefix consistent.
- Use a suffix that maps to a physical or asset record.
- Avoid sensitive customer or personal data in public pool dashboards.
- Document exceptions before a bulk rename.
- Confirm renamed workers appear under the intended pool account.
Operations
Worker naming patterns
Examples are structural only; replace them with the actual pool account and farm identifiers.
| Area | What to check | BTC Tools workflow |
|---|---|---|
| Rack-based | account.r03u12 | Maps to rack 03, unit 12. |
| Room and rack | account.room2-r07-04 | Useful across several rooms. |
| Asset-based | account.asset1842 | Matches an internal asset register. |
| IP-only | account.192-168-1-44 | Easy initially but unstable when addressing changes. |
| Random suffix | account.miner7 | Hard to reconcile without a separate mapping record. |
Setup
Rename in a small observable batch
Apply the convention to a few miners, check pool-side worker names and accepted work, then update the inventory before continuing with the next group.
