I fixed the rejected shares issue. Please check your efficiency again and see if it has increased.

The database issue has been resolved, and rejected shares are now minimal. We have also fixed the issue that caused some miners to be unable to connect. Check your "earnings" page and if you don't see a high efficiency please let me know.

We traced this to an issue with resource contention on our database server. I created a thread explaining it in the support forum and I will update the progress there.

We have determined that there is resource contention on our database server, which is causing shares to be queued and submitted all at once (thus getting rejected for being stale). We are working to reduce load on the database server in order to mitigate the issue. As usual I will keep you updated o...

I believe this is due to our stratum server changing coins so frequently that your miner is spending a lot of time switching to new work. We are working right now to try reducing the frequency of switching, but at some point we won't reduce it further. Our goal is to balance profitability and mining...

Right now, we do not have support for multiple workers per account, although we plan to add that in the future. A temporary solution would be to create multiple accounts, although I will acknowledge that at 1.2MH/s per account it would take a while to build up enough of a balance in each account to ...

I am aware that the pool is having a large reject rate at the moment. I believe this is due to the pool switching coins so frequently that there are many stale shares being submitted and rejected. I am working on changing the configuration in order to reduce these rejected, and I will keep everyone ...

I tried using dysan's name for our miners at "prohashing.com:3333" and it worked properly. I then tried connecting on my GPUs both with and without the prefix (our Zeusminer interface doesn't allow you to add the prefix) and either way it took about 30 seconds to connect and occasionally f...

The config values have been changed. Let's see what happens.

I think I know the issue. Try using just prohashing.com:3333 as the address and let me know what happens.