Starting pool mining with ViaBTC requires four working parts: compatible ASIC hardware, the correct Stratum address, a valid worker name, and a payment method. For BTC in 2026, ViaBTC lists port 3333 with 443 as failover, while workers use the userID.workerID format with up to 64 lowercase letters or numbers in the worker ID. PPS+ charges 4% on the block-reward portion and 2% on the transaction-fee portion; PPLNS charges 2%. A miner should be evaluated through accepted shares, pool-side hashrate, reject rate, electricity use, temperature, and uptime rather than the ASIC’s local hashrate alone.
Before opening a miner dashboard, match the coin to the machine. BTC uses SHA-256, so mining it requires SHA-256 ASIC hardware; an ordinary desktop or mobile phone is not a practical substitute. ViaBTC’s 2026 guidance states that Proof-of-Work mining requires dedicated mining equipment plus stable power, Internet access, cooling equipment, and an environment with suitable temperature and humidity.
Power should be measured before the first pool connection. A 3,200 W ASIC running for 24 hours consumes 76.8 kWh per day and about 2,304 kWh over 30 days. At $0.08/kWh, electricity costs about $184.32 per month; at $0.15/kWh, it reaches $345.60 before ventilation, maintenance, hosting, or pool charges are included.
Uptime changes the same calculation. A machine operating at 95% uptime loses about 36 hours during a 30-day month. If the ASIC would otherwise consume 3.2 kW continuously, those 36 hours represent 115.2 kWh of idle production time, while fixed hosting or equipment costs may continue.
That operating cost leads directly to connection setup. ViaBTC’s August 2026 pool information lists global BTC Stratum connections on port 3333, with port 443 available as failover. European BTC connections and SSL addresses are also published, so miners should use the current official pool information rather than copying an endpoint from a 2024 or 2025 tutorial.
The worker field is separate from the pool address. ViaBTC’s BTC guide uses the userID.workerID structure and allows the worker ID to contain lowercase letters and numbers within a 64-character limit. The password is optional, so a worker may be organized as account.r01, account.r02, or account.r03 without creating separate ViaBTC accounts.
A site with 24 ASICs can make the naming structure more useful by matching each worker to a physical position. Names such as account.a01, account.a02, and account.b01 let an operator connect a pool-side problem with a particular rack or machine, instead of walking through all 24 units to identify one that stopped submitting shares.
The miner interface normally asks for a pool URL, worker, and password. ViaBTC uses Antminer as one example and directs users to Miner Configuration, followed by Save & Apply. Its guide also recommends entering multiple ports so the machine can move to another connection if the first connection stops responding.
Local hashrate is calculated by the mining machine, while pool-side hashrate is estimated from shares received by the pool. Short-term readings therefore do not need to be identical.
A 100 TH/s ASIC may show 100 TH/s locally while the pool displays 94 TH/s during a short measurement period. A persistent difference of 10% or more deserves closer checking for rejected shares, overheating, Internet interruptions, hardware errors, unstable frequency settings, or repeated pool reconnections.
ViaBTC provides real-time hashrate monitoring, hashrate alerts, miner grouping, and watcher functions. For a 50-machine operation, one offline unit represents 2% of the machine count. Watching only the combined hashrate makes a single failed miner easier to overlook than checking worker-level status and alerts.
Payment settings affect how credited mining output is distributed. ViaBTC’s May 2026 documentation lists PPS+ and PPLNS as its two payment methods after SOLO was discontinued on May 20, 2026. BTC supports both PPS+ and PPLNS, while some other supported coins are limited to PPLNS.
Under PPS+, the BTC block-reward portion uses PPS and carries a 4% fee. ViaBTC states that this portion is allocated every hour using current difficulty. The transaction-fee portion is handled through PPLNS and carries a 2% fee, so the two parts of a PPS+ payout are not calculated in the same way.
PPLNS uses a 2% fee for the block reward plus transaction fees. ViaBTC states that allocation is based on the miner’s share of pool hashrate across the last 5 difficulty rounds when a mined block reaches 6 confirmations. Daily amounts can therefore vary more because payment depends on blocks actually produced by the pool.
| Item | Current ViaBTC BTC detail |
|---|---|
| Main Stratum port | 3333 |
| Failover port | 443 |
| Worker structure | userID.workerID |
| Worker ID limit | 64 characters |
| PPS+ block-reward fee | 4% |
| PPS+ transaction-fee component | 2% |
| PPLNS fee | 2% |
| PPLNS measurement period | Last 5 difficulty rounds |
| Block confirmation point | 6 confirmations |
The numbers in the table also explain why a correctly connected machine may produce different daily amounts without any configuration change. ViaBTC notes in its 2026 documentation that mining difficulty changes over time, and higher difficulty reduces output for the same hashrate. Transaction fees also vary and affect the fee portion distributed to miners.
For example, a miner’s hardware may remain at 100 TH/s while network difficulty rises 8%. Holding every other input constant, the same hashrate represents a smaller share of the network’s computational work. Looking only at the ASIC display would not explain the lower credited amount, because the machine itself may still be operating normally.
Electricity efficiency adds another comparison. If one 100 TH/s ASIC draws 3,000 W and another uses 3,500 W, the figures are 30 J/TH and 35 J/TH. The 3,000 W machine consumes about 14.3% less electricity for the same nominal hashrate and saves 360 kWh during 30 days of uninterrupted operation.
At $0.10/kWh, that 360 kWh difference equals $36 each month per machine. Across 20 identical units, the difference becomes 7,200 kWh and $720 over 30 days. Cooling requirements can widen the gap because additional electrical input eventually becomes additional heat that has to be removed from the mining area.
Share acceptance deserves the same attention. An ASIC reporting 100 TH/s with a 2% rejected-share rate is not delivering the same accepted work as a machine with the same hashrate and a 0.3% rejection rate. Network latency, connection stability, firmware configuration, and hardware condition can all affect how much submitted work is accepted.
That is where ViaBTC Crypto Mining account monitoring becomes useful. The dashboard can be used to compare individual worker status, recent hashrate, credited mining records, and machine availability instead of treating the account as a place that is checked only when coins are withdrawn.
A 50-unit site makes the difference easy to quantify. If every machine provides 100 TH/s, installed hashrate is 5 PH/s. One machine being offline removes 100 TH/s, or 2%; five machines being offline removes 500 TH/s, or 10%. Worker grouping makes those individual outages easier to locate.
Withdrawals come after stable share submission has been confirmed. ViaBTC’s May 2026 guide lists four methods: Auto Withdrawal, Normal Transfer, Inter-User Transfer, and Transfer to CoinEx. Auto Withdrawal is listed with zero withdrawal fee and daily processing between 10:00 and 18:00 UTC+8, while Normal Transfer can be initiated at other times and may include a fee.
Inter-User Transfer and Transfer to CoinEx are described by ViaBTC as requiring zero blockchain confirmations and zero transfer fee within their supported transfer process. Before selecting any method, miners still need to confirm the receiving address, blockchain network, current minimum amount, account security settings, and current transfer rules.
A worker-name mistake affects where mining work is credited. A withdrawal-address mistake affects where transferred assets go, so the two checks should never be treated as the same setup task.
Troubleshooting should therefore start at the mining connection and move outward. If a worker remains offline for 15 minutes, check the ASIC algorithm, current Stratum host, port, userID.workerID entry, Internet connection, DNS resolution, temperatures, and system log before changing firmware or performance settings.
If the first endpoint fails, test the published failover port rather than changing several settings together. ViaBTC specifically recommends multiple ports because a miner can switch when one connection becomes unavailable. A machine reconnecting repeatedly may still show local hashrate even while fewer valid shares reach the pool.
A practical operating record should cover at least 7 to 30 days and include average pool-side hashrate, uptime percentage, reject percentage, kWh consumed, credited coins, pool charges, and transfer costs. A machine at 98% uptime loses about 14.4 hours over 30 days; at 92%, lost operating time rises to about 57.6 hours.
The same record helps when adding more ASICs. After one miner remains stable across several payment cycles, its pool settings can be copied to other units while giving each machine a separate worker ID. In a 20-machine installation, mapping every worker to a rack position, electrical circuit, and serial number makes pool records easier to compare with power-meter readings and maintenance history.