The first ZCash Block was mined using so few shares that the payout calculation stopped long before the end of the PPLNS Window was reached (actually 80% left). Therefore I'm going to manually adjust the balances of all block participants until most of the block reward gets paid out. Since there's no automatism for that it may take one to two couple hours.

Dear miners, as the halving has occured, are you planning on reducing the 0.5 VTC payout to a lower one? It will take much more time to get to 0.5 now

A change has been deployed that strips the share multiplier from the "Shares" value for coins with a modifier such as MONA, VTC and LTC to make the displayed values less gargantuan. This change only affects the display of shares, not their value.

Hey!

After ~7.2M Share my share go back to 0 and my balance dont increase, Im mining with 1070ti in MonaCoin Pool. Any Ideas ?

Thx :)

Hi, newbie here, pls be gentle :)
I have configured per your instructions, but there is a difference in the recommended ports at poolmining.org/pool/xmr.

The ports list shows: stratum+tcp://xmr.poolmining.org:3033 GPU Mining

The instructions for Windows Nvidia GPU Mining shows: "url" :  "stratum+tcp://xmr.poolmining.org:3032", which is the listed port for CPU mining.

I have set port 3033. Is this correct?

I have Quadro K1200 and I am showing around 135 H/s. When mining with a different pool (ViaXMR using XMRminer), I was showing around 200 H/s. Is there a way to increase my hashrate with ccminer?

Sad to see a lot of negative comments and trolling on here. Even though I have only been playing with mining for a few days, it is clear to me that the smaller pools must pay out less frequently, but will pay out more in the long term. Why don't people get this?

Thanks for setting this up, I appreciate your work.

Just wanted to suggest an optional email update system. 

Creating a mailing service that notifies us when:

1. Blocks are found

2. Miner has stalled or was disconnected (I'm often out of the house and having smth to tell me the miner died would be useful!)

3. Service updates are scheduled or maintenance is incoming, so we can plan to restart our miners quickly.

4. Any other announcements from the admin team! 

Possible to implement chat?

First of all, I'm new to mining in general, and most of this is speculation based on comparing results here to elsewhere (and the volume of complaints about payments for these two cryptos - barring some of the "nicehash" noise of people coming from far larger pools, and expecting quicker results).

I believe there are probably 2 issues server side - and I think they are linked:

1) VarDiff - This seems to want each miner to have a super fast turn around, e.g. it's happy with them being returned within a couple of seconds (if that).  Other pools (for VTC) seem to set my difficulty around 64 (with sometimes dropping to 32, and then fairly soon going back up again) for my single GTX1080 - here it always hovers around 18.  This means on other pools I sometimes get shares that take 30 seconds or more - and others have a bunch within a couple of seconds.

E.g. this on P2Pool:

For us here, I think this is a "sledgehammer to crack a nut" scenario - using higher powered devices to solve simpler problems - people get a high number of shares - but because they are the small fry problems they aren't worth as much as their GPU solving potentially much harder stuff in a similar amount of time.

2) Allocation of jobs - this comes from the Excavator issue that is in another thread and that it seems like only here that CCMiner reports "enabled stratum stale jobs workaround", which from my investigation in another thread is that the server is reporting that the job doesn't exist - i.e. it's already been solved by someone else.  You can see this happens a lot in Excavator, and I believe CCMiner is just masking it by verifying that the job hasn't gone stale before reporting the share.  Given this I think the server doesn't allocate jobs efficiently, and will give out jobs to multiple workers, and whoever solves it first gets the share, and CCMiner will ditch the job before attempting to send the result - i.e wasting compute resource.

I would say these possibly go hand in hand, VarDiff would need to allow for more time between shares, however, the allocation of jobs needs to be so that multiple workers aren't working on the same jobs within that window.  It's possibly why the VarDiff target is so low.

I could of course be completely off base here, but thought I'd throw it out there :)

MSnmgCDQurZ3GuDtNUYbdkTaPhm4XY771p

19 hours, 5339 shares = 0 MONA

Why?