IMPORTANT information for NastyPool miners using NastyPoP payout method!

I work to improve performance for NastyPool. If you are using NastyPoP payout method there are some changes now! If you are using P2Pool payout method there are no changes.

For miners using NastyPoP payout method:

• change from port 9332 to port 3334
• remove the +N part of your username (if you use that)
• make sure your username ends with -PoP

If your miners are donating to the fanclub (NastyMining, Squirrel Dearing, Bees Brothers, punkboy15) then these changes apply to you as well. With this change I fix support for spaces in the username. So Squirrel and Bees can show their full name without using underscore now.

NastyPoP will continue to work on the old port for now. But I will eventually turn it off because it negatively affects efficiency for all miners. So please make these simple changes as soon as convenient.

For fans interested in some details the NastyPoP payout method now uses ckpool as a P2Pool frontend. After you switch to port 3334 you will notice a dramatic decrease in rejects and a improvement in detected hashrate.

If some of this is not clear or you have any questions then please PM me or post here.

Hey

Just wondering since I added -PoP to my username, I'm unable to see the hashrate on the website since I cant sign a message with address and -PoP at the end. Any idea ?

Edit: Got it
https://nastyfans.org/nastypool/nastypop_ticker

There is a message "WARNING: No miner using your-bitcoin-addy found. Please check your miner and your mining address." when mining with the -PoP suffix instead of just the bitcoin-addy. The -PoP stats show up fine in the ticker, but the warning message is disconcerting.
 

On nastyfans.org/nastypool (at bottom) it shows what version I use and also the minor patch needed to support NastyPoP.

I monitor the commits and try to choose a good "version". I will need to spend more time on this. The testing phase was very positive. But today we had 17 minutes of downtime as ckpool freaked out.

It started with "Client fd N disconnected - recv fail with bufofs 0 ret 0 errno 0" messages and escalated to "Client fd -1 disconnected - select fail with bufofs 0 ret -1 errno 0" messages.

I see your latest git commits touch some of this.

Is there a place for open discussions about ckpool development?

I joined NastyFans today, wee

Nice to hear. Suggestions are welcome at all times. I maybe not get to them immediately but I keep a list.

NastyPool is still young. We identify some issues relating to P2Pool. The use of CKPool is part of many steps we are taking to improve running public P2Pool nodes. We still have more steps to take.

Thanks for your time work and generosity!

Ya, nonnakip usually cleans up stuff like this last.  Right now he's working on stabilizing things with the new frontend.

On another topic...  Thanks Squirrel Dearing for hosting our X3!  You can see that Squirrel has the X3 up and running on behalf of NastyFans.

Well, 900 isn't an option so it's up to 1000.. [edit]And i jsut cracked my window open a little more! lol[/edit]