The time has come
Yesterday, November 6, a significant event took place on the Ethereum Classic network — the 385 epoch came.
What is the significance of this event? With the onset of the 385 epoch, a number of problems were discovered that apply equally to both the Ethereum Classic network and the possible problems with the main mining coin — Ethereum.
Problems
First, DAG file size exceeded 4GB and some miners stopped working, for example the legendary Claymore ETH Dual Miner, the latest version of which v15.0 - was released back in August 2019.
Most miners have fixed the problem of working with a DAG file larger than 4 GB, you just need to update and use the latest version. Otherwise, miners may either not work at all, or send incorrect shares to the pool, and your worker will most likely be banned by the pool.
Secondly, the problem was found in the code of the Ethash Lib library, so the error is reproducible for both Ethereum Classic and Ethereum, and it can appear in many scenarios, and cause instability of the entire network as a whole.
You can read more about this in this article by our colleagues from 2miners.com.
Solving
To keep your Ethereum Classic mining workers running smoothly, update Hive OS and use the latest versions of miners. We remind you that if you exceed the 5% barrier of incorrect shares on the Hiveon ETC pool, your worker will be banned.
So, in order to avoid a ban on the pool due to invalid shares, which were produced by the version of the miner that does not work correctly with a DAG file of more than 4GB or the loss of money due to the idle worker due to non-working, miners need:
- If you use Claymore for mining ETC you should switch to another miner (see below miner testing for compatibility)
- If you use PhoenixMiner with AMD Navi change it to TeamRedMiner or lolMiner
- If you use another miner than update your miner to latest
Globally, we removed Claymore ETH Dual miner from the list of recommended miners for our Hiveon pool, and the pools with which we cooperate did the same.
Miners testing for compatibility with 385+ epoch
We tested ethash miners for AMD (tested on OpenCL versions 19.20, 19.30 and 20.30) and Nvidia (v455.38) for compatibility with the 385+ epoch.
We share the results with you:
AMD
Status | Miner | Notices |
---|---|---|
Claymore v15.0 | miner stops working with the “Pool sent wrong data, cannot set epoch, disconnect” error | |
EthMiner v0.19.0.1+nhfix | performance on Vega and Navi family isn’t optimal | |
Bminer v16.3.4 | miner is not working with DAG >4GB even on drivers v20.30 | |
lolMiner 1.12 | supports the “Zombie” mode | |
PhoenixMiner v5.1c | incorrect shares on the Navi family are possible | |
TeamRedMiner v0.7.17 | supports the “Zombie” mode | |
NBMiner v33.3 | ||
NanoMiner 1.13.0 | supports the “Zombie” mode | |
SRBMiner v0.5.5 |
NVIDIA
Status | Miner | Notices |
---|---|---|
Claymore v15.0 | miner stops working with the “Pool sent wrong data, cannot set epoch, disconnect” error | |
EthMiner v0.19.0.1+nhfix | ||
Bminer v16.3.4 | doesn’t support RTX 30xx | |
lolMiner 1.12 | supports the “Zombie” mode | |
PhoenixMiner v5.1c | ||
T-Rex v0.18.6 | the problem in the latest version was fixed, supports the “Zombie” mode | |
NBMiner v33.3 | ||
NanoMiner 1.13.0 | supports the “Zombie” mode | |
GMiner v2.29 | ||
TT-Miner v6.0.0 |