The latest version of Z-enemy 2.4 is available for CUDA 9.1, 9.2 and 10.0 for 64-bit versions of Windows, as well as for the binary files CUDA 9.0, CUDA 9.1, CUDA 9.2 and CUDA 10 for Linux (HiveOS, PiMP OS, EthOS and Ubuntu). Make sure you have the latest video driver installed for the version of CUDA you want to use – 388+ for 9.1, 397+ for 9.2 and 411+ for CUDA 10.0, although 415+ is recommended for better performance
z-enemy – The name of the program that will run our .bat file. Leave as is. The z-enemy.exe file must be located in the batch file folder as in the example above
x16r – specify the coin algorithm that we will mine
rvn.suprnova.cc – specify the address of the pool of the mined coin. A pool is an association of miners with the goal of finding the block as quickly as possible.
6667 – specify the port of the pool. You can find it on the pool page. Usually in the Getting Started section.
rgzrgz_leo – after the -u switch, the name of the worker or the address of the digital wallet is indicated. Since in our example the Suprnova pool, then the name of the worker must be indicated on it
rgzrgz_leo – password of the worker. Indicated after the dot
c=RVN – after the key c =, the token of the mined coin is indicated. If this is not indicated, then some pools do not understand which coin you want to mine.
-i 20 – miner work intensity. Available values are from 8 to 31
So, we examined all the most important command line arguments for launching the Z-enemy miner. You can already run the program and try to overclock the video cards to maximize profits. However, below, in this walkthrough, we will talk about absolutely all the settings for this program. This is useful for experienced users. In the meantime, we try to run the program and see what the miner’s console tells us.
First launch of Z-Enemy
Running the program, we see that the miner begins to tell us a lot of information:
NVIDIA CUDA 10.0 – means that version 10 of CUDA is installed. Cuda 10.0 – drivers version 415+, Cuda 9.2 – drivers 398+, Cuda 9.1 – old drivers 388+)
Dev fee is 1.0% – the program warns of a commission of 1%
URL: stratum+tcp://rvn.suprnova.cc:6667 – the address of the pool on which we will mine. We indicated it above
USER: rgzrgz_leo.rgzrgz_leo – worker and pool password, which we also specified in the batch file
PASS: c=RVN – mined token
Starting on stratum+tcp://rvn.suprnova.cc:6667 – the program starts connecting to the pool
GPU monitoring enabled (NVML) – the program launched an API for monitoring and managing various states of video cards
Mining ‘х!бг’ with 2 threads – mining process starts in two streams
Hashorder algorithm legend: legend of the algorithm. Because Since we work with x16r, the hash rate (speed) of production varies from low to high. This is due to the operation of the x16r algorithm (it consists of 16 different algorithms)
New difficulty: 32 (0.12508) – the program picked up the difficulty of mining
GPU#1: Intensity set to 20 – intensity 20, which we set in a batch file
Shares: 1 (А:100.00%, R:0.00%), Diff:0.142, 25.51 MH/S, 90ms – OK, the program sent the ball (solution) to the pool. Note that miners are credited with money for balls, and not for anything else. The more the ball will be sent to the pool, the greater the reward.
GPU#1: MSI GTX 1080 Ti – 31.26 MH/S [T:61C, F:88%, P:276W, E:0.113MH/W] – One of the video cards works with a hash rate of 31.26 MH / S, its temperature is 61 °, the fan speed is set to 88%, the card consumes 276 watts, and the efficiency of the watt / hashrate is 113 (the efficiency is improved by fine tuning and downvolting, more on that below )
Block 518864, difficulty 49679.637 – current block height in mined coin
Uptime: 0 days, 0 hours, 0 minutes, 42 seconds – program run time – 42 seconds, because we just launched it
This post is also available in: РусскийEthereum creator Vitalik Buterin criticized the developers for making the controversial ProgPoW update, which minimizes the benefits of ASIC in favor of GPU miners. Last Friday, Ethereum developers announced that ProgPoW activation was tentatively scheduled for July 2020, three weeks after the EIP-1962 update […]