Introduction

To connect a used Bitcoin ASIC to your own ViaBTC account, access the miner’s web interface, replace all inherited pool entries with ViaBTC’s BTC settings and your own worker identifier, then save and verify mining activity under your account. Before configuring the pool connection, confirm that you control the device and have secured its management access.

Acquiring a second-hand SHA-256 ASIC is a common way to enter or expand Bitcoin mining at a lower upfront cost, but a used unit is rarely a blank slate. It may still hold the previous owner's pool address, worker name, static network settings, or a login password set by a prior operator or repair technician. Before any used miner is placed on a production network, the operator needs to confirm two separate things: that they have full control of the device itself, and that the device is configured to submit shares under their own mining pool account rather than someone else's.

This guide treats those as two distinct tasks. The first half covers taking control of a used ASIC—inspection, access to its local web interface, and removal of inherited settings. The second half covers pointing the device at a ViaBTC BTC mining account using the pool's current Stratum configuration values.

What You Need Before Starting

A short checklist is enough to begin:

• A SHA-256 ASIC intended for Bitcoin mining (confirm that the model supports BTC).
• Power infrastructure appropriate for the specific model's rated consumption.
• An Ethernet connection on the same local network as the computer used for configuration; most ASICs do not support Wi-Fi.
• The miner's local IP address, or a way to discover it.
• A ViaBTC account and the account's User ID.
• The pool's current BTC Stratum settings, taken from official documentation rather than from a seller's screenshot.

Power requirements, default credentials, and reset procedures vary by manufacturer and model, so the device's own documentation should be the final reference for those details.

Step 1: Inspect, Locate, and Take Control of the Used ASIC

Before connecting a used unit to a production network, check fans, heat sinks, and cabling for damage, and confirm the model label matches a SHA-256 miner suited to Bitcoin. For a device of unknown history, use an isolated setup network while checking and recovering the miner, following ViaBTC’s guidance for used or potentially compromised miners.

Connect the ASIC by Ethernet and locate its IP address through the router’s DHCP client list or a manufacturer discovery tool. Open that address in a browser on a computer connected to the same local network. Bitmain’s S19/S19 Pro setup guide describes using its IP Reporter utility to locate the device and then opening its web interface (Bitmain Support).

If the previous owner’s login credentials are unknown, or inherited static network settings prevent access, follow the manufacturer’s reset or recovery instructions for the exact model. Do not assume that one model’s default credentials or reset procedure applies to every ASIC.

Depending on the device’s condition, a factory reset or installation of official firmware may be appropriate. Use the manufacturer’s firmware and recovery instructions for the exact model. Bitmain’s S19/S19 Pro guide documents restoration of default settings and warns that power must remain on throughout a firmware update. It also explains that the firmware upgrade’s “Keep Settings” option controls whether existing settings are retained.

After any reset or firmware recovery, locate the miner again if its network settings have changed, then set or verify a new management password. If no reset or recovery is needed, change the inherited password as soon as you gain access. Complete this check before placing the miner on the production network.

A factory reset clears stored configuration on supported models, but it does not by itself guarantee that a device is free of unauthorized firmware. A unit suspected of compromise may need model-specific recovery steps from the manufacturer.

Step 2: Secure the ViaBTC Account Before Directing Hashrate to It

Before any worker is pointed at a pool account, the account itself should be reasonably secured. This includes using a unique account password, enabling two-factor authentication, and reviewing withdrawal-related settings. ViaBTC's account security documentation describes email verification, 2FA, and password checks as available account-protection tools, and its 2FA guide recommends enabling two-factor authentication for sign-in after binding a mobile method or an authenticator app. Readers can review the process to set up two-factor authentication directly from ViaBTC's help center.

This step is separate from ASIC configuration, but it matters in the same context: a used-equipment setup is a reasonable moment to confirm that the account receiving the hashrate is itself properly protected.

Step 3: Remove the Previous Owner's Pool Details

This is the step most specific to used hardware, and it is easy to do incompletely. Most ASIC firmware exposes multiple pool entries—commonly labeled Pool 1, Pool 2, and Pool 3—so that the device can fail over to a backup connection if the primary one becomes unreachable. A previous owner's configuration can persist in a secondary row even after Pool 1 has been updated.

In the miner's Mining Configuration or Pool Settings page, review every configured pool row, not only the first one. Replace any existing pool URL and worker name with values tied to the current operator's own ViaBTC account. Leaving an old secondary entry in place means the device could still submit shares to the previous account under certain failover conditions.

Step 4: Enter the ViaBTC BTC Mining Settings

Once the inherited entries are cleared, the device can be pointed at ViaBTC. The pool's current BTC mining settings specify the Stratum URL, the worker-name format, and the password field's behavior for BTC mining.

A standard configuration looks like this, with the reader's own ViaBTC User ID substituted in place of the placeholder:

Pool URL:  stratum+tcp://btc.viabtc.io:3333
Worker:    yourUserID.asic01
Password:  [optional / firmware-required value]

Three fields deserve separate explanation, since they are sometimes confused in practice:

• Pool URL is the Stratum server address that tells the ASIC where to send its proof-of-work shares.
• Worker name follows the userID.workerID format. The userID segment identifies the ViaBTC account, and the workerID segment is a device label—such as asic01—that distinguishes this unit from others reporting to the same account. According to ViaBTC's documentation, the worker ID portion is limited to lowercase letters and numbers, up to 64 characters.
• Password is optional for ViaBTC's BTC configuration, though some ASIC firmware still requires a non-empty value in that field; any placeholder accepted by the firmware is sufficient.

None of these three fields is a BTC withdrawal address. The withdrawal address used for payouts is configured separately within the ViaBTC account and is never entered into the ASIC's pool or worker fields.

Step 5: Add a Backup Pool Entry, Where Supported

If the ASIC's firmware provides additional pool rows, a documented alternate ViaBTC port can be entered as a backup connection:

Pool URL:  stratum+tcp://btc.viabtc.io:443
Worker:    yourUserID.asic01
Password:  [optional / firmware-required value]

This is practical guidance rather than a requirement, and it is only relevant where the firmware supports multiple pool entries and automatic failover. A backup row should point to the operator's own account on the same pool, not to an unfamiliar third-party pool or any endpoint inherited from the previous owner.

Step 6: Save, Apply, and Verify Mining Activity

After saving the configuration, verification should happen in two places. On the ASIC's own interface, confirm that the device reports a stable connection, check for error messages or temperature alarms, and look for a share-submission status if the firmware exposes one. On the ViaBTC account side, check the Workers page and Earnings page once the device has had time to stabilize.

A saved configuration is not itself proof that mining has started; ViaBTC’s BTC setup guide advises checking the Workers and Earnings pages after the miner has stabilized for around 10–15 minutes. Treat this as an approximate checking interval, not a guaranteed dashboard update deadline; an absence in the first few minutes is not necessarily a sign of misconfiguration.

Two readings should not be treated as interchangeable. The hashrate shown on the ASIC's own interface is a device-side reading taken directly from the hardware. The hashrate shown on the ViaBTC Workers page is a pool-side estimate, calculated from the shares the pool has received over its selected display window. Shares themselves are reported as accepted or rejected; a pool's share target is deliberately easier to satisfy than the Bitcoin network's block target, which is why a miner can submit a steady stream of accepted shares without finding an actual block itself (Bitcoin Developer Documentation). Neither the device-side hashrate nor the share count should be read as a direct measure of BTC revenue; realized earnings depend on the pool's payout method and are reported separately on the account's earnings page.

Step 7: Configure Payouts Separately

Payout configuration is not part of connecting the ASIC and should be handled as its own task once mining activity is confirmed. ViaBTC's account settings allow an external withdrawal address to be configured, or funds can remain within the ViaBTC account balance, subject to the account's security verification. The platform also distinguishes between payout triggered by account balance and payout calculated from daily earnings, and operators should review the auto-withdrawal configuration documentation for the exact current rules before enabling it, since thresholds and settlement timing can change.

Troubleshooting: The ASIC Is Not Showing Under My Account

When a worker fails to appear after a reasonable stabilization period, work through the configuration in order rather than guessing at the cause:

1. Confirm the miner model and the selected pool algorithm both correspond to Bitcoin's SHA-256 mining.
2. Recheck the full Stratum URL, including the protocol prefix, hostname, and port.
3. Recheck the complete worker field, formatted as yourUserID.workerID.
4. Confirm that no secondary pool row still holds an old or third-party entry.
5. Check local Ethernet connectivity, DNS resolution, gateway settings, and any firewall rule that might block outbound Stratum traffic.
6. Reopen the ASIC's interface to confirm the settings were actually saved rather than reverted on reboot.
7. Allow time for stable operation and dashboard updates, using the documented 10–15-minute checking interval as a guide rather than a guaranteed deadline.
8. If a pool URL or worker name changes unexpectedly after being set correctly, treat it as a possible sign of compromise rather than a simple configuration error.

That last point is worth taking seriously on used equipment specifically. ViaBTC's guidance on miner malware lists an altered pool address or worker name, an inaccessible miner interface, repeated restarts, an inability to apply firmware updates, and a sharply reduced hashrate as warning signs of compromised firmware. The same guidance recommends isolating the device from other network equipment, using manufacturer-verified firmware, and changing the miner's login password after any third-party repair—practices that are particularly relevant for a unit of unknown history.

FAQ

Can I use the same worker name the previous owner used?

The worker-name segment after the account identifier is only a device label within your own account, so reusing a label like asic01 is not a security concern. What matters is that the userID portion of the worker name corresponds to your own ViaBTC account, not the previous owner's.

Is a mining pool password the same as my ViaBTC account password?

No. The password field in the ASIC's pool configuration is a mining-connection value, which ViaBTC lists as optional for BTC mining; it is unrelated to the account password or two-factor authentication used to sign in and manage withdrawals.

Why does the ASIC show a hashrate but the pool dashboard shows none yet?

The ASIC's displayed hashrate is a local, device-side reading and can appear immediately. The pool’s Workers page reflects an estimate based on shares actually received. ViaBTC’s BTC setup guide advises checking after around 10–15 minutes of stable operation, but this is not a guaranteed update deadline. If the dashboard still shows no activity, check the connection and worker settings using the troubleshooting steps above.

Does entering a BTC withdrawal address into the worker field do anything?

It does not configure your payout address. For ViaBTC, use userID.workerID; entering a wallet address instead is an incorrect configuration and should not be expected to credit your account. Configure the withdrawal address separately in the account’s payout settings.

Is a factory reset enough to make a used ASIC safe to use?

A factory reset clears stored configuration, including a previous owner's pool and worker settings, on models that support it. It does not guarantee the removal of unauthorized firmware; a device suspected of running altered firmware may require manufacturer-specific recovery steps.

References

• ViaBTC Help Center, "BTC Mining"
• ViaBTC Help Center, "What is Miner Virus and How to Deal with it"
• ViaBTC Help Center, "What Is Auto Withdrawal? How to Set Up and Manage It"
• ViaBTC Help Center, "How to Set Up 2FA (Two-Factor Authentication)"
• Bitmain Support, "How to set up a new S19/S19 Pro"
• Bitcoin Developer Documentation, "Mining"