Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux)

[pilotbtc1]

 What did I do wrong ? : no of mining
ZecMiner64.exe -zpool SSL: //zec-eu1.nanopool.org:6633 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw r -i 8 

Thanks

[delle54]

It's not that I don't trust Claymore's Miner.. but my Kaspersky Anti Ransomware Tool just blocked just blocked zecminer64.exe ..

Just put it in "exceptions". Miners are oftenly recognised as viruses.

[adly3000]

Fiji still beats the pants off 1070...

Efficient Setup
Fury $260 300H/s 100W
1070 $400 330H/s 95W
You're paying $840 more for 180H/s and 30W efficiency on a 6 card rig.

Full Bore (small scale with no electric cost)
Fury $260 350H/s
Edit: 1070 $400 430H/s
Edit: You're paying $840 more for 480H/s on a 6 card rig.

Which Fury model consumes 100W and clocks please!!!

[Claymore]

Just noticed Claymore has a sense of humor:

Code:

not so easy bro :)

When setting AMD_OCL_BUILD_OPTIONS_APPEND

Setting AMD_OCL_BUILD_OPTIONS gets:

Code:

it fails too ;)

However after a quick hex edit of the amd opencl shared library

Code:

export AMD_OCL_RALPH_OPTIONS_APPEND=-save-temps

Works just great. :-)

Yeah - I've unpacked the real miner binary (zecminer64 is only 66k, this is because it loads Data3.bin, decodes it, and then runs it.)

From there you end up with a binary that looks to have been packed by a modified version of UPX - unpacking what it drops looks like an ELF loaded at 0x80000 - it patches several jumps in it to make it work, because it looks like it expects to be loaded at 0x40000. THAT looks like it drops ld.so and the real miner ELF into memory.

Yo dawg, I herd you like executing, so I put an ELF64 in your ELF64 so you can execute while you execute.

I think now one of my points about Linux release is clear - other devs want to see how my miner works and do reverse engineering as soon as they can. It's much easier to do it in Linux.
My License.txt prohibits such things clearly, so you violate the license.
Remember I violated MIT license in past and was blamed that I steal other's work. Now I see same thing from you. Have fun...

[ocminer]

All tries getting the linux miner to work just fail for me with either access violations or a complete lock up of the rig where only a hard reset helps.  Optiminer works fine though.

[doktor83]

Just noticed Claymore has a sense of humor:

Code:

not so easy bro :)

When setting AMD_OCL_BUILD_OPTIONS_APPEND

Setting AMD_OCL_BUILD_OPTIONS gets:

Code:

it fails too ;)

However after a quick hex edit of the amd opencl shared library

Code:

export AMD_OCL_RALPH_OPTIONS_APPEND=-save-temps

Works just great. :-)

Yeah - I've unpacked the real miner binary (zecminer64 is only 66k, this is because it loads Data3.bin, decodes it, and then runs it.)

From there you end up with a binary that looks to have been packed by a modified version of UPX - unpacking what it drops looks like an ELF loaded at 0x80000 - it patches several jumps in it to make it work, because it looks like it expects to be loaded at 0x40000. THAT looks like it drops ld.so and the real miner ELF into memory.

Yo dawg, I herd you like executing, so I put an ELF64 in your ELF64 so you can execute while you execute.

I think now one of my points about Linux release is clear - other devs want to see how my miner works and do reverse engineering as soon as they can. It's much easier to do it in Linux.
My License.txt prohibits such things clearly, so you violate the license.
Remember I violated MIT license in past and was blamed that I steal other's work. Now I see same thing from you. Have fun...

Well you had to knew this.. i'm just surprised they openly talk about it on the forum

[ocminer]

Just noticed Claymore has a sense of humor:

Code:

not so easy bro :)

When setting AMD_OCL_BUILD_OPTIONS_APPEND

Setting AMD_OCL_BUILD_OPTIONS gets:

Code:

it fails too ;)

However after a quick hex edit of the amd opencl shared library

Code:

export AMD_OCL_RALPH_OPTIONS_APPEND=-save-temps

Works just great. :-)

Yeah - I've unpacked the real miner binary (zecminer64 is only 66k, this is because it loads Data3.bin, decodes it, and then runs it.)

From there you end up with a binary that looks to have been packed by a modified version of UPX - unpacking what it drops looks like an ELF loaded at 0x80000 - it patches several jumps in it to make it work, because it looks like it expects to be loaded at 0x40000. THAT looks like it drops ld.so and the real miner ELF into memory.

Yo dawg, I herd you like executing, so I put an ELF64 in your ELF64 so you can execute while you execute.

I think now one of my points about Linux release is clear - other devs want to see how my miner works and do reverse engineering as soon as they can. It's much easier to do it in Linux.
My License.txt prohibits such things clearly, so you violate the license.
Remember I violated MIT license in past and was blamed that I steal other's work. Now I see same thing from you. Have fun...

Actually, it would have been easier to reconstruct the actual miner binary on Windows. There's nice tools to do this for the PE32+ (PE 64-bit) format, but jack shit for ELF64.

My owner and I recovered the binary in its original, unpacked form, btw - not much in the way of anti-debugging once you get to there. Some obfuscation, but not much. Checkmate - that was a fun workout; time to figure out something else to do.

Stop worrying about your devfee, it's not about removing it or altering it. It was just fun to do.

Clay you can rest assured that every big(er)  cloud hashing company has your miner variations and optimizations already -  regardless of ssl, packing, upx, linux etc..  

[nicehash]

Hi,

We have added SSL support for mining on NiceHash with Claymore Equihash Zcash miner (as you know, SSL lower's Claymore miner's fee from 2.5% to 2.0%).

You have to use stratum+ssl:// for stratum connection and use port 33357. Please see the examples below:

Mining with Claymore Equihash Zcash miner on EU location

Code:

ZecMiner64.exe -zpool stratum+ssl://equihash.eu.nicehash.com:33357 -zwal [YOUR-BTC-ADDR].[YOUR-WORKER-NAME] -zpsw -x

Mining with Claymore Equihash Zcash miner on USA location

Code:

ZecMiner64.exe -zpool stratum+ssl://equihash.usa.nicehash.com:33357 -zwal [YOUR-BTC-ADDR].[YOUR-WORKER-NAME] -zpsw -x

Mining with Claymore Equihash Zcash miner on ASIA Hong Kong location

Code:

ZecMiner64.exe -zpool stratum+ssl://equihash.hk.nicehash.com:33357 -zwal [YOUR-BTC-ADDR].[YOUR-WORKER-NAME] -zpsw -x

Mining with Claymore Equihash Zcash miner on ASIA Japan location

Code:

ZecMiner64.exe -zpool stratum+ssl://equihash.jp.nicehash.com:33357 -zwal [YOUR-BTC-ADDR].[YOUR-WORKER-NAME] -zpsw -x

Best regards,
NiceHash team.

[QuintLeo]

The 1070 has a long way to go before it's worth a look.  The entry cost of $400/card is just too steep to overcome without some serious hash.

Edit: AMD guys are quibbling over 0.5% using ssl and 2%-4% in pool variance.
Nvidia guys are paying a 20% premium just to play the game and screaming victory.  It would be funny if it wasn't so pathetic.

 It's nice for those of us that already HAVE the 1070s, but I certainly wouldn't consider buying one over 1.8-2x RX 470s just to mine with.
 On the other hand, some folks are ALL ABOUT "I've got the fastest, nah nah nah!"...

 ...in which case the Titan X Pascal has been reported at well over 500 sol/s on eqm 1.0.4a


I won't get into the $1200 - it's NOT WORTH IT unless you already have the card!

[Claymore]

Actually, it would have been easier to reconstruct the actual miner binary on Windows. There's nice tools to do this for the PE32+ (PE 64-bit) format, but jack shit for ELF64.
My owner and I recovered the binary in its original, unpacked form, btw - not much in the way of anti-debugging once you get to there. Some obfuscation, but not much. Checkmate - that was a fun workout; time to figure out something else to do.
Stop worrying about your devfee, it's not about removing it or altering it. It was just fun to do.

Yeah, you and your owner did it just for fun, I understand it of course

Clay you can rest assured that every big(er)  cloud hashing company has your miner variations and optimizations already -  regardless of ssl, packing, upx, linux etc..  

Agreed.
I know what I do.
However, I'd like to state that some devs don't respect the license and discuss their success in miner disassembling and GPU kernels dumping right in my thread.

[QuintLeo]

does not work with my gigabyte hd7950 3gb,
none of the claymores did, some 7950 do work btw. high hashes, thanks clay,
what could the cause be. card mines the hell out of other alts.

anyway.. version 9.3 on the way i guess,?

 Very odd, v9.2 LINUX version runs fine for me on a HD 7870 2GB card (only had the chance to check it out on one machine so far, holiday stuff and eqm 1.0.4a + Burst deployment keeps getting in the way).

 Catalyst 15.12, SDK 2.9.1, Ubuntu 14.04 LTS with evilTrinity replaced by XFCE (XUbuntu "upgraded" to XOrg 1.18 which breaks fglrx which destroys the whole POINT to running 14.04 at all).

[QuintLeo]

Actually, it would have been easier to reconstruct the actual miner binary on Windows. There's nice tools to do this for the PE32+ (PE 64-bit) format, but jack shit for ELF64.
My owner and I recovered the binary in its original, unpacked form, btw - not much in the way of anti-debugging once you get to there. Some obfuscation, but not much. Checkmate - that was a fun workout; time to figure out something else to do.
Stop worrying about your devfee, it's not about removing it or altering it. It was just fun to do.

Yeah, you and your owner did it just for fun, I understand it of course

Cats are like that.

[ocminer]

What did I do wrong ? : no of mining
ZecMiner64.exe -zpool SSL: //zec-eu1.nanopool.org:6633 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw r -i 8 

Thanks

ZecMiner64.exe -zpool SSL://zec-eu1.nanopool.org:6633 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw -i 8 

Alternative :

ZecMiner64.exe -zpool ssl://zec.suprnova.cc:2242 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw -i 8 

[QuintLeo]

For Linux - Ubuntu - use this :

export GPU_FORCE_64BIT_PTR=0
export GPU_MAX_HEAP_SIZE=100
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PERCENT=100
export GPU_SINGLE_ALLOC_PERCENT=100

make new file : run.sh

Code:

#!/bin/bash
export GPU_FORCE_64BIT_PTR=0
export GPU_MAX_HEAP_SIZE=100
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PERCENT=100
export GPU_SINGLE_ALLOC_PERCENT=100

sleep 20
./zecminer64

Note: change the run.sh Permission

Code:

chmod +x run.sh

 use any setting ( read the ReadMe!! file )
  i think this will help!!

Thank you, but for what reason do you use the sleep command?

 I don't get that one too - but I've got a couple of ATICONFIG commands (one fan speed set, one clocks set) after the exports and before the miner startup, never had an issue doing it that way on any miner software I've ever run.

[nicehash]

What did I do wrong ? : no of mining
ZecMiner64.exe -zpool SSL: //zec-eu1.nanopool.org:6633 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw r -i 8 

Thanks

ZecMiner64.exe -zpool SSL://zec-eu1.nanopool.org:6633 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw -i 8 

Alternative :

ZecMiner64.exe -zpool ssl://zec.suprnova.cc:2242 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw -i 8 

Som more alternative:

ZecMiner64.exe -zpool stratum+ssl://equihash.eu.nicehash.com:33357 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw -x

[QuintLeo]

one question...

for mining ZEC is big difference to have

AMD rx 470 4gb

or

AMD rx 470 8GB ?

thx

 It's about the memory SPEED, not the size.

 With that said, the 8GB cards seem to mostly if not all use 8000 Mhz (effective) RAM where 4GB cards usuallly have 6600 or 7000.

 You might also see this listed as 2000 vs 1750 or 1650 - the raw clock rate vs. the effective.

[QuintLeo]

- added Linux version.

what version of ubuntu should be used?

 14.04 for R9 280x / 280 and older HD series (NOT XUbuntu as it updated XOrg to 1.18 which is NOT fglrx compatable) due to AMD not offering support on many or most of those cards past 15.12 Crimson.

 16.04 for RX 4xx as those are only supported by AMDGPU PRO drivers that don't work on older Ubuntu versions.

 I'd probably go with 16.04 on the R9 3xx series as well to leave room for easy future upgrades.

[bazsy]

Hi!
Claymore v9.2 linux miner how to run windows cygwin terminal?

[Yerba]

What did I do wrong ? : no of mining
ZecMiner64.exe -zpool SSL: //zec-eu1.nanopool.org:6633 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw r -i 8 

Thanks

ZecMiner64.exe -zpool SSL:(YOU HAVE SPACE HERE)//zec-eu1.nanopool.org:6633 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw r -i 8 

[ocminer]

What did I do wrong ? : no of mining
ZecMiner64.exe -zpool SSL: //zec-eu1.nanopool.org:6633 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw r -i 8 

Thanks

ZecMiner64.exe -zpool SSL:(YOU HAVE SPACE HERE)//zec-eu1.nanopool.org:6633 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw r -i 8 

Alternative:

ZecMiner64.exe -zpool ssl://zec.suprnova.cc:2242 -zwal t1RGQ4QhSqMMDNF8RaZRm5AHvrP7zyFZD6v.1 -zpsw x -i 8