@gentarkin / HOW DOES IT WORKWe assume if the LP response from deepbit is first then deepbit owns it. We actually reset the owner to take into account if another pool drops but currently we don't reset deepbits starts due to that.

It looks like efficiency is good. Parai got about 168% and magnet got about 559% efficiency. I just did the calculations for you guys.

EDIT:However I haven't actually gotten my server to mine on deepbit. Only my dev machine. So there may still be errors.

But, I hardly ever see the "owned by" stat in the window = deepbit. Its usually someone else. But it still switches to mine deepbit in that case anyways.

So, Im curious, since deepbit will be mined a majority of the time w/ BH...what is the importance of the other pools? Should, we stick w/ mining deepbit even when another pool got a fresh round? Or should we slice between all eligible pools? hrm.....

After wrestling with linux I got it running again. I'm getting a bunch of api errors for rfc, btcmonkey, mtred, nofeemining, ozco, bmunion, and polmine. Anyone else? I used the same config on my localhost machine but I just moved it to a vps.

Need slush to take priority over all other pools including deepbit .. I just manually had to disable deepbit, because it stole from slush at 3% ... luckily, I was quick enouigh to catch slush's amazingly fast 3minute block =). This change needs to be made to default scheduler ASAP!