Introduction
Operators frequently assume that pool compatibility is a property of the ASIC model itself — that any Antminer, Whatsminer, or Avalon unit of a given generation will work with any pool offering the same coin. In practice, pool connectivity depends on matching the mining algorithm, the protocol and transport supported by the installed firmware, and the connection and account format required by the pool. If the existing firmware supports the target pool, connecting usually requires configuration rather than a firmware change. When choosing or replacing firmware, compatibility with the exact miner model and control-board revision is an additional prerequisite. Misunderstanding any one of these layers is a common source of failed connections, rejected shares, or a miner that appears "online" locally but never registers on the pool dashboard.
This article separates those layers and explains what each one controls, using ViaBTC's published Bitcoin mining configuration as a concrete reference point.
What ASIC Firmware Actually Does
Firmware is the embedded software running on a miner's control board. It manages chip initialization, frequency and voltage tuning, fan control, temperature monitoring, and — relevant here — the network connection to a mining pool. Firmware translates the pool's job data into work the ASIC chips can process, and it packages completed work (shares) into the format the pool's Stratum server expects.
Firmware does not determine whether a pool will credit rewards for submitted work; that is a pool-side function. The pool independently validates each submitted share against its own share-difficulty target and applies its payout logic. This distinction matters because firmware-reported figures — local hashrate, chip temperature, fan speed — describe device behavior, while pool-reported figures — accepted shares, rejected shares, pool-estimated hashrate, and credited earnings — describe how the pool has processed that device's submissions. These two sets of data are related but should not be treated as interchangeable, and neither should be used to infer the other without matching measurement windows.
Defining Pool Compatibility: Three Connection Requirements
"Compatible with a pool" is not a single condition. It requires a match across three areas. Firmware installation compatibility is a separate prerequisite when selecting or replacing firmware.
Algorithm compatibility
The ASIC's chip design, the firmware, and the pool endpoint must all target the same mining algorithm. A SHA-256 Bitcoin ASIC can only connect meaningfully to a SHA-256 endpoint; pointing its firmware at a different algorithm's Stratum URL will not make the hardware capable of mining that algorithm.
Protocol and transport compatibility
The firmware must support whatever protocol and transport the pool offers at that endpoint. Most pools, including ViaBTC, publish standard Stratum V1 over TCP. Some firmware builds additionally support encrypted transport (stratum+tls://) or the newer Stratum V2 protocol. If the firmware's connection interface does not recognize the URL scheme a pool requires, the connection will fail regardless of whether the algorithm and account details are correct.
Connection and account-format compatibility
Even when the protocol matches, the firmware must send credentials in the exact format the pool expects. ViaBTC's Bitcoin mining configuration uses the userID.workerID worker-naming convention, with worker IDs limited to a maximum of 64 lowercase letters and numbers. Firmware that auto-generates worker names using unsupported characters, or that truncates the identifier differently, can cause a miner to connect at the network level while still being misassigned or rejected at the account level.
Stock Firmware, Custom Firmware, and the Pool Layer
Firmware and mining pools perform different functions in the mining stack, even when the same company provides both. Most modern firmware — whether factory-installed or third-party — is not restricted to a single pool. Braiins, for example, documents that its Braiins OS firmware supports connecting to any pool and remains backward-compatible with Stratum V1, including through a translation layer when a pool does not offer native Stratum V2. This is a vendor-specific documented capability, not a universal property of all third-party firmware; different firmware projects support different protocol versions, transport options, and pool-failover behavior, so the supported feature list should be checked against the specific firmware version in use rather than assumed from the vendor's general reputation.
For a standard configuration — for instance, an Antminer running stock firmware pointed at ViaBTC's Bitcoin pool — compatibility begins with the pool's published connection method rather than with any special integration between the hardware brand and the pool brand. ViaBTC's current guide lists a primary Stratum endpoint at stratum+tcp://btc.viabtc.io:3333 and an alternate endpoint on port 443, and it recommends configuring more than one pool entry so the miner can fail over if a connection drops. Both published URLs use stratum+tcp://; port 443 alone does not indicate TLS encryption. The relevant compatibility question is simply whether the firmware's pool-configuration fields accept this URL format, port, and worker syntax — not whether the firmware carries any particular brand name.
Stratum V1, TLS, and Stratum V2: What Actually Changes
Stratum V1 remains the connection method published by most pools and supported by most deployed firmware. Two more recent developments affect compatibility planning without replacing V1 outright.
First, some firmware has added support for TLS-encrypted Stratum connections. LuxOS, for example, added support for stratum+tls:// connections in its firmware changelog dated March 2, 2026. This illustrates a point that applies generally: transport encryption is not solely a pool-side feature. Both the pool's endpoint and the miner's firmware must support the same connection scheme, or the encrypted option simply will not be available in that firmware's configuration menu.
Second, the Stratum V2 protocol introduces a redesigned Mining Protocol between miner and pool (or miner and proxy). The Stratum V2 Reference Implementation 1.0.0, released March 21, 2024, described two distinct interoperability paths: firmware built with native Stratum V2 support can connect directly to an SV2-capable pool, while firmware that only supports Stratum V1 can reach an SV2 pool through a Translation Proxy. These are operationally different arrangements. Native Stratum V2 firmware connecting to a compatible V2 pool does not need a V1/V2 translation proxy; proxy-based compatibility requires deploying and maintaining a separate translation component. Other V2 capabilities, such as constructing and declaring custom block templates, may involve additional components. An article or operator evaluating "Stratum V2 readiness" should treat these as two different questions rather than a single yes/no compatibility check.
Why the Model Number Alone Doesn't Guarantee Firmware Installation Compatibility
When selecting or replacing firmware, the image and installation method must support the miner's exact hardware. This check is separate from configuring a pool connection in firmware that already runs on the device.
A given ASIC model name can correspond to more than one control-board revision, and firmware images are generally built for a specific board type — for example, distinct images for AML-, CV-, BB-, or 7007-based control boards within the same product family. Installing an image intended for the wrong board revision can leave the miner non-functional rather than simply failing to connect to a pool.
Security restrictions add a further constraint. Bitmain's documentation on its security firmware states that covered firmware uses signature verification and disables SSH access on affected models, and it warns that loading unauthorized third-party firmware onto these units can cause malfunction and may void the warranty. This does not amount to a blanket prohibition on all third-party firmware across every ASIC model; the accurate conclusion is narrower and model-specific: installation paths, available recovery options, and warranty terms differ by manufacturer, model, control-board revision, and the firmware already installed on the unit. Before changing firmware, it is worth confirming the firmware vendor's supported model and control-board list, along with its recovery procedure, since "the pool will accept this connection" and "this firmware image can be installed on this board" are two separate questions.
Configuring a Miner for a Pool: Practical Points to Check
The following points reflect configuration factors rather than a mandatory procedure, and their relevance depends on the specific firmware and pool involved.
- Confirm the ASIC's mining algorithm and exact model/control-board revision before selecting any firmware image.
- Check the firmware vendor's documentation for the hardware revisions and versions it supports.
- Copy the pool's currently published Stratum URL, port, and worker-naming format directly from official documentation rather than from older tutorials or screenshots, since pool infrastructure can change over time.
- Verify whether the firmware supports the protocol and transport the pool requires at that endpoint, such as plain Stratum V1, TLS-encrypted Stratum, or native Stratum V2.
- Where the firmware supports multiple pool entries, configure a backup endpoint to reduce the impact of a single connection interruption.
- When comparing firmware-reported hashrate against pool-reported hashrate, use matched time windows, since the two are calculated differently and will not be numerically identical even under normal operation.
For ViaBTC specifically, the current Bitcoin mining setup guide is the authoritative reference for the primary and alternate endpoints, the worker-ID format, and recommended failover configuration, and it should be used in preference to reproducing settings from third-party sources.
FAQ
Does a firmware update change how much a miner earns from a pool?
Firmware updates can affect local hashrate stability, tuning behavior, and network connectivity, which in turn can affect how many valid shares a miner submits. Firmware does not itself rewrite the pool's payout rules. However, firmware developer fees, the allocation of hashrate to collect those fees, and any firmware-linked pool fee discounts can affect net earnings. Check the applicable firmware and pool terms, and evaluate credited earnings using the pool's account and payout records rather than local firmware readings alone.
Can any ASIC firmware connect to any Bitcoin mining pool?
Only if the firmware and the pool endpoint use a matching algorithm, protocol, and transport, and the firmware can transmit account credentials in the format the pool requires. A SHA-256 pool endpoint and SHA-256 firmware are necessary but not sufficient; connection syntax and worker-naming rules must also match.
Is Stratum V2 required to mine on ViaBTC or other major pools today?
No. Stratum V1 remains the standard published connection method for most pools, including ViaBTC's current Bitcoin endpoints. Stratum V2 support depends on both the firmware and the pool offering it, and adoption is still uneven across the industry as of this writing.
Why does my miner show a stable local hashrate but low pool-reported hashrate?
These two readings alone do not establish the cause. Short-term differences can reflect the randomness of share submissions or different measurement windows. Compare longer averages over matching periods first. If the gap persists, check rejected and stale shares, connection stability, hardware errors, and firmware or tuning settings. A stable local reading does not rule out a device-side problem. See ViaBTC's guidance on local and pool hashrate differences.
Is it safe to install third-party firmware on any ASIC model?
Installation feasibility and risk depend on the specific model, control-board revision, currently installed firmware, and the third-party firmware vendor's supported hardware list. Signed or security-restricted factory firmware can block or complicate certain installation paths, so vendor documentation should be checked before attempting a change.
References
- ViaBTC Help Center — BTC Mining configuration guide
- Stratum V2 — Protocol Overview
- Stratum V2 — Reference Implementation 1.0.0 announcement
- Bitmain — ANTMINER Security Firmwares Q&A
- Braiins — Braiins OS Firmware documentation
- Luxor — LuxOS Changelog
- ViaBTC Help Center — Why is the Hashrate Shown in the Mining Pool Lower than that of the Mining Machine?