Prohashing Mining Pool Forums

The profit at litecoin.org is 103% PPS right now and you are charging 5%!
You must provide a profit of at least 10% to compete!
How is that going?

And here is the profit from Nice: 0.1055 * 20% 0.1074 *

PRO is way below.
You seem to have some problems to resolve.

Clevermining is showing 120% of LTC right now or 0.0001084, and PRO is making less.
Why is that?
Someting is wrong with PRO!

Right now; Clevermining 0.0001030
And right now: Prohash 0.0007138

Just a snapshot of the reality.

Steve Sokolowski wrote:Try using h=100, and see what difference that makes with hashrate, and report back.

Ok I put in the h=100 just now it does seem to have stablized my miners at there more normal hashrate but to early to tell. But IMO it sure seems to have helped right off will check back in after they have run a while

I know that the Yobit issue described in the other post is causing some problems, but Chris seems to think that there is something causing losses across all coins. He was unable to correlate it by miner or over time, and he's trying other variables to see what he can make the correlation with.

Hopefully, he'll be able to reply this evening with more info.

ok....

Right now: Clevermining: 119% of LTC. or 0.0001054.
Nicehash: 120% of LTC or 0.0001060 BTC
Prohash: Under LTC or 0.0007353.

Are you gonna fix this?

Chris is continuing to investigate.

His latest theory is that the issue is related to orphan mining. We are going to attempt another release with orphan bonuses disabled, and see what happens.

We spent last night investigating this problem. We determined that the cause of the problem is the orphan mining changes that were made a few weeks ago, and we programmed and tested a solution to the problem. It works on the development environment, but it failed release three times last night, not recording any shares each time.

Unfortunately, today is a Friday, and there is nothing more frustrating than this system being suboptimal when I can't work on it. When the evening arrives, I'll get back to work on this and try to figure out why the release continues to fail in production.

Thanks for your patience!

Steve Sokolowski wrote:We spent last night investigating this problem. We determined that the cause of the problem is the orphan mining changes that were made a few weeks ago, and we programmed and tested a solution to the problem. It works on the development environment, but it failed release three times last night, not recording any shares each time.

Unfortunately, today is a Friday, and there is nothing more frustrating than this system being suboptimal when I can't work on it. When the evening arrives, I'll get back to work on this and try to figure out why the release continues to fail in production.

Thanks for your patience!

Thanks for keeping us up to date on what is happening. I know you are working hard to get this fixed