What is Equihash?
Equihash is a memory-hard proof-of-work algorithm based on the generalized birthday problem. Zcash uses Equihash with n = 200 and k = 9, commonly written as Equihash 200/9. For ZEC miners, the practical starting point is to confirm that a device explicitly supports this variant or that its manufacturer lists ZEC as a supported coin, then verify its firmware, pool settings, and installation requirements.
The parameters n and k define the structure of the computational puzzle and affect the memory and computational work needed to solve it. They are distinct from the network difficulty target. The original research describes memory-hardness as a way to narrow the performance gap between general-purpose hardware and specialized hardware by making efficient solving depend on memory capacity and bandwidth, not only raw computational throughput (Biryukov and Khovratovich, Equihash).
Equihash is parameterized rather than one fixed configuration. Changing n or k changes the work involved in finding a valid solution, so a hashrate figure reported in Sol/s (solutions per second) must be interpreted in the context of the specific variant. Two devices advertised as “Equihash miners” are not necessarily doing comparable work.
Zcash's consensus rules specify Equihash 200/9 for both Mainnet and Testnet. Its proof-of-work check requires a valid Equihash solution and a separate check that the block header hash meets the network's difficulty target. These are two distinct conditions, not a single combined test (Zcash Protocol Specification, Sections 7.7.1–7.7.2).
Why parameters matter
“Supports Equihash” is an incomplete compatibility claim. Variants such as 144/5 have different memory requirements and solution-search spaces from 200/9. Hardware or software designed for one parameter set does not automatically support another.
This distinction has two direct consequences:
- Consensus validity. A device that cannot generate Equihash 200/9 solutions cannot produce valid Zcash proof of work, regardless of its hashrate on another parameter set.
- Hashrate comparability. A Sol/s figure for Equihash 144/5 cannot be treated as equivalent to the same numerical figure for Equihash 200/9. Comparisons need to account for the algorithm variant and measurement conditions; different coin names alone do not determine whether the figures are comparable.
The parameter pair is therefore a necessary starting point for compatibility, while explicit manufacturer support for ZEC provides a practical way to identify suitable equipment.
ASIC and software compatibility
Algorithm support and pool connectivity are separate checks. First establish that the hardware and its installed firmware support ZEC mining. Then verify that the firmware supports the pool's connection protocol and worker-credential format.
Review compatibility information for the firmware version actually installed, especially on secondhand equipment or devices running custom firmware. When an upgrade is planned, consult the manufacturer's release notes and confirm valid-share submission after the change. A firmware change should not be assumed to make an ASIC support a different Equihash parameter set.
Physical and electrical requirements also matter independently of algorithm support. Input voltage, input current, cooling, noise, and operating temperature must suit the intended site.
As a concrete example, BITMAIN's Z15 Pro specification page identifies the miner's algorithm as Equihash and explicitly lists ZEC among its supported coins. It gives typical figures of 840 KSol/s, 2,780 W power on wall at 25°C, and 3.31 J/KSol wall efficiency at 25°C, with stated variation of ±3% for hashrate and ±5% for power and efficiency (BITMAIN, Z15 Pro Specifications).
The same page specifies 200–240 V AC input and lists an input current of 20 A, with a footnote specifying two AC inputs, 10 A per input cable. This input arrangement should be included when assessing the site's electrical requirements; the listed current alone is not a complete circuit-design specification.
These performance figures are manufacturer typical values under stated conditions, not guaranteed results at a particular site. Actual hashrate and power draw can differ with operating conditions and firmware settings. A model-specific manufacturer specification is therefore more useful for a purchase decision than a marketplace listing that says only “Equihash miner.”
Pool setup implications
Once hardware compatibility is confirmed, configure the pool connection separately. A compatible ASIC still needs the correct connection settings to submit valid shares.
ViaBTC's ZEC mining documentation lists standard endpoints at stratum+tcp://mining.viabtc.io:3002 and stratum+tcp://mining.viabtc.io:302, with smart-mining endpoints on separate ports. It recommends configuring multiple ports so the miner can switch to a backup if the primary connection fails. The documented worker-name format is userID.workerID; the ASIC setup instructions allow any password and state that the password is optional (ViaBTC Help Center, ZEC Mining).
After connecting, monitor the miner's locally reported hashrate, the pool's hashrate estimate, valid and rejected shares, and any rejection reasons. The pool's estimate is based on submitted valid shares over its measurement window, so it can differ from the local reading. Rejected shares can include stale, invalid, or duplicate submissions; the reason helps distinguish latency, configuration problems, and possible hardware faults.
Payout selection is a separate decision. ViaBTC documents PPS+ and PPLNS payment methods. Under PPS+, the block-reward portion follows Pay-Per-Share logic, while transaction fees are allocated using PPLNS logic. Under PPLNS, rewards depend on the pool's actual block discovery and the miner's qualifying contribution (ViaBTC Help Center, PPS+ and PPLNS).
The PPS component reduces the effect of pool block-finding luck on that portion of income because payment for valid shares does not depend on whether the pool finds a block. It does not fix total earnings: network difficulty, uptime, valid-share submission, and the transaction fees collected by the pool still affect results.
Hardware purchase checks
Before purchasing or deploying an Equihash ASIC for Zcash:
- Confirm ZEC support. Look for explicit Equihash 200/9 support or ZEC in the manufacturer's supported-coin list.
- Check the installed firmware. Verify the version and its compatibility information, particularly for secondhand or custom-firmware devices. Review release notes before upgrading.
- Match the site to the machine. Check voltage, input arrangement, current, circuit capacity, cooling, noise, and operating temperature requirements.
- Read performance figures in context. Note the manufacturer's test conditions and variation ranges when comparing hashrate, power, and efficiency.
- Verify pool configuration and operation. Use the pool's current official connection instructions, configure backup connections where supported, and confirm accepted shares after setup.
- Understand settlement. Choose a payout method based on its mechanics, separately from hardware and connection compatibility.
FAQ
Is every Equihash-labeled ASIC able to mine Zcash?
Not necessarily. Zcash requires Equihash with n = 200 and k = 9. Look for explicit Equihash 200/9 support or ZEC in the manufacturer's supported-coin list, then verify the installed firmware and pool setup.
Can I directly compare hashrate figures across different Equihash parameter sets?
No. Sol/s figures for different parameter sets, such as 200/9 and 144/5, represent different computational work and should not be treated as equivalent. When comparing figures for the same variant, check that the measurement conditions are comparable too.
Does a manufacturer's listed hashrate and power figure guarantee what I will see at my site?
No. Manufacturer specifications are typical values under stated test conditions, generally with an explicit variation range. Actual results can differ with operating conditions and firmware settings.
How does PPS+ affect earnings stability compared with PPLNS?
The PPS portion of PPS+ reduces exposure to pool block-finding luck by paying for valid shares independently of whether the pool finds a block. Transaction fees remain under PPLNS logic, and total earnings can still change with network difficulty, uptime, valid-share submission, and the fees collected by the pool.
Where should I get current ZEC pool connection details?
Use the pool's current official help documentation. Endpoints, ports, and worker-naming requirements can change, so cached configurations and third-party guides may be out of date.