That's the global p2pool hashrate which dictate variance and block discovery.

P2Pool local hashrate is less important, you'll prefer a pool with excellent latency and low DOA instead.

- Reserved for future use -

Tired of bad pool network connectivity?

We were too! We're proud to present our new p2pool running on a nice low latency network with ddos filtering.

Pool advantages:
- 0% fee!
- Safe and robust pool framework
- DDoS filtered network
- Low network latency, increase p2pool efficiency
- Hop proof algorithm

Bitcoin:
Server: pool.cp8.ca:3333
Username: your bitcoin address
Password: anything
Stats : http://pool.cp8.ca:3333/static/

Litecoin:
Server: pool.cp8.ca:5555
Username: your litecoin address
Password: anything
Stats : http://pool.cp8.ca:5555/static/

We still run the original stats pages, we wanted to get a stable environment first. Better stats layout should be incoming in the next few days.

Try us now!

Edit: Due to multiple request, we've finished the installation of our safe and fast BTC p2pool service.

I also just added the new s3.mining.eligius.st pool. For some weird reason, I'm getting a lot of invalid shares :

Submitted duplicate shares   17   4
Submitted stale shares   35   0

Which I don't get if I access directly. Anyone else noticed this behavior? The only thing I can see is that worker use the same login on the pool.

Nice!

On a 6950 : 349 MH/s -> 366 MH/s (3.75%)

Thanks!

Thanks, I'll check that out

You can keep it running, just slow down the upload rate to allow your miners packet to pass..

Nice link, quite interesting!

I've done fpga in the past on an old vortex 2 pro. Could be interesting to starting playing again..

Any of you could recommend some good FPGA dev board to start up with? Something that has a good power/price ratio?

Thanks

Do you have any p2p(torrent or whatever) software running? I've seen this problem often on satured internet connections...