Quote from: aeon on July 03, 2014, 01:21:29 PM

Quote from: 33zer0w0lf on July 03, 2014, 05:06:22 AM

Quote from: aeon on July 03, 2014, 05:01:55 AM

Quote from: 33zer0w0lf on July 03, 2014, 02:24:17 AM

Quote from: xaitienle on July 03, 2014, 02:14:53 AM

Quote from: 33zer0w0lf on July 03, 2014, 01:58:19 AM

Quote from: xaitienle on July 03, 2014, 01:54:06 AM

Quote from: 33zer0w0lf on July 02, 2014, 10:47:58 PM

Quote from: pepi on July 02, 2014, 09:43:43 PM

Maybe your pool has latest code, but http://minin.gs has farrrr leesssss orphan blocks then any other pool. You may ask him for advice...

I don't think you understand how pools work.
If all the hash is on one pool, then other pools will receive orphans until the hash spreads more evenly.
I have the largest pools for bytecoin, and ducknote, I understand very well how to run the pool.

I agree with you 33zer0w0lf, how about mount coin ? Have you fixed it yet ?

not yet haven't heard from CRZ in a while.
I could setup another mountcoin pool and have it payout fresh from version 2.0.3 but I have put so much time into it that I didn't really want to do anymore work on it until the first issue was resolved.

I moved my rigs to your pools 33zer0w0lf ( around 10KH/s) hope it will decrease your orphans blocks and spreads hash to network

very cool, thanks xaitienle.

Dev: this fix form zone117x for the monero dameon fixed an issue that this coin is having as well, you should look into implementing this fix.
https://github.com/zone117x/bitmonero/commit/b87577f4441fd53d513ecf64a905104db3db20e2

This fix was reverted: https://github.com/monero-project/bitmonero/pull/55
Feel free to test it with your pool though.

They implemented another fix to solve the issue, are you going to do something similar?

What issue are we talking about?
Can you PM more details?

The daemon auto saves, when this happens if it takes to long to save the blockchain the wallet will time out. Obviously on the pool this is not good as then different modules will freeze up.