./ethdcrminer64 -epool etc-eu.suprnova.cc:3333 -ewal suprnova.1 -epsw x -esm 3 -allpools 1 -allcoins 1
Is there any disadvantage of using it like this ? Seems to work fine for me...
Hmm, earlier there were some reports that "extranonce.subscribe disabled", when mining with claymore on nicehash, reduced speed.
Edit:
Gotta walk the dog.. but i can put some rigs to test with claymores.
Should i mine on the nicehash settings or regular?
Regular won't work, but Nicehash Mode should work fine.. (-esm 3 -allpools 1 -allcoins 1)
Seems ok.
I got this line on of the miners. But only once.. and its finding shares right after. So i guess its ok. Ill watch it for while to compare reported and actual hashrate.
ETH: Received error: {"id":4,"result":null,"error":[21,"jobnotfound"]}
ETH: 07/26/16-14:52:34 - SHARE FOUND - (GPU 4)
ETH: Share accepted (62 ms)!
ETH: 07/26/16-14:52:36 - SHARE FOUND - (GPU 6)
ETH: Share accepted (63 ms)!
ETH: 07/26/16-14:52:39 - SHARE FOUND - (GPU 3)
ETH: Share accepted (63 ms)!
Update.
@ ocminer
I noticed a "problem"
Im not sure if its the claymore miner or the nicehasd stratum.
But the hashrate is 40-50% lower there.
Example pic.
http://imgur.com/a/g4p97
Miner 1 = genoils
Miner 3&5 = claymores
They should all be 110-130
As u can see the claymores are way lower.
Should i test the low diff?
Hmm, when you use this genoil:
https://github.com/nicehash/cpp-ethereum
It works 100% as it's the native implementation for nicehash's stratum.
I'll try Claymore now again, and adapt my stratum to the native claymore protocol too, the problem is just, that it uses Wallet adresses instead of usernames which is a bit uncommon on MPOS pools but i'll get something around it...
Tried low diff too (3332) but got even lower rate.
But!!!
Isnt this just the reported rate. The miner mines at 125mh, even tho the pool says 55mh.
And it finds share like f**k.. every 5th second or something.
Isnt it the shares that count? I dont get any rejected.. just low reported hashrate, but still finding shares (locally) very fast.
Yes, it's the share that count but your hashrate should also match.
For me my Rig which was mining with this:
https://github.com/Genoil/cpp-ethereum/tree/110
(with -SP 2)
And is now mining with Claymore has no problems (4 x 280x) and the hashrate matches.
Even when I test-rent at nicehash and point it to the dedicated nicehash port, my hashrate matches the one displayed at nicehash's site.
Genoils works nicely. The pool even reports higher hashrate than the miner.
Claymores still very low... but the shares fly by.
Miner 3 is R9 380s
Miner 5 has R9 390s
Ah, I think I found the problem, should be ok now
3334 works nicely now.
Retrying claymore.
Edit:
Claymore good too! (port 3333)