Zmine GUI - Easiest GUI Miner for Zcash

super3 · April 2, 2018, 5:11pm

First official release of zmine. Please be gentle. We welcome feedback, comments, and suggestions.

Code

Github - Free and AGPLv3 licensed.
Releases - Windows and Linux binaries here.

Features

One click mining
Automatic error validation of zcash address
Automatic platform detection and download of mining software
Easy switch between CPU, NVIDIA, and AMD mining
Easy access to mining pool dashboard

Notes

We are currently using nheqminer-0.5c as the backend mining software
Current hashrates are being sent to http://zfaucet.org:3000/ for a future remote stats panel
Linux version may not work due to dependency issues - will be fixed in future releases

Screenshot

miner-0 2 0

CitricAcid · April 3, 2018, 1:46pm

Why are you using software that has not been updated in 15 months and is long outdated for anything other than CPU mining.

You list this as the easiest GUI miner for Zcash; however you just joined this forum 21 hours ago and using this software would lead me to believe you are either 100% new to this or this is a scam since its pointing to the pool that YOU choose.

super3 · April 3, 2018, 2:16pm

I agree that it is not the best miner, but it seemed to support CPU, and both families of GPUs. I understand your skepticism, but you can see in this issue we plan to add many more miners. The goal is actually to add all the major zcash miners to the GUI. Do you have any thoughts on which one we should add next?

Code is open-source. So you can verify it rather than trusting me.
Joined because I wanted feedback on the GUI
Flypool was the only pool that had a consistent and good API for the advanced stats we want to add.

Your point is noted on the outdated mining software. We will add better options in the next major release.

CitricAcid · April 3, 2018, 6:08pm

IMO there are only three miners for Zcash

AMD = claymore

Nvidia = EWBF and DSTM

nheqminer-0.5c is CPU only and more so for hobbyist and those that want to test how it all works

Shawn · April 3, 2018, 9:17pm

This looks promising, if it can be on par with the other major mining software it will be a welcome addition to the Zcash ecosystem! Ease of use is always important.

super3 · May 10, 2018, 10:22pm

New version out. DSTM-0.6 added as a supported miner per @CitricAcid’s suggestion. We were not able to get EWBF working on the first pass. Here is the new interface:

We done have an AMD machine laying around, so is there anyone who can provide me with console output from Claymore-12.6? I’m looking for console output that shows the hashrate and what the output is when it finds and share.

phakov · May 11, 2018, 2:40pm

Here’s a feature request: Is it possible to mine to two or multiple wallets? I’d like to be able to do the following:

Mine X% to Wallet1
Mine Y% to Wallet2

And so forth - as it is, I do not know of any mining programs that do that.

Also, what are you looking for from Claymore’s output? Do you just want a text copy of the screen?

super3 · May 11, 2018, 3:13pm

@phakov What would be the benefit of splitting the mining rewards? Yeah just want someone to copy paste the text from the console window output here.

garethtdavies · May 11, 2018, 3:20pm

Is this what you are after?

ZEC: GPU0 297.952 H/s, GPU1 304.918 H/s, GPU2 301.263 H/s, GPU3 264.533 H/s, GPU4 303.408 H/s
Pool switches: ZEC - 0
Current ZEC pool share target: 0x00041893 (diff: 16000H)
GPU0 t=58C fan=83%, GPU1 t=69C fan=83%, GPU2 t=60C fan=83%, GPU3 t=51C fan=83%, GPU4 t=65C fan=83%
ZEC: 05/10/18-17:23:34 - SHARE FOUND - (GPU 2)
ZEC: Share accepted (96 ms)!
GPU #0: Ellesmere
GPU #1: Ellesmere
GPU #2: Ellesmere
GPU #3: Ellesmere
GPU #4: Ellesmere
ZEC - Total Speed: 1471.568 H/s, Total Shares: 14900(3250+3335+3349+2920+3239), Rejected: 60, Time: 47:05
ZEC: GPU0 297.376 H/s, GPU1 305.126 H/s, GPU2 301.067 H/s, GPU3 264.563 H/s, GPU4 303.436 H/s
Pool switches: ZEC - 0
Current ZEC pool share target: 0x00041893 (diff: 16000H)
GPU0 t=58C fan=83%, GPU1 t=68C fan=83%, GPU2 t=60C fan=83%, GPU3 t=51C fan=83%, GPU4 t=65C fan=83%
GPU0 t=58C fan=83%, GPU1 t=69C fan=83%, GPU2 t=60C fan=83%, GPU3 t=51C fan=83%, GPU4 t=65C fan=83%
GPU #0: Ellesmere
GPU #1: Ellesmere
GPU #2: Ellesmere
GPU #3: Ellesmere
GPU #4: Ellesmere
ZEC - Total Speed: 1471.533 H/s, Total Shares: 14900(3250+3335+3349+2920+3239), Rejected: 60, Time: 47:05
ZEC: GPU0 297.125 H/s, GPU1 304.886 H/s, GPU2 300.984 H/s, GPU3 264.544 H/s, GPU4 303.994 H/s
Pool switches: ZEC - 0
Current ZEC pool share target: 0x00041893 (diff: 16000H)
GPU0 t=58C fan=83%, GPU1 t=69C fan=83%, GPU2 t=60C fan=83%, GPU3 t=51C fan=83%, GPU4 t=65C fan=83%
GPU #0: Ellesmere
GPU #1: Ellesmere
GPU #2: Ellesmere
GPU #3: Ellesmere
GPU #4: Ellesmere
ZEC - Total Speed: 1471.488 H/s, Total Shares: 14900(3250+3335+3349+2920+3239), Rejected: 60, Time: 47:05
ZEC: GPU0 297.208 H/s, GPU1 304.722 H/s, GPU2 300.976 H/s, GPU3 264.488 H/s, GPU4 304.094 H/s
Pool switches: ZEC - 0
Current ZEC pool share target: 0x00041893 (diff: 16000H)
GPU0 t=58C fan=83%, GPU1 t=69C fan=83%, GPU2 t=60C fan=83%, GPU3 t=51C fan=83%, GPU4 t=65C fan=83%
GPU #0: Ellesmere
GPU #1: Ellesmere
GPU #2: Ellesmere
GPU #3: Ellesmere
GPU #4: Ellesmere
ZEC - Total Speed: 1473.031 H/s, Total Shares: 14900(3250+3335+3349+2920+3239), Rejected: 60, Time: 47:05
ZEC: GPU0 297.824 H/s, GPU1 305.251 H/s, GPU2 301.342 H/s, GPU3 264.438 H/s, GPU4 304.177 H/s
Pool switches: ZEC - 0
Current ZEC pool share target: 0x00041893 (diff: 16000H)
GPU0 t=58C fan=83%, GPU1 t=69C fan=83%, GPU2 t=60C fan=83%, GPU3 t=51C fan=83%, GPU4 t=65C fan=83%
ZEC: 05/10/18-17:23:48 - SHARE FOUND - (GPU 1)
ZEC: Share accepted (96 ms)!
GPU #0: Ellesmere
GPU #1: Ellesmere
GPU #2: Ellesmere
GPU #3: Ellesmere
GPU #4: Ellesmere
ZEC - Total Speed: 1473.208 H/s, Total Shares: 14901(3250+3336+3349+2920+3239), Rejected: 60, Time: 47:05
ZEC: GPU0 297.779 H/s, GPU1 305.198 H/s, GPU2 301.461 H/s, GPU3 264.421 H/s, GPU4 304.349 H/s
Pool switches: ZEC - 0
Current ZEC pool share target: 0x00041893 (diff: 16000H)
GPU0 t=58C fan=83%, GPU1 t=69C fan=83%, GPU2 t=60C fan=83%, GPU3 t=51C fan=83%, GPU4 t=65C fan=83%
GPU #0: Ellesmere
GPU #1: Ellesmere
GPU #2: Ellesmere
GPU #3: Ellesmere
GPU #4: Ellesmere
ZEC - Total Speed: 1473.592 H/s, Total Shares: 14901(3250+3336+3349+2920+3239), Rejected: 60, Time: 47:05
ZEC: GPU0 298.408 H/s, GPU1 305.269 H/s, GPU2 301.566 H/s, GPU3 264.638 H/s, GPU4 303.712 H/s
Pool switches: ZEC - 0
Current ZEC pool share target: 0x00041893 (diff: 16000H)
GPU0 t=58C fan=83%, GPU1 t=68C fan=83%, GPU2 t=60C fan=83%, GPU3 t=51C fan=83%, GPU4 t=65C fan=83%

root · May 11, 2018, 3:31pm

@super3 If someone were hosting gpu hardware it might make sense for them to take N% of rewards to cover electricity and hosting fees. I believe that’s what @phakov was going for.

Question: Do you plan to add easy overclocking or temperature targets to this? That is one of the big missing parts for Linux at the moment. I’ve been working towards it but don’t yet have anything to release.

super3 · May 11, 2018, 6:21pm

@garethtdavies Thank you very much!
@root My personal though is they should just do that in their wallet. As far as easy overclocking and temperature targets it is something that could be added. Could you tell me a bit more about this problem, and how you think we could solve it?

root · May 11, 2018, 6:51pm

It’s correct that you could do that in your wallet, but if you’re hosting quite a few users that could become a complex task that’s worth automating.

As for the temperature problem, I can only speak for Nvidia gpus. Essentially you use something like this to query for gpu info every few seconds:

nvidia-smi --query-gpu=index,temperature.gpu,power.draw,clocks.sm,clocks.mem,clocks.gr --format=csv,noheader

Then loop through those results, checking the gpu temperature and adjusting the power level to decrease or increase where necessary:

# N is the gpu bus_id
# -pl range 150-250 for 1080 ti    
nvidia-smi -i N -pl new_power_level

So essentially you keep a specified temp.

Additionally to add overclocking you could have a simple switch or range for the power level per gpu and set the core and mem clocks.

E.g., If power level is 150-170 you could set the core to 20 and the mem to 20:

# N is the gpu_id
nvidia-settings -a [gpu:N]/GPUGraphicsClockOffset[3]=20
nvidia-settings -a [gpu:N]/GPUMemoryTransferRateOffset[3]=20

I have some work in progress that’s not ready yet.

I’ll be open sourcing this when it’s done.

phakov · May 11, 2018, 6:54pm

The benefit to having multiple addresses is that a machine can send a portion of its proceeds to another party automatically. There are uses for it.

super3 · May 12, 2018, 12:27am

So basically you want to overclock in real time based on temp?

root · May 13, 2018, 3:34pm

Yes - via managing the power level and then core+mem values. Users have different core and mem values that they like, so this might be different for everyone.