POOL: stratum+tcp://dcr.suprnova.cc:2252, WALLET: user.rig, PSW: passwd

Thanks for the explanation, but actually on yiimp.ccminer.org auto exchange is disabled on the pool level. So no any exchange should take place.

Correct answer to another question :-)

Found DCR blocks go through few stages:
- Immature (lasts up to 24 hours): network confirmations
- Exchange (lasts 1-3 hours): exchange DCR to BTC (say, on ZPool)
- Clearead (instant): earnings transferred to the balance.

You meant the "Immature" stage that is slow.
I talked about "Exchange" stage. It is obvious when I mine DCR and get paid in BTC. But when both currencies are the same (DCR), what is Exchange stage for?

I think that's workaround. They use password string to give some options like payment currency (if exchange is enabled). It will be shown in the "Extra" column (instead of x I use currently), yes, but it is not the rig name instead of "dcr" string:

dcr   x   decred   12      2.6 gh/s

Tried both zpool and yiimp (now with CDM 4.2). I found that share percent per block on Zpool somehow may be changed (lowered) for immature blocks while waiting. I understand the same for earnings, but for shares (shouldn't it be fixed at the time of block finding)?. So finally, dwarfpool and yiimp. I also like the latter because it pays in DCR to Bleutrade. I can exchange them when I like the rate, not when ZPool does, or use Auto-Sell feature of Bleutrade. The only question I have is why the pool software performs slow "Exchange" stage for DCR mining/DCR payment...

BTW, anybody knows how to report rig names to yiimp? I found their explanation to use "-u wallet,rigname", but adding rigname to the -ewal option did not work for me with CDM. Pool always shows "dcr" as a rig name for both my rigs. Any ideas?

Actually, I did RTFM for pools I used. But it was never mentioned in the README for the miner that wallet option can be somehow combined with something else to build up the final URL. Being it called 'url' option - no questions. But I expected that if you mention ethermine and dwarfpool in your examples and provide 3 different stratum modes for them, then their specifics are already implemented by -esm option.

Anyway, I agreed that it is not the issue with the miner, but with the documentation. Thank you for great product, I like it and use it now.

This sample works.

It looks like my fault is that I always RTFM (in this case, the README!!!.txt for the miner) :-)

- the examples for ethpool/ethermine do NOT show how to use rig name;
- the example for Dwarfpool does NOT show how to use rig name, but says 'you can also specify "-eworker YourWorkerName" option' - exactly that I did and that does not work.

So for both ethermine and dwarfpool the -eworker option does not work as expected. I would recommend you either update examples with rig names, or add a note that -eworker might not work, and in that case makes sense to use pool-recommended format with dot or slash for the rig name. Since no source available, it is not obvious if wallet name should/may be concatenated with other URL options like rig or password, because there are options for them and maybe there are same in the stratum protocol variations.

Since I see no hashrate report, could you please give a definitely working command line for that?

As with the case of ethermine I suspect that the miner has some issues with command line parsing. At least for ethermine the shares reports depend on the command line args order. So I suspect the same is with -esm 0.

To be precise, here is the command line which does NOT report hashrate to dwarfpool:

Claymore,

should your miner report "Sent hashrate" to DwarfPool in ESM=0 mode? I see no reported hashrate, but eth-proxy with ethminer report this.

This sample works (with changed wallet and worker name)!
Now I will try to determine what's wrong with my command line. First I suspect is different pool (I use eu1 instead of us1). Anyway, thank you, now I know that miner works, and I know where to dig.

EDIT: eu1 pool works as well. It seems to me that's the matter of parameters order in the command line. I used a bit different order, and it never worked for share stats reporting. I used your cmdline, replaced with my wallet/rig names, changed pool to eu1, added some -etha in the end (my two identical 7950 cards like different -etha values), and it works, now shares are shown. Great!

Claymore, sorry, still about missing shares @ethermine with -esm 1.  Doubled hashrate seen only after miner start, then it stabilizes to the real. But still no share info. What should I find in miner logs to find out why? What's the protocol difference, can you help? Not say it is very important (no rejected shares for me), but nice to see the number of shares found.

It works but the same way. Here is how it looks like:

qtminer updates share stats every 5 minutes (of course, not qtminer but the pool when mined with qtminer)

I'm trying to mine at ethermine.org. All works except two things (tested on both 4.0 beta and 4.1):
- Sometimes ethermine reports doubled "Reported hashrate" for the account, but always correct hashrate for the rig (just one rig used).
- With -esm 0 or -esm 1 it still does not show stats "Shares (Invalid / Valid / %)". All are always 0.

Command line:

What can be wrong?