It's working like a charm for me. I've even gotten solo mined MON & PLX already @ ~1.2MHS.

Now who's got it quad mining?

I don't have a list of merge mineable Scrypt-N coins. Is there a list of coins that could be merge solo mined from a p2pool node?

If I try to add merged mining for something like Execoin by copying the settings for PLX & MON, what am I likely to miss?
(I recall the instructions have a reminder to open the new ports in iptables).

Thanks, and happy mining to all.

Thanks for all your contributions to the community. Thanks in advance, in anticipation of all the requests and hassles you'll get as your reward. ;-) Every time I try something that should make sense, I end up back at vtcpool (p2pool) but I'm going to try your VM (Hyper-V).

As a low hashrate ( 1 MHS) miner, I know I'm going to want to keep checking that the MON & PLX solo mining shares are going in, in between the infrequent finding of blocks. What are some of the best options for checking that work is properly being contributed to MON & PLX? I don't need a UI, just a string to grep in some logfile, or a command to type, would keep me from wasting time if something were broken (or when I'm just too impatient).

Pool is working much better, thanks guys.

After the 1.6 hard fork, when the multipools can't jump so easily, it should get even better.

Everybody ready for the switch at block 145,000?

I can confirm I am getting consistently an average reward only half what I would expect for my hash rate.
I get 1/4 the average reward post halving where I would expect 1/2 the pre halving reward.
It is statistically improbable that 'bad luck' (random chance) could produce this for so many 24hr periods.

Bad shares is down to ~1%, so that doesn't appear to be a problem.
My only clue from the interface, is that Est. Shares is listed as 400%, 800% or more, much of the time.

When I was getting 4x the reward, pre halving, with other variables fixed,
the interface did not show that as often.

A problem somewhere with the  math & computing?
(math is hard, there doesn't have to be any 'scam' going on).

Anyway, I'm switching to my backup pool,
until I read here that something has been changed.
Then I'm happy to come back and test again.

Thanks guys.

What is 'low hashrate'? Is there a FAQ on your vardiff algorithm?

I run separate workers, each ~1MH/s, are they individually low hashrate?
Should they be on the low hashrate port or dogepolis?

What's optimum for the variable difficulty?
Should we try for just lower vardiff than the worker's average hashrate?

P.S. I'm also seeing almost 10% rejections right now.
Not complaining, just adding another data point.

Thanks for all your hard work,
and for any answers to my questions above.

Everybody could mine the most if you could add optional email alerts when a worker is not working (and/or SMS alert).
Right now, especially because the Web interface is down so much of the time, it's hard to tell (by constant pull refresh) when workers are not working.

A (push) email alert would help miners get their workers going again faster, switch to a new port when you need it, etc.
Email alerts should also decrease how often many people keep refreshing your Web pages.

Thanks for a good pool, and all your hard work!