Behind Low Orphan Rates and Hourly Settlement: A Decade of Engineering at ViaBTC
2026-11-19 07:22

By the ViaBTC Engineering Team

 

The machines at a mining farm are running as usual, but the hashrate chart on the pool dashboard has dropped. Naturally, miners want to know whether their earnings are affected and whether their equipment needs attention. Our job is to check their connections, mining jobs, and share submissions, identify the cause, and recommend what to do next.

 

ViaBTC launched in 2016, and we’ve now been operating for ten years. Monitoring hashrate, maintaining nodes around the world, and troubleshooting issues are part of our daily work. ViaBTC’s account-based model allows miners to hold and manage their earnings on the platform. Supporting that model brings additional responsibilities: beyond keeping miners connected, we also maintain reward settlement systems and wallets for each supported cryptocurrency, and protect assets held in user accounts.

 

Why Has a Miner’s Hashrate Dropped?

When we see a drop in hashrate, we start with share submission records. Have any machines disconnected? Are shares still being submitted consistently? Which submissions have been rejected? The hashrate shown by the pool is estimated from valid shares submitted over a given period and their associated difficulty. Short-term changes in submission counts can cause the chart to fluctuate. We use these records to determine whether the change is normal statistical variation or an equipment, connection, or pool service issue affecting actual mining activity.

 

We also check whether machines are receiving new jobs promptly. In Bitcoin mining, for example, when a new block is found on the network, machines need to start working on top of that block. If job delivery is delayed, machines that are still connected may keep working on an outdated job. That work may no longer count as a valid contribution, wasting electricity and computing resources.

 

During troubleshooting, we trace the process through job delivery, share validation, and reward settlement to establish where the problem occurred and which users were affected. We handle issues within the pool service ourselves. When miners need to take action, we recommend specific equipment checks or connection adjustments, reducing unnecessary restarts and configuration changes.

 

From Disconnections to Orphan Blocks: How Do We Reduce Mining Losses?

Sometimes machines are working normally and their pool addresses have not changed, yet their connections begin dropping repeatedly. In these cases, we examine network performance in the affected region for issues such as ISP routing changes or congestion.

 

After deploying our global nodes, we continue tracking latency, disconnections, and share submissions across regions. Some issues affect only one region or network route and account for such a small portion of overall activity that they are easy to miss in platform-wide data. We therefore examine these changes by region and route, investigate persistently unstable connections, and adjust our node deployment and connection setup based on what we find.

 

We also regularly advise miners to configure one or two official backup pool addresses where their equipment supports them. If the primary connection becomes unavailable, the machines can try another endpoint according to their settings. A working backup connection lets them resume mining with less time spent waiting for manual intervention.

 

Communication between the pool and the blockchain network also requires ongoing maintenance. When we receive information about a new block, we need to update mining jobs as quickly as possible. When we find a block, we need to broadcast it promptly. Propagation delays can allow a competing block at the same height to be accepted first, leaving ours orphaned and without the corresponding reward.

 

To address this, we developed our own Bitcoin client and optimized the underlying bitpeer and blockmaster modules to speed up block propagation. These engineering improvements have helped ViaBTC maintain the industry’s lowest orphan rate and reduce earnings lost to propagation delays. Miners have already committed electricity and computing resources to that work. We aim to minimize how much of that investment is lost through connection and propagation issues.

 

Hourly Settlement: How Do We Manage Data and Control Risk?

ViaBTC settles PPS+ rewards hourly, making it one of the fastest pools in the industry to credit mining rewards. Miners can promptly manage their credited earnings. For us, this means completing a processing cycle every hour: checking miners’ contributions, network difficulty changes, and block data, then calculating and recording the rewards to be distributed. More frequent settlement leaves less time for each round of processing and reconciliation. We need to maintain accuracy while preventing data backlogs from delaying reward distribution.

 

When miners bring additional machines online or take some offline during the day, their contributions change. We calculate rewards from valid shares and their associated difficulty in each period, retaining detailed records for later review and reconciliation. Hourly settlement generates more settlement records and makes data management more complex. We have optimized our data processing and storage systems to securely retain large volumes of historical records and allow those records to be retrieved and reconciled efficiently.

 

Hourly reward distribution also means that an attacker who obtains rewards through malicious activity may be able to withdraw them sooner, leaving us less time to detect and respond to the risk. Our team therefore continuously monitors unusual hashrate and submission behavior to identify and address hashrate-based attacks promptly, prevent illicit reward withdrawals, and protect the pool and legitimate users.

 

Once earnings are credited, miners can retain their balance, set up automatic withdrawals, or transfer assets out manually. We maintain wallet nodes for each supported cryptocurrency and reconcile account deposit and withdrawal records with actual transaction status so that balance changes can be traced. For example, if a miner reports that a withdrawal has not reached an external wallet, we first check its progress. If it is still being processed on the platform, we investigate delays or errors in that process. If it has already been broadcast to the network, we check its confirmation status and explain where the transaction stands and whether further confirmations are needed.

 

Our routine work includes checking node synchronization and deposit and withdrawal transactions, as well as keeping up with wallet software updates. Ahead of a blockchain protocol upgrade, we also verify that deposits for each affected cryptocurrency will be recognized correctly and that withdrawal transactions can be processed under the new rules. We plan maintenance accordingly to reduce the impact on asset services.

 

How Do We Protect User Assets?

When miners keep their earnings in their accounts, we are responsible for protecting those assets. ViaBTC uses asset security measures on par with those used by leading exchanges, including cold wallets and multisignature controls, supported by real-time monitoring and risk reviews.

 

Before making significant configuration changes, we verify access permissions and review the proposed changes. We keep records throughout the process to reduce unauthorized changes and operational errors and make problems easier to trace. Development and operations environments are kept separate, and the production environment uses dedicated equipment to reduce exposure to external risks. We also conduct regular security audits, use penetration testing to identify vulnerabilities, and run stress tests to assess system capacity. We address any issues we find and test again to verify the fixes.

 

ViaBTC has completed SOC 2 Type I and Type II audits. Alongside our internal checks, independent auditors have reviewed our systems and operating procedures for security, availability, and confidentiality.

 

For user accounts, we offer two-factor authentication options such as Google Authenticator (GA), and we encourage miners to enable two-factor authentication for login after linking their authenticator. Even if a password is compromised, an additional identity check is still required to log in, reducing the risk of account takeover. ViaBTC has also added passkeys to its two-factor authentication options, with support for biometric verification to make authentication more convenient. We remind miners to keep their authenticator backup keys secure and never share verification codes.

 

Protocol Upgrades Should Be Seamless for Miners

Before a blockchain protocol upgrade, we test job generation, block submission, reward processing, and wallet functionality. We pay particular attention to the transition as the new rules take effect, checking that machines can continue receiving jobs and submitting shares, and that reward settlement, deposits, and withdrawals continue to operate normally.

 

The recent Zcash NU7 upgrade is one example. Although the technical details can be complex, we completed the necessary changes, testing, and deployment on the pool side in advance, then monitored operations as the upgrade took effect. Miners could continue mining through the transition without changing their configurations, taking any additional steps, or needing to understand the technical details.

 

Over the past ten years, each round of troubleshooting, maintenance, and upgrades has added to our experience and helped us improve both our systems and the way we resolve problems. From faster block propagation to hourly settlement and preparation for protocol upgrades, the results show up in miners’ everyday experience: fewer losses from connection issues, timely access to earnings, and the confidence to keep mining as network rules change. These are the outcomes that continue to guide our engineering work.