Ethereum ProgPoW miner with OpenCL, CUDA and stratum support
Progminer is an ProgPoW GPU mining worker: with progminer you can mine every coin which relies on an ProgPoW Proof of Work thus including Ethereum ProgPoW and others. This is the actively maintained version of progminer. It originates from ethminer project. Check the original ProgPoW implementation and EIP-1057 for specification.
- First commercial ProgPoW miner software for miners.
- OpenCL mining
- Nvidia CUDA mining
- realistic benchmarking against arbitrary epoch/DAG/blocknumber
- on-GPU DAG generation (no more DAG files on disk)
- stratum mining without proxy
- OpenCL devices picking
- farm failover (getwork + stratum)
- Ethereum-based ProgPoW implementations supported only, doesn't support previous ethash version or Bitcoin-based forks.
Standalone executables for Linux, macOS and Windows are provided in the Releases section. Download an archive for your operating system and unpack the content to a place accessible from command line. The progminer is ready to go.
Builds | Release | Date |
---|---|---|
Last |
For AMD-only rigs please use the version with -amd tagged , cuda version wouldn't work for you rig.
If you have trouble with missing .dll or CUDA errors please install the latest version of CUDA driver or report to project maintainers.
The progminer is a command line program. This means you launch it either from a Windows command prompt or Linux console, or create shortcuts to predefined command lines using a Linux Bash script or Windows batch/cmd file. For a full list of available command, please run:
progminer --help
Note that Progminer doesn't support mining Bitcoin-based ProgPoW implementations such as Bitcoin Interest, etc. (See https://github.com/gangnamtestnet/progminer/issues/9 for more information)
Connecting to 2miners.com:
./progminer -P stratum1+tcp://[email protected]:2020
or
progminer.exe -P stratum1+tcp://[email protected]:2020
The list of current and past maintainers, authors and contributors to the progminer project. Ordered alphabetically. Contributors statistics since 2015-08-20.
Name | Contact | |
---|---|---|
Andrea Lanfranchi | @AndreaLanfranchi | ETH: 0xa7e593bde6b5900262cf94e4d75fb040f7ff4727 |
EoD | @EoD | |
Genoil | @Genoil | |
goobur | @goobur | |
Marius van der Wijden | @MariusVanDerWijden | ETH: 0x57d22b967c9dc64e5577f37edf1514c2d8985099 |
Paweł Bylica | @chfast | ETH: 0x8FB24C5b5a75887b429d886DBb57fd053D4CF3a2 |
Philipp Andreas | @smurfy | |
Stefan Oberhumer | @StefanOberhumer | |
ifdefelse | @ifdefelse | |
Won-Kyu Park | @hackmod | ETH: 0x89307cb2fa6b9c571ab0d7408ab191a2fbefae0a |
Ikmyeong Na | @naikmyeong |
All bug reports, pull requests and code reviews are very much welcome.
Licensed under the GNU General Public License, Version 3.
The new WDDM 2.x driver on Windows 10 uses a different way of addressing the GPU. This is good for a lot of things, but not for ETH mining.
- For Kepler GPUs: I actually don't know. Please let me know what works best for good old Kepler.
- For Maxwell 1 GPUs: Unfortunately the issue is a bit more serious on the GTX750Ti, already causing suboptimal performance on Win7 and Linux. Apparently about 4MH/s can still be reached on Linux, which, depending on ETH price, could still be profitable, considering the relatively low power draw.
- For Maxwell 2 GPUs: There is a way of mining ETH at Win7/8/Linux speeds on Win10, by downgrading the GPU driver to a Win7 one (350.12 recommended) and using a build that was created using CUDA 6.5.
- For Pascal GPUs: You have to use the latest WDDM 2.1 compatible drivers in combination with Windows 10 Anniversary edition in order to get the full potential of your Pascal GPU.
Because of the GDDR5X memory, which can't be fully utilized for ETH mining (yet).
Only GCN 1.0 GPUs (78x0, 79x0, 270, 280), but in a different way. You'll see that on each new epoch (30K blocks), the hashrate will go down a little bit.
Not really, your VRAM must be above the DAG size (Currently about 2.15 GB.) to get best performance. Without it severe hash loss will occur.
The default parameters are fine in most scenario's (CUDA). For OpenCL it varies a bit more. Just play around with the numbers and use powers of 2. GPU's like powers of 2.
@davilizh made improvements to the CUDA kernel hashing process and added this flag to allow changing the number of tasks it runs in parallel. These improvements were optimised for GTX 1060 GPUs which saw a large increase in hashrate, GTX 1070 and GTX 1080/Ti GPUs saw some, but less, improvement. The default value is 4 (which does not need to be set with the flag) and in most cases this will provide the best performance.
What is progminer's relationship with Genoil's fork?
Genoil's fork was the original source of this version, but as Genoil is no longer consistently maintaining that fork it became almost impossible for developers to get new code merged there. In the interests of progressing development without waiting for reviews this fork should be considered the active one and Genoil's as legacy code.
No, use geth, the go program made for ethereum by ethereum.
There is an environment var CUDA_DEVICE_ORDER
which tells the Nvidia CUDA driver how to enumerates the graphic cards.
The following values are valid:
FASTEST_FIRST
(Default) - causes CUDA to guess which device is fastest using a simple heuristic.PCI_BUS_ID
- orders devices by PCI bus ID in ascending order.
To prevent some unwanted changes in the order of your CUDA devices you might set the environment variable to PCI_BUS_ID
.
This can be done with one of the 2 ways:
-
Linux:
- Adapt the
/etc/environment
file and add a lineCUDA_DEVICE_ORDER=PCI_BUS_ID
- Adapt your start script launching progminer and add a line
export CUDA_DEVICE_ORDER=PCI_BUS_ID
- Adapt the
-
Windows:
- Adapt your environment using the control panel (just search
setting environment windows control panel
using your favorite search engine) - Adapt your start (.bat) file launching progminer and add a line
set CUDA_DEVICE_ORDER=PCI_BUS_ID
orsetx CUDA_DEVICE_ORDER PCI_BUS_ID
. For more info aboutset
see here, for more info aboutsetx
see here
- Adapt your environment using the control panel (just search
Error: Insufficient CUDA driver: 9010
You have to upgrade your Nvidia drivers. On Linux, install nvidia-396
package or newer.