just a quick heads up, press s and verify your incorrect shares. I reverted to 5.3 because all above 6 gave me about 1% incorrect shares. after much testing I can confirm the incorrect share problem is real with the newer versions, all else being equal. why? no idea, maybe claymore could look into it. running 4 rigs, 380s, 390s, one 280x, 470s, win7 and one rig win10
Just checked it, currently v6.4 got 6 incorrect shares and 6140 correct ones. So it's about 0.1% of incorrect shares. It is because of fast math I use in kernels, if you don't like it you can use "-etha 2" but it's about 1% slower. DAG size grows and it causes more incorrect shares, as soon as they reach about 0.5% I will use "-etha 2" by default. However, v5.3 and v6.4 must show same rate of incorrect shares on same DAG (epoch).
Okay your ignorance let me take the descission to ban claymore from my pool-sources, at time porting open-ethereum-pool to open-decred-pool ...
but you are out
Oh, you can ban me from anything you want of course.
Though I'd like to know what you want anyway, it seems I overlooked something interesting, this thread is full of newbies questions and grows all the time by several pages every day. If you are a dev, you can PM me and I will try to answer your questions.
EDIT: found your question finally, my miner supports four different ETH stratum versions, check "-esm" option for that in OP:
-esm Ethereum Stratum mode. 0 - eth-proxy mode (for example, dwarpool.com), 1 - qtminer mode (for example, ethpool.org),
2 - miner-proxy mode (for example, coinotron.com), 3 - nicehash mode. 0 is default.
So if miner does not work with your pool, probably you use incorrect "-esm" value.
PS. While searching within your latest posts to find a message in my thread, found your nice phrase "you could dual mine without closedsource claymore shit". Thanks you are so polite
