A close hard look at pool profitability - or - results are what matters

[CSZiggy]

why bother, no one cares.

[yeominer]

One use case is simply to allow miners to establish how profitable the different algos actually were (and divide it by # devices on same algo to capture avg device profitablity), currently when pointing an L3 and an X11 at PH during the same 24h period cannot be allocated which algo did what (comparing it to your live est or historical). Although I use the workaround to use 3333 for one algo and use the proxy port for the other. That fails as soon as one wants to add a third algo. say point S9s as well, which I also do.

Just make multiple accounts on the prohashing.com site.

and set each algo to that user account so you have control, just login to whichever one you need, OR, use the API keys from each account to view them all on 1 screen.

Just ideas.
Good Luck!

yep, only registration for new PH accounts was closed for long time, and this crutch also involves then redundant tax / payout etc setups, not efficient at all. As Steve has confirmed will be non-issue soon anyways.

[Steve Sokolowski]

One use case is simply to allow miners to establish how profitable the different algos actually were (and divide it by # devices on same algo to capture avg device profitablity), currently when pointing an L3 and an X11 at PH during the same 24h period cannot be allocated which algo did what (comparing it to your live est or historical). Although I use the workaround to use 3333 for one algo and use the proxy port for the other. That fails as soon as one wants to add a third algo. say point S9s as well, which I also do.

Just make multiple accounts on the prohashing.com site.

and set each algo to that user account so you have control, just login to whichever one you need, OR, use the API keys from each account to view them all on 1 screen.

Just ideas.
Good Luck!

yep, only registration for new PH accounts was closed for long time, and this crutch also involves then redundant tax / payout etc setups, not efficient at all. As Steve has confirmed will be non-issue soon anyways.

Constance is going to work on this in June, so we hope that by the beginning of July we'll have the ability to group miners.

We'll be going further than per-algorithm statistics. Instead, customers will be able to create up to a certain number of "miner groups," for which balances will be tracked independently. Customers will be able to set up one group per algorithm if they would like, but the groups can also be used in other ways as they see fit.