Introduction

To manage different mining farms with ViaBTC subaccounts, create a subaccount for each farm, connect its miners using that subaccount's username, and review its workers, hashrate, mining income, alerts, and payout settings separately. This structure can also help operators organize hosted-miner groups or separate self-operated and third-party-owned ASICs under one main account.

ViaBTC subaccounts are subsidiary mining accounts with separate hashrate and mining-income displays. Each can have its own auto-withdrawal address and notification email (ViaBTC subaccount guide).

What Is a ViaBTC Subaccount?

A ViaBTC subaccount functions as an independent mining account nested under the main account. Workers can connect using a subaccount's username, and its dashboard shows its own hashrate, worker list, and mining-income figures, separate from other subaccounts and the main account. According to ViaBTC's documentation, a user may create as many subaccounts as needed.

Subaccounts organize pool-side monitoring and payouts. They do not replace device-level monitoring, bookkeeping, or agreements between an operator and its customers.

When Separate Subaccounts Make Sense

Separate subaccounts can be useful in several situations, though the right structure depends on how an operation is organized:

• Different physical farms. A facility in one location and a facility in another—for example, an air-cooled site and a hydro-cooled site—may each warrant a dedicated subaccount so hashrate and income are not mixed in one dashboard.
• Different hosting arrangements. An operator managing miners across multiple hosting providers may find it easier to review each provider's fleet separately.
• Self-operated versus hosted miners. Keeping owner-operated ASICs apart from machines managed on behalf of a third party can simplify both monitoring and reporting.
• Separate customer or partner allocations. Separate subaccounts can help where distinct pool dashboards and income records are required for different parties.
• Different payout destinations or internal allocations. Separate subaccounts can be useful where each group needs its own withdrawal address or auto-withdrawal configuration.

These are practical considerations rather than requirements; an operator with a single small farm may not need more than one subaccount.

A Simple Account Hierarchy for Multi-Farm Mining

The following structure illustrates one way an operator might organize a main account, subaccounts, workers, and worker groups. Farm A, Farm B, and Hosted Miners are descriptive labels here; use the actual subaccount username when configuring a miner.

Main account
├── Farm A subaccount
│   ├── Worker IDs: farma001, farma002, farma003
│   └── Worker groups: Container-1, Container-2
├── Farm B subaccount
│   ├── Worker IDs: farmb001, farmb002
│   └── Worker groups: Air-cooled, Hydro-cooled
└── Hosted Miners subaccount
    ├── Worker IDs: host001, host002
    └── Worker groups: Customer-1, Customer-2

In this layout, the subaccount separates farms, hosting arrangements, or customer groups, while workers and worker groups organize individual miners within it.

Setting Up a Farm Under a Subaccount

1. Create the subaccount. Sign in to ViaBTC and open Account Management → Mining Account → Create Sub-Account. Enter the subaccount name and confirm.
2. Switch to the subaccount. Select its name from the account menu at the top right of the page. This lets you review the intended mining account before configuring and checking its miners (ViaBTC subaccount guide).
3. Configure the miners. In each miner's configuration interface, enter the applicable mining URL and port from the official guide for the coin you are mining.
4. Enter the mining username. Use userID.workerID, where userID is the actual subaccount username. For example, if your subaccount username is farma, the first miner could use farma.farma001. For Bitcoin, ViaBTC specifies worker IDs containing lowercase letters and numbers, up to 64 characters. Use a distinct worker ID for each miner (BTC mining guide).
5. Check the connection. Save the miner configuration and allow time for stable operation. ViaBTC's BTC guide recommends checking worker status and earnings after approximately 10–15 minutes of stabilization.
6. Review the farm's settings. Once workers appear, check the subaccount's worker list, earnings record, alert settings, and payout configuration.

Worker Names and Worker Groups for Day-to-Day Operations

Within a subaccount, individual miners appear automatically as workers once they connect and begin submitting shares. ViaBTC's worker-management documentation defines three status categories: active, offline, and inactive. A worker is marked offline when it has shown no hashrate for between 20 minutes and one day, and inactive when no hashrate has been recorded for more than one day. These are pool-side dashboard classifications rather than a direct diagnosis of hardware health (worker-management guide).

Worker groups provide an optional layer of organization beneath the subaccount—for example, grouping workers by container, rack, or customer batch. A consistent naming scheme, such as farma001 or hostedcustomer1012, makes it easier to identify a specific machine when reviewing alerts or worker lists.

To organize workers, open Pool → Workers. Under My group, use Create group or Manage group. To assign workers, select Manage Miners in the worker list, choose the relevant workers, and use Add to to move them into the intended group.

Configuring Alerts for Each Farm

ViaBTC supports hashrate and rejection-rate notifications through email, app push, or Telegram, depending on the configuration. Worker-offline and rejection-rate alerts can also be delivered to a Telegram group (notification setup guide).

For each farm's subaccount:

1. Switch to the relevant subaccount.
2. Open Pool → Dashboard → Alert Settings.
3. Configure the available alert parameters and click Confirm.
4. Under Notification Method, set the receiving email address or Telegram account as applicable.

ViaBTC documents support for different notification email addresses for different subaccounts. Choose available thresholds that reflect each farm's normal hashrate and variability rather than applying one fixed threshold across sites with materially different fleet sizes or miner models.

Investigate sustained deviations using both the pool dashboard and local monitoring tools to identify the affected equipment or connection.

Payout Settings and Revenue Allocation

Configure Auto-Withdrawal for Each Subaccount

ViaBTC supports two auto-withdrawal destinations:

• An external address. The applicable minimum payment requirement applies. ViaBTC currently lists 0.001 BTC as the Bitcoin minimum; check the current documentation and account settings before enabling withdrawals.
• Your own ViaBTC main account or subaccount. This route supports only accounts belonging to you. The minimum payment amount does not apply, provided the withdrawal amount is greater than zero.

Auto-withdrawal supports Payout by Account Balance and Payout by Daily Earnings. It is processed once daily between 10:00 and 18:00 (GMT+8), subject to the applicable payout conditions (auto-withdrawal guide).

Multi-account tools let you compare auto-withdrawal settings or synchronize them across accounts. Synchronization applies the current account's withdrawal address, minimum payout amount, and auto-withdrawal switch to selected accounts. Check these settings and the target accounts carefully, especially when farms need different payout destinations.

Use Revenue Sharing for Proportional Allocations

For operations that need to divide proceeds among partners or other ViaBTC accounts, Revenue Sharing can allocate a portion of the current account's mining yield proportionally to recipient main accounts or subaccounts. This is separate from auto-withdrawal to your own accounts.

Revenue Sharing settings take effect when saved, while daily yield is settled and transferred to recipients the following day under ViaBTC's documented T+1 process. Saving a configuration does not mean an immediate transfer of earnings (Revenue Sharing guide).

Comparing Data Across Farms Correctly

When reviewing multiple farms side by side, compare figures using the same measurement type and time window. ViaBTC's real-time pool hashrate is calculated as the average over the preceding 10 minutes, while its daily hashrate reflects the average over the preceding 24 hours. A miner's local display may use a different averaging period or refresh schedule (pool and local hashrate explanation).

For routine comparisons across farms, use matching pool-side metrics and periods. You can also cross-check pool-side figures against local ASIC readings when troubleshooting, but account for differences in their measurement methods and time windows before interpreting a gap.

A lower pool-side figure than a local reading does not, on its own, indicate hardware underperformance. ViaBTC identifies possible causes including network latency, rejection rate, and hardware or firmware settings. Energy efficiency in J/TH also requires a matching measured power input, so pool-side hashrate alone is insufficient to calculate it.

Practical Checklist

• Consider creating one subaccount per meaningful farm, hosting arrangement, customer group, or payout boundary.
• Use a consistent worker-naming scheme that follows the applicable coin's configuration rules.
• Use worker groups where a subaccount contains several containers, racks, or customer batches.
• Set available alert thresholds appropriate to each farm's typical hashrate and variability.
• Review withdrawal destinations and applicable minimum payment requirements before enabling multi-account synchronization.
• Compare hashrate and income figures across compatible measurement windows.
• Protect the main account using available verification tools, such as email confirmation, two-factor authentication, and password verification.

FAQ

What is the difference between a subaccount and a worker?

A subaccount is a subsidiary pool account with its own hashrate display, income record, and payout settings, typically used to separate a farm, hosting arrangement, or customer group. A worker identifies a connected miner within a subaccount or the main account; workers do not have independent payout settings.

Can I delete a ViaBTC subaccount once it is created?

As checked on 10 October 2026, ViaBTC's official subaccount guide contains conflicting instructions: its introduction says subaccounts cannot be deleted, while a later section describes a deletion option under Account Management. Confirm the current rule with ViaBTC support before relying on deletion, and choose subaccount names and structures carefully (subaccount guide).

How many subaccounts can I create?

ViaBTC's subaccount guide states that users can create as many subaccounts as they need; that guide does not specify a numeric limit.

References

• What are Sub-Accounts for? How Can I Add One?
• BTC Mining
• How to Manage Workers?
• How to Set Hashrate or Rejection Rate Notification?
• What Is Auto Withdrawal? How to Set Up and Manage It?
• What is & How to Set Revenue Sharing
• Why is the Hashrate Shown in the Mining Pool Lower than that of the Mining Machine?