Check your email again, account is unlocked.

**EDIT**

PityThePool's block confirmation time is after 120 confirms, which is a bit long and will take awhile before coins move into your balance.  If the dev chimes in with the proper block confirmation time, I can lower this.

Can someone explain this to me.

I like that the prices/volumes/market cap can be shown in both BTC and $USD.  However, when I change from USD to BTC the percentages and market cap % change column is always the same for both.

Shouldn't this be different?  If the $USD price of BTC is up by 5%, then I would expect any coins whose exchange price against BTC is unchanged to also be up by 5%.  But if I switch to BTC, I would expect the %change to be 0%. 

Instead, I see 5% regardless of whether I'm using BTC or USD to show prices.  This seems wrong to me.  If a coin's price is up by 5% I don't know whether that's because BTC is up 5%, or whether the actual exchange price of the coin is up by 5%.

Agreed!  Changing block rewards and KGW algorithm will prevent dumps on the exchanges by the multipools.  Price will steadily increase from here on out.

I received your request via the website - you need to click on the link from the activation email before you can login.  You should receive an email within a few moments of signing up.

Sorry but unfortunately fees are necessary to cover costs.
We are a SOLID and RELIABLE pool with GREAT uptime and fast response to support requests.
Our servers are not rentals at some VPS provider - we own the physical servers, the rack, and the data center.  We are here to stay.

As an added bonus - I will donate all pool fees and donations to the SunCoin development team for the first 48 hours, to help increase the coin's chance of success

GO SUNCOIN

Nope, sorry on deleting pools, I will add a delete button soon

PityThePool! is upgraded - now we just need miners

http://meow.pitythepool.com

Update

35 users have signed up so far, and only about 30 rigs are being monitored.  It seems the majority of users appear to be signing up just to "snag" one of the limited quantity of alpha accounts and have no mining rigs configured.  I'm opening up the alpha period to 60 years - we need more!

Would love to hear some more feedback from those of you who are using the system.

I was afraid of that - good to know, thanks.  It is definitely happening far less often receiving in 8k chunks rather than the 2k chunks I was using previously, and it was only happening when the data returned was greater than the receive buffer size.  As I said, time will tell on whether this is stable.

Thanks again for the input.  I've run into this as well.

Short version:
Every time you change pools, RigHound first checks to see if your instance of cgminer has that pool in it's "pools" list, and if it doesn't, adds it.  Then, it commands cgminer to switch to that pool.

The problem occurs when cgminer's "pools" list gets larger than maybe 3-4 pools in it.  I haven't figured out why yet, but for some reason sometimes I get back truncated JSON results (like, I get back 3 pools and only half the 4th's pools info).  Part of the problem may be that I'm using a raw TCPIP socket connection rather than an HTTP request (I'm convinced raw TCP/IP is faster), this means I have to build my own buffering/receive mechanism rather than the built-in HTTP ones, and I'll be the first to admit there may be some bugs there.

It doesn't happen all the time, and not with every rig, so it's tough to troubleshoot.  I'm working on this along with a better, faster & automatic way to refresh your rig's status (so you don't have to click the "Refresh" button and wait FOREVER).  Stay tuned, I'm making changes & improving this every day!

**EDIT**
Just implemented a possible fix for this, time will tell if it works consistently - as an added bonus, the "Refresh Status" button is about 2x faster as well

ABSOLUTELY!  Bulk rig management is definitely coming in the near future, including scheduling (mine at pool A for X hours then switch to pool B).  *Maybe* even some auto-profitability switching stuff (not sure I want to head down that path).  Right now I'm mostly concentrating on connectivity & reliability in reaching out to your rigs & controlling them.

Updates today:
Miscellaneous UI bugfixes
Rig total uptime displayed next to individual device statistics

Up next
Automatic refresh of mining rig statistics - so you don't have to click the "Refresh status" button to update your current pool info, hashrate, etc.

Thanks both of you for reporting this.  I found the issue, you should be able to add new pool workers now.

Hint:  RigHound configuration is easier when you use the same worker name for your rig at all your pools.  You can set the "Default Worker name" from the Edit Miner window.  If you do this, when you add new pool workers, they will be associated with the correct mining rig automatically.